When I try to upgrade DameWare 8.0 to 12.0 (or 11.1), I get this popup error:

The Application Event logs show:

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"

So I tried running SWregInst.exe while having the popup error, and I get another popup error saying:

The application was unable to start corredtly (0xc0000022). Click OK to close the application.

Any idea why the install is failing?

HI. there is any option in Dameware mini remote control to perform operation on other machine in invisible mode(without his knowledge)?

I can't use "invite user to join remote session" in Dameware Mini Remote Control, this option is gray and I can't access

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.

Any suggestions for a fix?

Thanks,

Chris

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.

Appreciate any help.

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:

1. Event 1026, .NET Runtime

Applicazione: SolarWinds.DRS.Licensor.exe

Versione framework: v4.0.30319

Descrizione: il processo è stato terminato a causa di un'eccezione non gestita.

Informazioni sull'eccezione: SolarWinds.Licensing.Framework.Store.LicenseStoreException

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL.ValidateStoreHash(Byte[])

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL.CreateNewStore()

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL.InitializeStore()

   in SolarWinds.Licensing.Framework.Store.LicenseStoreDAL..ctor()

   in SolarWinds.Licensing.Framework.Store.SingletonLicenseStoreFactory.get_StoreInstance()

   in SolarWinds.Licensing.Framework.LicenseManager..ctor(SolarWinds.Licensing.Framework.Interfaces.ILicenseStore, SolarWinds.Licensing.Framework.IOnlineLicenseManager)

   in SolarWinds.Licensing.Framework.LicenseManager.GetInstance()

   in SolarWinds.NTUtilities.Licensor.Program.RunLicensingWindow(Boolean, System.Collections.Generic.Dictionary`2<System.String,System.String>, Boolean)

   in SolarWinds.NTUtilities.Licensor.Program.Main(System.String[])

2. Event 1000, Application Error

Nome dell'applicazione che ha generato l'errore: SolarWinds.DRS.Licensor.exe, versione: 12.0.4.5007, timestamp: 0x58366005

Nome del modulo che ha generato l'errore: KERNELBASE.dll, versione: 10.0.14393.479, timestamp: 0x58256d37

Codice eccezione: 0xe0434352

Offset errore 0x000da832

ID processo che ha generato l'errore: 0x28c4

Ora di avvio dell'applicazione che ha generato l'errore: 0x01d2a2e463f502f7

Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\SolarWinds\DameWare Remote Support\SolarWinds.DRS.Licensor.exe

Percorso del modulo che ha generato l'errore: C:\WINDOWS\System32\KERNELBASE.dll

ID segnalazione: 245c6734-4e27-4431-9f06-11dc7ae1a826

Can you help me?

My computer is running Windows 10 64bit with all the updates installed.

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by dcolpitts on Wed Feb 27, 2008 8:58 am

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:

%ProgramFiles%\Dameware\DWRCS.EXE -install <-- installs DWMRC + start it
net user administrator clear_text_password <-- creates administrator account and sets it's password as BartPE does not have user accounts as per se

This basically installs and starts DWRCS from %ProgramFiles%\Dameware without adding any files to the %systemroot%\system32 and %systemroot%\system32\drivers folers - and since the ISO image is read only, updating the %systemroot%\system32 and %systemroot%\system32\drivers folders is impossible anyways once it is booted.

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.

dcc

Dean Colpitts
Members IT Group
Salisbury, NB

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by bryan on Wed Mar 12, 2008 2:46 am

Hi Dean,

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 hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by andrewsun on Wed Mar 04, 2009 8:17 am

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.

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by dcolpitts on Wed Mar 04, 2009 8:54 am

I'm not sure if this will help you or not, but I use Dameware with BartPE 3.1.10a and here is my plugin files:

CODE: SELECT ALL
; dameware.inf
; PE Builder v3 plug-in INF file for Dameware Mini Remote Control
; Created by Dean Colpitts, Members IT Group

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Dameware Remote Control Agent"
Enable=1

[WinntDirectories]

[SourceDisksFiles]
Files\System32\*.*=2,,3

[Software.AddReg]
; XPE Shortcuts
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","198","||xpeinit.exe -f -s -m ""Starting Dameware Remote Client"" %Windir%\System32\DWRCS.EXE -install"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","199","||xpeinit.exe -f -s -m ""Starting Dameware Remote Client"" net user administrator password"

Note that the username / password to connect with is saved in clear text within the registry of BartPE and is assigned on the last line of of dameware.inf file.

Below is the script I use to ensure my Plugin folder is update to date from the current installed build on my BartPE compiling machine prior to building a new version of my BartPE image:

CODE: SELECT ALL
rem UPDATE_DAMEWARE_PLUGIN.CMD
C:
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCK.dll" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCS.exe" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCSET.dll" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCShell.dlx" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCSI.dll" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCST.exe" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32
copy /y "C:\Program Files\DameWare Development\DameWare Mini Remote Control\DWRCST.exe.manifest" C:\_bartpe_3.1.10a_xpe\plugin\DAMEWARE\files\system32

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.

I know for one thing for sure, BartPE & Dameware have significantly help us cut our response time and costs for reimaging / repairing remote machines.

dcc

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by andrewsun on Sat Mar 07, 2009 4:05 am

Hi Dean,

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.

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by andrewsun on Thu Mar 26, 2009 7:38 am

PCAnywhere Thinhost is able to work well on Windows PE 2.0 and 3.0. Hope Dameware can develop a similar product as well.
Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)

by guy on Tue May 11, 2010 11:58 am

I have not been able to make DW work with any WinPE at all it just saying "Initalzing Desktop. Please Wait...."
I've got a post running here: viewtopic.php?f=9&t=2052&p=5221#p5221

anyone have any ideas?

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by nhelp4k6 on Wed Jun 02, 2010 1:01 pm

I'm curious as to why folks are using mrc (or any similar product) in a PE environment - just not seeing the utility.

The core of WinPE hasn't changed much from 2.x to 3.0, the overview of what WinPE is designed and scoped for can be found here:

http://technet.microsoft.com/en-us/library/dd799308(WS.10).aspx

tl;dr: WinPE is designed to load the OS or prep hw for the OS, not to be the replacement....

Re: DWMRC 6.7.x.x Mirror Driver & BartPE (WinPe / XPE)
by guy on Tue Aug 10, 2010 5:48 am

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.

Yes, I've seen the June 2011 discussion blaming Microsoft for this same problem but I'm wondering if anything has changed since then. Here's why.

Since I upgraded to DRS v9.0.1.247 last week, I have been unable to use it. I continually show No PDC. Yes, when I use Hyena v9.2 and open Computers, they all show.

Does this not indicate a problem within DRS? If the problem was due to NETBIOS browsing in Windows Server 2008 shouldn't both DRS and Hyena be unable to access the computer browser?

Thanks,

Phil

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.

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

Damware Remote on Windows PE?
by guy on Wed Feb 24, 2010 5:01 am

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.

DWRCK.dll
DWRCS.exe
DWRCSET.dll
DWRCSI.dll
DWRCST.exe

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"

Can anyone help me? I'm using Windows PE 3 with all packages installed WMI etc. 

Many Thanks!

Re: Damware Remote on Windows PE?
by guy on Wed Apr 07, 2010 9:04 am

Bump...
Anyone have any ideas at all?

Re: Damware Remote on Windows PE?
by dcolpitts on Sun Apr 25, 2010 8:15 am

You didn't make mention of whether you are using x86 or x64 of WinPE... As of 6.8.1.4, the Dameware client was 32 bit only, so it wouldn't work with the x64 builds of WinPE. You may want to have a look at my posting here: http://forums.dameware.com/viewtopic.php?f=9&t=469

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.

And just to be perfectly clear, I have not tried what I suggested above yet with WinPE 3, but I believe it should work.

dcc

Re: Damware Remote on Windows PE?
by rotot on Tue Apr 27, 2010 7:47 am

mmm...thanks for info

Re: Damware Remote on Windows PE?
by guy on Tue May 11, 2010 11:31 am

Sorry I was not clear and the delay.
my WinPE is currently 32bit.
I will test the install and let you know.

Re: Damware Remote on Windows PE?
by guy on Tue May 11, 2010 11:55 am

Thanks for your help so far!

Ok so I've done the follows:
Made a Windows Vista (32-bit) MSI with proprietary challenge/responce
Build the MSI
Extracted the MSI
Extracted Cabs.dwrcs.cab
Copyed the files: DWRCK.dll,DWRCS.exe,dwrcs.ini,DWRCSET.dll ,DWRCSh32.dlx,DWRCSh64.dlx,DWRCSI.dll,DWRCST.exe to X:\Windows\System32\ (X: being the standard drive letter PE sets)
Launched "X:\windows\system32\DWRCS.EXE -install"
It connects to the point saying Initalzing Desktop. Please wait...." and thats it nothing more I have turned off the mirror driver as well.

Any Ideas

Re: Damware Remote on Windows PE?
by dcolpitts on Tue May 11, 2010 12:37 pm

Not right off... I just tested it and get the same result you do. I fear you may SOL unless someone from Dameware wishes to point us in the correct direction.

dcc

Re: Damware Remote on Windows PE?
by guy on Wed May 12, 2010 4:48 am

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.... 

Re: Damware Remote on Windows PE?
by dcolpitts on Wed May 12, 2010 9:38 am

I'm not sure that is the issue... My BartPE (with Sherypa's XPE based on Windows 2003 SP1) works fine with Dameware, and it does not have RDP support in it.

Re: Damware Remote on Windows PE?
by guy on Thu May 13, 2010 8:13 am

in your BartPE if you type Net Start do you have Terminal Services running?!

Re: Damware Remote on Windows PE?
by dcolpitts on Thu May 13, 2010 8:50 am

Nope. These Windows services are started:
Audio Windows
DameWare Mini Remote Control
DCOM Services
DHCP Client
EventLog
Network Connections
Network Location Awareness (NLA)
Plug and Play
Protected Storage
Remote Procedure Call (RPC)
Security Accounts Manager
TCP/IP NetBIOS Helper
Workstation

dcc

Re: Damware Remote on Windows PE?
by nhelp4k6 on Wed Jun 02, 2010 12:51 pm

Read both the WAIK documentation (msdn or technet) and the Technet forums; PE stands for Preinstallation Environment - as in completing tasks so that the *full* system can be loaded. If you are interested in a windows "slackware" style session there is a convuluted method of building XPe to CD size. Disadvantages of the XPe method are several, to begin with it's a lot of work for limited (based on your description) payback, targeting tends to be specific to machine hw config, and you need the target designer - last I checked it ran ~$1K.
Better question, why do you want to use dwmrc inside PE/slackware?

Re: Damware Remote on Windows PE?
by guy on Tue Aug 10, 2010 5:55 am

The reason for wanting Dameware in PE is for remote rebuilding/repair.
PCAnywhere has "thin host" which works but it's very expensive and not really helpful as we have Dameware in many places.
The idea is that you boot into PE (remotely) connect into the PC with Dameware start the process you need i.e. A build and off you go.

HI. there is any option in Dameware mini remote control to perform operation on other machine in invisible mode(without his knowledge)?

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 5:28 pm

The full text of the message is The Dameware mini remote service is not running on xxx. Would you like to start it now? I answer OK and get "Unable to Start Service; System Error 2; The system cannot find the file specified. It started on a server this morning. After doing a random check of the computers on our domain I have found that it is random. Some machines are ok, some I can't access. It is not dependent on a specific operating system. Can anyone help?

Thanks.
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Mon Jul 09, 2007 6:02 pm

Hello Jodi,

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 7:12 pm

Bryan,

The DWRCS.exe file is version 5.1.1.0. We are using 32 bit computers running Windows 2000 SP4 and Windows XP SP2.

One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest. Some of the machines don't have the file at all.

Our AntiVirus software is Computer Associates and it checks for updates each day and will download them to the individual computers if needed on a daily basis.

Thanks for your help.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 3:30 am

Hi Jodi,

You're welcome.
One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest
Actually, the manifest file is a valid file, so it appears your DWRCS.EXE file has been deleted, not renamed. So this is most likely due to your CA eTrust software, either within the Anti-Virus portion of the software, or within the Pest Patrol portion of the software.

Therefore, all you should have to do is define an exception for our software in either portion of the CA software (AV or Pest Patrol) so it does not delete any files for our software.

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 9:33 am

Hi again Jodi,

Here is some additional information I received from another customer on this. Many thanks go out to Zac T. for this information. Hopefully this will help you out:
Here is what worked for me…

1. Log into the E-Trust management console
2. click on the policy management tab at the top of the page
3. under the policies section, change the application dropdown to eTrust PestPatrol and the Type dropdown to Pest Exclusion
4. on the right side of the page change the tab to “Pests” and click the change button.
a. In the box type DameWare and click search.
b. Highlight “DameWare Mini Remote Control” and hit the over arrow so it moves to the Excluded Pests box on the right
c. To close click the “Set Exclude List” button at the bottom
d. Click apply in the Policy Management tab to save those settings
5. Change the tab to “Paths”
a. Click Add
b. Type “Program Files\DameWare Development\DameWare NT Utilities” in the box and click “Set Exclude Path”. (I also added “c:\windows\system32\dwrcs.exe” but I don’t know if that is necessary)
c. Click apply in the Policy Management tab to save the settings
6. the last step is to assign the group to these policies
a. click the “Assign” button
b. navigate to the organization to assign the policy to, move the group to the right and click “assign branches”

that should do it…

This is what worked for us and I hope it helps someone else out that might experience similar issues.

Zac T
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Tue Jul 10, 2007 12:11 pm

Thanks Bryan and Zac T,

We excluded the dwrcs.exe in Pest Patrol and everything is back to normal (at least on the computers we have copied the file back to). Your help has been much appreciated.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Wed Jul 11, 2007 6:53 pm

Hi Jodi,

You're absolutely welcome, and thanks so much for letting us know this resolved your issues.
I'm glad we were able to help out.

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by wuliping0011 on Fri Apr 16, 2010 8:39 pm

Bryan wrote:Hello Jodi,

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000Replica chanle handbags

though that i know a lot.thanks

Dameware Mini Remote Control 12.1.0 Hotfix 2
is now available for download in your customer portal. Below are the release notes for this hotfix.

This hotfix addresses the following issues:

• Security fixes
• MRC crashes while connecting to PC with portrait mode
• Send refresh makes display stop updating (with enabled mirror driver)

Hotfix 2 also includes all fixes from Hotfix 1.

This hotfix requires Dameware Mini Remote Control version 12.1.0 (with or without Hotfix 1)

Warning: SolarWinds strongly recommends that you edit the files mentioned in this document only as instructed. Any additional modifications to these files may result in system performance issues or may cause an error. Make a backup of the files mentioned in the instructions below if you want to uninstall this hotfix later.

Install the hotfix on DameWare Proxy

1. Go to the Dameware Proxy machine.
2. Turn off the Dameware Proxy component in the Configuration wizard. If the Dameware Server runs on the same computer, turn it off as well. Do not close the Configuration wizard.
3. Open the DameWareDB.sdf database file using the free CompactView tool.
   By default, the file location is as follows: C:\Program Files (x86)\SolarWinds\DameWare Central Server
4. Go to the RoleConfiguration table and clear all check boxes in the ''Status'' and ''IsInitialized'' columns.
5. Remove all files from the binary folder.
   By default, the folder location is as follows: C:\Program Files (x86)\SolarWinds\DameWare Central Server\WebServerStaticContent\binary
6. Extract Hotfix 2 archive, and copy the contents of the Dameware Proxy folder into the binary folder.
   By default, the folder location is as follows: C:\Program Files (x86)\SolarWinds\DameWare Central Server\WebServerStaticContent\binary
7. Open Services, and select Stop the Dameware Server service.
8. If you have Dameware Proxy installed on a separate machine (Dameware Server installed on another machine):
   a) In the opened configuration wizard, turn on the Dameware Proxy component.
   b) Pair the Dameware Proxy component with Dameware Server (on the server side).
9. If you have Dameware Proxy on the same machine as the Dameware Server:
   a) In the opened Configuration wizard, turn on the Dameware Proxy component.
   b) Turn on the Dameware Server component.

Install the hotfix on Dameware Mini Remote Control

• If you have MRC x86 version, copy the contents of the MRCx86 folder to the MRC installation folder on the computer.
• The default location of the folder for Centralized Version as a part of the Dameware Server installation is as follows: C:\Program Files (x86)\SolarWinds\DameWare Remote Support
• If you have MRC x64 version, copy the contents of MRCx64 folder to the MRC installation folder on the computer. By default, the installation folder location is as follows: C:\Program Files\SolarWinds\DameWare Mini Remote Control x64
• Warning: If you have the remote control agent already installed on your remote machines from the Dameware 12.1 release, remove and install it manually from MRC (with Hotfix2 applied).

Uninstall the hotfix

1. If you want to uninstall Hotfix 2, you need to back up files (which will be replaced during the installation process) and save them in a separate location.
2. Follow the same steps described in the installation process, but instead, use your backed up files. The hotfix is then uninstalled.

For more information, see https://support.solarwinds.com/Success_Center/Working_With_Support.

Hi all,

I am having issues authenticating to a client machine. I am using Dameware Mini Remote Control version 7.5.9.1. I have attached a picture so you can see the exact error I am receiving. I can log onto the remote machine via the Windows NT Challenge/ Response option. It won't seem to authenticate the smart card for whatever reason. I have checked for the DWRCSS.dll in %systemroot%\DWRCS on the local and remote machines. It is in both locations. Any help on this issue would be greatly appreciated.

I get this error when I use Dameware SSH client for windows(Ver: 1.0.0.0) to ssh to some of my ESXi servers. Any idea how it can be resolved?

Error Message: connection error: Could not negotiate diffie-hellman-group1-sha1

Any help appreciated..

Regards,

S.G.K !

When our IT remotes to our Windows PCs they leave behind the DameWare Development Mirror Driver. This driver causes problems with at least one software application, and so it needs to be removed after the remote IT session is ended. How can this be automated?

Please note we have released Hotfix 1 for Dameware version 12.0. This hotfix is available on your customer portal.

Hotfix 1 addresses the following issues:

• ZDI-CAN-3125 vulnerability (Thanks to Andrea Micalizzi aka rgod, working with HP's Zero Day Initiative, for identifying this issue.)
• Upgrading MRC agents on remote machine failed.
• MRC was not able to connect to remote machine using "MRC Ping" feature.
• DRS Service installation failed in DRS.
• Event log does not show content in DRS.

Hotfix 1 requires SolarWinds DameWare Mini Remote Control version 12.0.0.509. Hotfix 1 can be applied to both 32-bit and 64-bit installations or SolarWinds DameWare Remote Support version 12.0.0.509.

You can find more details in README file included in hotfix.

Now go and download the hotfix now.

Hello,

I just installed the Dameware Remote Central Server on a fresh Windows Server 2012R2.

Unfortunately I cannot connect with the admin console and the server is not running properly.

In the wizard it just shows me, that the Server is "Not running, connection problems found". But not any detail about it.

Firewall is off, Server is in AD connected, DNS is fine and works from other machines to the server.

The admin console tells me "DameWare Server was not found on specified location. Please try different IP/Hostname....".

Do I have to do s.th. special to get the server running?

Can't find anything in the documentation.

I'm glad for every hint and help.

Thank you and have a nice day.

Kind regards,

Markus

I took over configuring Dameware 11 and configuring the Internet Proxy (and later the Mobile Gateway) from another admin. He had installed the components on a server which was already running IIS. I can't tell whether it installed web components within IIS or is using another web service. So that would be my first question. How do I confirm whether it is using the default website within IIS? I had setup a second IP on the server to be used only by Dameware so there would be no conflict on ports 80/443 with any previous services using IIS on the server. Now I need to make sure Dameware is only using that IP (I believe I've accomplished that in the settings), and I need to generate a CSR so I can get and install an SSL certificate for Dameware.

Thanks in advance for any help!