
This enables users to deploy and license DRS or MRC to several remote systems without being prompted to enter licensing information every time. and allowing it to push the 9.0 DWRCService to clients (as per Dameware's recommended approach).The MSI and EXE installers for DameWare Remote Support and MRC version 9.0 include command-line arguments that allow you to enter licensing information when installing from the command line. So I gave up and re-wrote our deployment scripts:ġ.) Used only on fresh/new/virgin machines to install the DWRCService (so in this scenario I don't need to worry about uninstalling any previous versions because it's a recently wiped/imaged machine)Ģ.) Upgrading the DWRC Host package 7.5 to 9.0.

I wish they'd be more transparent/document how to achieve this. So SOMEHOW Dameware is able to overwrite those files even though I can't do it manually.

and when that machine eventually reboots, the. If I have a machine that has DWRCS 7.5 and I push DWRCS 9.0 to it. rd %systemroot%\DWRCS\ /s /q (removes everything BUT fails to delete DWRCSE.dll, DWRCSh.dll and DWRCWXL.dll because "ACCESS IS DENIED"."C:\Windows\DWRCS\dwrcs.exe -remove" (seems to succeed, but fails to remove/delete the DLL's).regsvr32 /u C:\Windows\DWRCS\dwrcsh.dll (successfully unregisters the DLL, but can't unhook it from the shell).


posting this question here because I bet you guys/gals are more familiar with Dameware than some of the other forums.
