DameWare Mini Remote Control 7.5.9.0 (x86-x64)
Vita Strait
Product: DameWare Remote Support -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action PhoneHome_DIR, location: C:\Users\myacct\AppData\Local\Temp\, command: "C:\Users\myacct\AppData\Local\Temp\PhoneHome\SWregInst.exe"
Until recently, DRS has been working great. Then I applied the November update to Windows 10 and no the Microsoft Windows Network no longer displays anything in DRS. I am using version 12 with both hot patches applied. Other than applying the update nothing had changed in our environment. I can still find computers through the Active Directory, but it isn't nearly as convenient. It is particularly troublesome to find the few computers that are not part of the domain.
I have had Dameware for over 10 years I think. A great product, but recently we don't show any but about 9 systems as online. All of the servers show up, as do a few machines on the same VLAN. All the other VLANs no longer show. They have shown up for the last 2 years when the VLANs were configured. I can connect to them still under computers, but they no longer are listed under workstations. The "green" PCs show up under Workstations as online but the "blue" ones do not.
I tried upgrading to the newest release but the issue remains. I really want them back under Workstations so I know what is online. The Computers section shows all 1341 PCs in the AD, which I do not want to have to look through to find a staff member that needs assistance.
Hi, I have a problem to activate the latest version of DameWare Remote Support. When I i try to launch the executable SolarWinds.DRS.Licensor.exe or try to click the button "Enter License" inside DameWare Remote Support software I obtain the following error: "SolarWinds.MRC.Licensor has stop working" and in my computer event viewer I have these two entries:
I've built a support CD that is based on BartPE with Sherpya's XPE plugin interface, using Windows Server 2003 R2 (so SP1) media, that allows us to either boot machines via PXE into BartPE, or using a ramdisk, boot.ini and winnt.sif on the machine's hard drive, boot a copy of our ISO image from a folder. I started out integrating DWMRC into my BartPE image back with version 6.4.0.5. I generally update my ISO image every month or so with the newest DWMRC, antivirus defs, other drivers, etc, and have never had issues using DWMRC until 6.7.0.x. Now when we attempted to connect to the machine booted with BartPE, we are getting the message that theMirror Driver is not able to load, or the machine needs to reboot for it to become active. Yeah, I know we can click by it, but it is a pain, and the performance over DSL to some client locations is less than acceptable.
To integrate DWMRC into the BartPE image, I have created a folder on the ISO image (\Programs\Dameware) and into there, I have placed DWRCK.dll, DWRCS.exe, DWRCSET.dll, DWRCSI.dll, and DWRCST.exe. Next, I've modified the start init for BartPe (actually I'm using Sherpya's XPE interface over top of BartPE) that adds two entries the Microsoft\Windows\CurrentVersion\RunOnceEx key:
So, my question is, what has changed in the mirror driver installation between 6.6.x.x and6.7.x.x and how do I go about integrating the mirror driver of 6.7.x.x into my BartPE ISO. I thought it may just be a matter of adding DamewareDisp.dll to system32 and DamewareMini.sys to drivers, and that they would already be there when the mirror driver tries to install, but that did not help. If I had a copy of the registry entries that DWMRC creates when it installs themirror driver, then I could embedded those in the system hive that exists prior to BartPE booting.
Basically nothing has changed in the Mirror Driver itself. The only thing new was the addition of the actual message, letting you know the Mirror Driver couldn't be initialized during this connection for some reason. For example, in a non-standard machine config when the Terminal Services Service has been disabled.
Previously under conditions like this the software would just connect without using the MirrorDriver when it couldn't be loaded for whatever reason. In other words, it would just automatically switch over to non-Mirror mode without notifying you. In this latest version we decided to notify the user of this condition, but all you should have to do is click on OK to continue your connection.
I used the same method to integrate DWMRC into windows PE 2. After the computer booted from this windows PE CD, DWRCS.EXE was installed fine and DWMRCS service was started as well. From another computer, dameware remote control is able to authenticate to it but the process stucked at "initializing desktop, please wait". This message stayed on screen and dameware remote control could not show the remote desktop. I have tried DWMRC 6.2.x, 6.7.x, 6.8.1.4 and windows PE 2.0, 2.1, 3, but no luck. Did I miss any step or there is some other reason? We are using windows PE CD to image computers at remote sites. It will be great helpful if DWMRCcan work on windows PE CD.
I build my code from a mounted Windows 2003 SP1 ISO image on my BartPE development machine (actually it's a VM that I do my building in) and I use Sherpya's XPE 1.0.7 plugin for my user interface instead of the nu2menu. I use a default resolution of 1024 x 768 x 32bit.
Once we have the BartPE image created, we then install it into Windows boot loader (or boot.ini) and we also use it with PXE for reimaging / repairing machines at remote sites across the country. This way we can modify the boot.ini remotely to force the machine to boot the BartPE image without any user intervention, or if the machine's HDD is dead / blank / new, we can have the end user PXE boot the machine for us so we can re-image it / repair it as required.
Actually I used these methods yesterday at one client site to install Windows XP on a desktop that we didn't have an image for by invoking an unattended XP setup from within BartPE and once the pc rebooted, it automatically installed XP and joined the domain, where a GPO pushed the Dameware client to the machine and I was able to finish the software installation and customization of the machine.
Your method works perfect on BartPE, however windows PE does not like it. I guess MS puts some restrictions on their PE. One benefit of winpe is that it has all device drivers we are using though it is easy to add device drivers to BartPE. I expect some one knows how to fix it on windows pe, otherwise I will switch to BartPE.
The reason I want to use Dameware in PE is that I could remotely boot a PC but then I have no way to dial into the computer and kick off a build or recover a file etc.
Symantec have created PCAnywhere Thinhost for the exact reasons which I want but it's stupidly expensive.
So after upgrading my M.2 240ssd to a 1TB m.2 I figured I would reinstall windows 10 and go with the latest creators version 1709. After installing Dameware Remote Support 12.05.6002 I no longer saw the MS network section expanded in the master browser with all my windows devices like it had in previous versions of windows, including previous windows 10. 1703
Well after contacting solarwinds support and working through the issue, as well as searching on google for this issue. I came across Microsoft disabling smbv1 in windows 10 1709 by default. After I went in to contol panel, add/remove programs, and windows features turn on/off I renabled the smbv1 protocol and now the MS windows network section is once again populating. Ive attached a screen shot of the place to check.
Solarwind's whole licensing procedure is terrible. Everything was running just fine with Dameware Remote Support (which includes Dameware Mini Remote Control) until today when I received a "License Expired" popup when launching DMRC. I tried to re-activate and I get a "License Activation" failure whether I use the local license manager or online activation. Our maintenance was up a couple of years ago, but we only have one client on Dameware and they are on the same version that we are on, so there is clearly no need to upgrade to version 12 since it would force them to also upgrade to version 12. I have tried uninstalling and reinstalling the same version 11 that was available when the maintenance was in effect. I've even tried regenerating the license file using my unique machine ID and it still fails. Anyone have any ideas.
Hello,
Over the last few days I have been trying to get Windows PE to run Dameware.
What I have done is install the client onto a base PC, copy off the drivers I think are required (below) copying them to PE in X:\Windows\System32\ and then started DWRCS.exe - install /-service.
I can ping the PC with PE (firewall switched off on both computers) and it authenticates and it even tells me the keyboard set is in a different language but it then gets stuck on "initializing desktop, please wait"
Also, since my last posting there, I found a somewhat simplier way to do things. Use the "DameWare Mini Remote Package Builder" to build an MSI, including configuration for Proprietary Challenge/Response, then extract that resulting .MSI with 7-Zip, and then within there, you will find a Cabs.dwrcs.cab. Extract that to your WinPE's \windows\system32 folder. That contains everything you need to run the client. Lastly, you will need to add a line to run "\windows\system32\DWRCS.EXE -install" within WPEINIT.
Thanks for that...
At least I know I'm not being stupid now if someone else can replicate the issue I have.
It's as shame as I'm sure it's something fairly simple to fix as it's -almost- working....
Anyone from Dameware - Are you reading ?
Re: Damware Remote on Windows PE?
by guy on Wed May 12, 2010 7:56 am
Just to update further.... It seems that becuase Dameware required Terminal Services this will never work....
PE is just too stripped down to allow anything like this to work
I guess it's time to look at an open source application for PE....