Updated March 11th, 2016
This article provides steps to do the following:
I. Manual Installation:
The DameWare NT Utilities (DNTU) Client Agent Service (DNTUS26.EXE) and the DameWare Mini Remote Control (DMRC) Client Agent Service (DWRCS.EXE) can be manually installed on any machine by simply copying the required files to the appropriate directory on the remote machine, then executing one simple command to install the Client Agent as a Service.
When running version 6.x or later, the easiest and most efficient way to install the DMRC Client Agent Service on all remote machines is by building an MSI package with the new DMRC Client Agent MSI Builder included within the software. The DMRC Client Agent MSI builder (DWRCSMSI.EXE) allows a user to build custom MSI packages (including all settings, INI or Registry) to deploy the DMRC Client Agent Service in your environment. These MSI packages can then be sent to the clients (or even distributed via Group Policies within Corporate Environments, etc.) using any of your existing distribution methods.
Additional information on this topic can be found in the following Knowledge Base article:
How to create an MSI package via DMRC Client Agent MSI Builder
II. Manually Installing the DameWare NT Utilities (DNTU) Client Agent Service (Windows XP Pro and above only):
The DNTU Client Agent Service is completely separate from the DMRC Client Agent Service (see below) and is not required to be installed on the remote machine in order for DNTU to function properly. The DNTU Client Agent Service is only required for the RCMD Console, RCMD View, and ShutDown View (poweroff and logoff only), and provided the necessary File & Printer Sharing ports are open between the local and remote machines, DNTU will automatically prompt the user when the service is necessary and not installed on the remote machine.
To manually install the DNTU Client Agent Service:
III. Manually Installing the DMRC Client Agent Service:
Unlike the DNTU Client Agent Service, the DMRC Client Agent Service must be installed and running on the remote machine before a connection can be made to that machine via the DMRC software. Typically, in a Local Area Network (LAN), the installation of the Client Agent Service can be done when the initial connection is made, however, the ability to install the Client Agent Service remotely depends on many different factors within the Operating System implementation and configuration.
1. A valid set of credentials (UserID & Password) with local Administrator rights on the remote machine is necessary.
2. "File & Printer Sharing" must be enabled on the remote machine.
3. The Admin$ share must be available on the remote machine.
4. All the necessary File & Printer Sharing ports (UDP 137, UDP 138, TCP 139, & TCP 445) must be open on all routers/firewalls between the local and remote machines.
5. These same ports must also be open on any firewall software on the remote machine (i.e. Windows Firewall, ZoneAlarm, Black Ice, etc.).
6. The remote machine must be running Windows XP Pro (with "Simple File Sharing" disabled), 2003 Server, Vista, Windows 7, or 2008 Server.
If any of these conditions are not true, then the DMRC Client Agent Service MUST be manually installed on the remote machine before a connection will be allowed.
In order to manually install the DMRC Client Agent Service:
For version 6.x and below, copy the following files from the DameWare Development installation folder to the System32 folder on the remote machine.
**For Windows 95/98/Me, copy these files to the \Windows\System folder instead of System32:
**For 64-bit Operating Systems, copy all these files to the SYSWOW64 folder instead of System32:
DWRCSh32.DLX (v6.7 and higher)
DWRCSh64.DLX (v6.7 and higher, only for 64-bit Operating Systems)
DWRCShell.DLX (v6.6 and below)
DWRCShell64.DLX (all versions between 220.127.116.11 and 6.6.x, and only required for 64-bit Operating Systems)
The following modules are required for connecting via FIPS Mode (v6.7 and above).
For version 7.x and above, copy the following files to the %windir%\dwrcs folder on the remote machine.
In order to use FIPS Mode in v7.x, the following files must also be copied:
1. Open a Command Prompt (Start / Programs / Accessories / Command Prompt). For Vista and above, due to UAC you will have to right-click on the Command Prompt and select "Run As Administrator".
2. Change the default directory to the appropriate folder listed above.
3. Type the following command to install the Service:
DWRCS.EXE - install
One additional thing to note is that some Windows Operating Systems do not automatically start a Service during the installation. Therefore, the Service may have to be manually started the first time either via DNTU Services View or the machine's Administrative Tools - Service view (MMC Services Snap-In). This can also be accomplished from the Command Prompt via the Net Start command (include quotes around the service name).
Net Start "DameWare Mini Remote Control" or Net Start DWMRCS
Net Start "DameWare NT Utilities 2.6" or Net Start DNTUS26
Similar to the installation of a Service, some Windows Operating Systems do not automatically stop a Service when it is removed. This may or may not cause issues when reinstalling the Service without rebooting the machine. Therefore, it may be beneficial to access the machine's Administrative Tools - Services view (MMC Services Snap-In) and Stop the Client Agents before removing the Service. This can also be accomplished from the Command Prompt via the Net Stop command.
Net Stop "DameWare Mini Remote Control" or Net Stop DWMRCS
Net Stop "DameWare NT Utilities 2.6" or Net Stop DNTUS26
A single command is required to manually remove the Service. This also applies to the centralized version. Command is shown below:
For the DNTU Client Agent Service:
For the DMRC Client Agent Service:
After the Service has been removed the associated files listed above can be deleted.
Using Microsoft SC.EXE utility to create or delete Services
Microsoft offers an additional utility which allows a user to remotely create, start, stop, and delete Services from the command line. It is called the SC tool (Sc.exe). Also note that [MachineName] is an optional parameter, and when it is not specified the current machine is used.
How to Create a Windows Service Using Sc.exe (© 2017 Microsoft, available at https://support.microsoft.com, obtained on March 20, 2017.)
For Example: (XP/2003 only):
sc [MachineName] create DWRCS DisplayName=DameWare Mini Remote Control Type=own Type=interact binPath="DWRCS.exe -service"
For Vista / Windows 7 / 2008 Server (since Services no longer interact with the Desktop):
sc [MachineName] create DWRCS DisplayName=DameWare Mini Remote Control Type=own binPath="DWRCS.exe -service"
sc [MachineName] delete DWRCS
If files or Registry entries are mistakenly deleted/renamed prior to reading this article, further knowledge of Services and how they work within Microsoft Operating Systems is needed. Please consider the following:
1. Services are not the same as programs. Services are only for Administrators to install and remove, and by Microsoft's design will not show up in Add/Remove programs. To find the list of Services installed on a machine, look under Services in Microsoft's Management Console (MMC) , or use DNTU's Services View.
2. Also, deleting/renaming Registry keys or files is not the proper way to remove ANY Service within the Operating System. When a Service is installed, the Operating System will create and maintain Registry entries for the Service. Deleting these files or entries will only generate errors when the machine is rebooted because the Operating System will still be looking for the files. It is important that a user follow the instructions above to properly remove the Service.
3. Due to the new User Account Control (UAC) security included in Vista and above, the Command Prompt must be opened as an Administrator. Otherwise it will be run as a Filtered Administrator (i.e. regular user) and the user will not have sufficient rights to install, remove, start, or stop the DMRC Client Agent Service.
If the files are mistakenly deleted or renamed without running the command above to properly remove the Service first, try the following:
1. Re-copy all the necessary files listed above from the DameWare Development installation folder back to the appropriate folder (listed above) on the remote machine.
2. Open a command prompt and change the current directory to this same folder where you just copied the files. Now issue the command to remove the Service properly:
3. The Service can be reinstalled by typing: DWRCS -install. and restarting the Service, either via the MMC or by typing: net start "DameWare Mini Remote Control". The Service can also be reinstalled by connecting to this machine again using the DMRC software.