There are two pieces, or sides, of the Mini Remote Control program. Since, by definition, an MRC connection occurs from a local machine to a remote machine, the MRC application is the actual program installed on the MRC User's local machine. The MRC application is used to control the remote machine. On the remote machine is installed the second piece (the remote piece) of the MRC program called the MRC Client Agent Service.
Since the remote control connection is established using a straight TCP connection from the local machine to the remote machine, the MRC Client Agent Service simply gives the MRC application something on the remote machine to connect to. This Service runs in the background of the remote machine under the Local System account. When there is not an active MRC connection it uses little to none of the remote machine's CPU.
Installing, removing, starting, stopping, and upgrading or downgrading of the MRC Client Agent Service requires local Administrator rights within the Operating System security of the remote machine. For details on how the MRC Client Agent Service can be installed on a remote machine, please see the "MRC Client Agent Service Installation Methods" Help Topic in the Additional Information section of the Help Files. Lastly, having the MRC Client Agent Service installed and running on a machine is not a security risk as the MRC user must authenticate locally to the remote machine prior to the MRC connection being established. For more information regarding Security, please see the "Security and Encryption Overview" Help Topic in the Additional Information section of the Help Files.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.