After installing the Symantec Response Assessment Module, the RAM Server Service is not installed.
The Symantec Response Assessment Module Application Server service account must have Log on as a Service right. The Web Service application pool account is used to authenticate users to the domain. The Symantec Response Assessment Module Application Server service account and the Web Service application pool account should be the same user account.
The following rights are required for the Symantec Response Assessment Module Application Server service account:
Verify that the RAM_DB has been created.
The CCS RAM needs to have the sysadmin rights to properly create the RAM_DB (i.e the default name of the RAM database) and the tables inside this database.
- Bypass traverse checking
- Log on locally
- Log on as a service
- Log on as a batch job
The Web Service application pool account must have the following permissions:
- Minimum permissions and rights to the installation computer
- Be a member of the local IIS_WPG group. NOTE: on Windows 2008 this group is called : IIS_IUSRS
- Full permissions to the %Windir%\Temp directory
- Full permissions to the .NET installation directory
- Read and write access to the SQL Server.
If you enter the incorrect service account information during the installation, you can edit the identity. Open the IIS Manager and navigate to the RAMAppPools Properties > Identity tab. You can edit the service account information for the Symantec Response Assessment Module Application Server service.
Follow these steps to verify the service has been installed:
Click Start > Run and type services.msc, and then press ENTER.
In the details pane, the Symantec Response Assessment Service should be visiable.
After the above has been implimented. It is advised to uninstall CCS RAM. Verify that the database has been uninstalled. If not uninstall the database.
Then reboot the system. Login as local administrator or domain admin and reinstall CCS RAM. The Symantec Response Assessment Service should be visiable.
If the issue continues. Try to install the application on another server.
To gather further evidence to troubleshooting RAM issues it helps to obtain the log table.
The log table for RAM is located in the SQL ram_db database there is a table named logs.