It is possible to remotely monitor a Riva server without enabling RDP access. Two remote access methods can be enabled:
Enable Remote Monitoring of the CRM Agent Service
it is possible to configure the CRM Agent Service on the Riva server to pipe output to the Riva CRM Service Monitor application installed on another Windows system.
To do so:
Install Riva on the Windows system that will be used to monitor the Riva CRM Agent service. (For example, if Mary will monitor Riva, install the Riva files on Mary's Windows system.) Do not configure any Riva connections or sync policies. Just place a shortcut for the CRM Service Monitor application on the user's desktop.
On the Riva Server modify the CRM Agent Service .config file to identify the IP address:port for the Windows system that will run the Remote CRM Service Monitor application.
Note: The communication between the Riva CRM Agent Service and the CRM Service Monitor application is made via XML messages sent via UDP. By default, the communication occurs on port 10999.
On the Riva server, add an app.setting to the CRM Agent Service .config file to direct the UDP communication stream to an additional IP address. If the file does not exist, create it:
- To modify the Riva CRM Agent for Exchange, the file name is Omni.Riva.CrmAgentEx.exe.config
- To modify the Riva CRM Agent for GroupWise (legacy connection), the file name is Omni.Riva.CrmAgent.exe.config
Use this key: Crm.EventLogger.UdpTargets = 127.0.0.1:10999;x.x.x.x:xxxxx
The value is a comma or semi-colon delimited list of IP-ADDRESS:PORT targets. Ensure that you include 127.0.0.1 for the localhost. In this example, if the IP address for Mary's Windows system is 10.10.5.253, then the value would be:
Enable Remote Access to Riva Server Logs
To provide remote access to the Riva server logs, share the following Riva server folders to those AD users that need access and provide Read Only share permissions:
- Riva system logs: \Riva\Logs
- User monitor activity logs: \Riva\CRM Integration Logs