[DameWare Mini Remote Control] Logging 功能要如何使用?

How to Enable the New Centralized Logging Feature in the Mini Remote Control Program

The centralized (remote) logging feature of the MRC Client Agent Service enables Administrators to send a duplicate copy of the DWMRCS entries recorded in the Application Event log on a remote machine to another centralized logging server.

To take advantage of this feature, you must first install the MRC Client Agent Service on all your remote machines. The easiest and most efficient way to accomplish this is to use the new MRC Client Agent MSI Builder included in version 6.x and above. The MSI Builder will create a MSI installation package including all custom settings from the DWRCS.INI file or the Registry, which you can then distribute to all your remote machines using any of your existing distribution methods (i.e. Group Policies, etc...). For users running older versions prior to 6.x, you would have to pre-install the MRC Client Agent on your remote machines, and then you can either go back and manually enable the logging settings or push out the appropirate Registry keys. Unfortunately, these logging settings are not available within the DWRCS.INI file, only in the Registry:

Here is some additional information on how this process works:

1. All machines (the ones sending the logs and the ones receiving the logs) must have the Mini Remote Client Agent Service installed & running (not in a stopped state).

2. All machines sending their logs must have the following settings defined within the MRC Client Agent:

  • The "Enable Remote Logging" setting must be enabled.
  • The IP-Address, HostName, or FQDN of the machine receiving these Log Files (Log Host) must be specified.
  • The correct TCP port the MRC Client Agent Service is configured to listening on, on that specific remote machine (Log Host Port Number), must be specified.

Then, anytime someone connects to this machine using the Mini Remote Control software, the Log Entry will automatically be recored in the Operating System's Application Event Log on that remote machine, and then the MRC Client Agent on that machine will also forward a duplicate copy of the Log Entry to the MRC Client Agent running on the Log Host machine.

3. The machine receiving these Log Files must have the following settings defined within the MRC Client Agent:

  • The "Enable Logging to this host" setting must be enabled
  • A Log Path for this local machine must be specified (i.e. C:\DameWare Log Files\ ). A UNC path is not valid.
  • The Maximum log file size must be specified in bytes.

When the MRC Client Agent on this machine sees an inbound logging request, it will take the log entry in and then append it to the DWRCS.CSV file in the specified Log Path directory. If the file does not exist, one will be created.

That's basically it in a nutshell.

Other than this, make sure all machines are running the same version of the MRC Application or MRC Client Agent Service. Also, if you apply these changes by distributing a .REG file or importing these changes directly into the Registry after the MRC Client Agent has already been installed on the remote machine, then you also have to make sure to stop & restart the MRC Client Agent Service on the remote machine before these new settings will take effect. The MRC Client Agent only reads in it's settings when you initially start the Service, or when you manually make changes within the GUI (right-click on the SysTray icon and then select Settings, or select View / Remote Server settings while you're connected).

Registry settings for machines sending the log files:

"Enable Log Reporting"=dword:00000001 (0=disabled, 1=enabled)
"Log Host"="192.168.xxx.xxx"
"Log Host Port Number"=dword:000017f1 (hex value)

**"Log Host Port Number" specifies what TCP port the Client Agent Service is listening on (in hex), for the remote machine receiving the log files.

Registry Settings for machine receiving the log files:

"Enable Reporting For This Host"=dword:00000001 (0=disabled, 1=enabled)
"Log Path"="C:\\WINDOWS\\SYSTEM32\\"
"Max Log Size"=dword:009c4000 (hex value)

The DWRCS.CSV log file :

All entries are then recorded or appended in the DWRCS.CSV log file, which is created in the "Log Path" you defined above (if one doesn't already exist). This is a standard CSV (Comma Separated Value) formatted file which can be opened in any third-party reporting tools (i.e. Excel, etc..).