hello,
I love Dameware, have been using it for years, even before SolarWinds bought it. It seems though, looking at these forums, that DameWare seems to be "dead" most of the questions in this forum are old and even more of them do not even have answers. am I in the right place when looking for support or is this product dead and no longer supported?
thanks
Mike
I’m thrilled to announce that Dameware 12.0 is now publicly available. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. Technicians can now support end-user in company network as well as in Internet anytime.
This release brings several bigger and smaller improvements, so let me highlight a few of them:
Dameware 12.0 is available for download on your customer portal for those customers under current maintenance.
If you are not a Dameware user yet, now go and download new version from www.dameware.com now!
We use Dameware all throughout the Air Force and we will be going to mandated PIV's where we have to use our CAC cards with our administrative accounts, which will prevent us from using Dameware. Is there a work around for this, or will there be a solution for this issue? If there isn't, we will no longer be able to use Dameware and the Air Force will not purchase any more licenses.
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:
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.
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
Our company is evaluating your product (DRS) for wide use in our environment, but due technical issues we are not able to do that.
About the issue, I want to use Microsoft App-V to virtualize DRS in our environment (because we will distribute DRS with Citrix XenApp). I was able to virtualize DRS, but licence won't follow with virtual package. When I start DRS inside virtual bubble, it says that there were no licence available (all tho I gave licence information via /ARGS during installation like your KB article 400113 states).
So where licence lays? Is it in registry or where? Have anyone done App-V virtualization to DRS earlier successfully with latest versions (DRS 10 and App-V 4.6 or 5.0)?
Thank you already for your reply.
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?
I just upgraded my centralized server to version 11.1 and I'm trying to get all of my techs client machines upgraded but the silent install isn't working. It just hangs forever. Any idea if there are some changed arguments for version 11.1 .exe install.
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.
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?
I have been running on Windows 10 for quite a while (since last fall) and using Dameware Remote Support (11.0.0.1003). Recently I upgraded to the latest W10 version (1607). Unfortunately, this broke the remote clipboard. I have a co-worker who had the same experience. The only difference between the two was that his mini-remote worked fine, then he upgraded to the "full-version" (as we call it).
Any ideas about how to fix this? I would have thought a reinstall of the application, but with the fresh install that was broken that didn't seem like a solution. Any thoughts?
HI Guys.
wonder if you can shed some light on this. we have changed the IP address of the Web Help Desk server, when i try to use the intergration from WHD and upload to the ticket via Mini remote control the URL is incorrect. Anyone know where i can change this?
thanks
I'm working with central server Dameware 11.1 and trying to get it to work with smart card connectivity in windows 10. It keeps kicking out an error "SmartCard Driver was installed but requires a system reboot (5.5.105.2)." They remote system was restarted in an effort to troubleshoot, however, the event logs do not show anything else other than
System Message: The operation completed successfully.
(srv 64 bit)
Has anyone seen this yet?
Hi guys,
We need to buy DameWare Mini Remote Control for some of our sites.
But, the first installation under Windows 10 was not a success with this message: "There is a problem with this Windows installer package. A program run as part of the setup ... etc etc"
We find some solutions to this issue, download again installer, framework 4.6 and 3.5 presents.
No success...
Anybody can help?
Thanks for answers.
SFT not working
by fabvit on Tue May 17, 2011 3:47 am
SFT not working:
1. I've installed DWMRC v7.5.6.0 on my local windows 7 pro 64 machine.
2. I've installed DWMRCS Agent v7.5.6.0 on the remote pc of one of my customers windows XP Pro 32 bit SP3. Please note that after Installing the Agent I've rebooted the pc. I've installed the Agent after having logged in as Administrator.
If I try to upload from my pc, right clicking on a file on my desktop I can see in the context menu:
DameWare MRCC -> Copy to Remote Host: HOST_NAME
but pressing it does blink and does not upload the file.
On the remote pc things are worse: the DameWare MRCC context menu's menuitem is completely missing.
Please note that on the remote machine I have enabled SFT in the tryicon settings.
This is specific to this connection: I can upload/download files and folders when connected with other customers.
Any idea?
Thank you
fabvit
________________________________________
Re: SFT not working
by DawgBone on Tue May 17, 2011 10:08 am
Does the file get copied when you drag and drop it into the application? (local >remote)
Does the file get copied if you use the SFT Drop window? (hold down shift+blue folder)(remote>local)
This would determine if it is the SFT feature failing or the right click context that's failing.
DawgBone
________________________________________
Re: SFT not working
by fabvit on Wed May 18, 2011 2:51 am
> Does the file get copied when you drag and drop it into the application? (local >remote)
No, the file is not get copied when I drag drag and drop it into the application (local >remote)
> Does the file get copied if you use the SFT Drop window? (hold down shift+blue folder)(remote>local)
No, the file is not get copied if I use the SFT Drop window (hold down shift+blue folder)(remote>local) and an notification dialog appears:
The MRC Client Agent are not ready for file transfer
Some idea on how to solve this issue: SFT is foundamental to my day to day support activity.
Thanks, fv
--
fabio vitale
fabvit
________________________________________
Re: SFT not working
by bryan on Thu May 19, 2011 11:19 am
If there are errors with SFT (or any other feature) there should be 1 or more dwmrcs entries in the Application Event log on the remote machine. Please copy and paste the full text of each of those entries and send this information to our support team at Support@dameware.com so we can review it. Please also send another screen shot of the exact error that's displayed when you try to open the SFT drop window on the remote machine (Shift + blue folder).
So nothing happens when you drag a file/folder from your local machine into the Open MRC connection window?
Also see if the %windir%\dwrcs\sft folder exists.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: SFT not working
by bryan on Fri May 20, 2011 3:59 pm
Hi again Fabio,
One more thing you might want to try is to update the MRC Client Agent service on the remote machine once you get connected, in case there is some type of file corruption. Make your MRC connection, then select File / Update Client Agent from the MRC main menu. Then try your SFT again.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
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
Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 13, 2007 5:34 am
Hi All,
We are currently having issues with logging onto some of our machines using the DameWareMini Remote Control. We recently installed some Microsoft patches on the machines and this has resulted in us having to log onto the machines using Remote Desktop rather than DameWare. Do you know of any Windows updates that may affect DameWare connection? When we try toconnect using DameWare we get the Winsock error:
Connect Error:
System Error: 10061
System Message: No connection could be made because the target machine actively refused it.
We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.
Any help would be greatly appreciated.
Kind regards.
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Fri Sep 14, 2007 11:13 am
Hello threeofspades,
Are you sure you're specifying the correct TCP port in your Host settings?
Is the MRC Client Agent Service already installed & running on these remote machines?
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?
Because a Winsock 10061 error typically means the MRC Agent Service was not listening on the TCP port that you specified (default is TCP 6129). Then a subsequent attempt at interrogating the Servcie Control Manager on the remote machine failed for some reason (insufficient rights, ports blocked, file & printer sharing not enabled, etc…). This process of interrogating the Service Control manager requires the Operating System's Installed Protocols (File & Printer Sharing - UDP 137, UDP 138, TCP 139, TCP 445) to be open between the loal & remote machines, and it also requires Administrator rights within the O/S security on the remote machine.
Therefore if we cannot connect to the MRC Client Agent on the remote machine using the specified TCP port, and then we also cannot communciate with the Service Control Manager on the remtoe machine using Microsoft’s APIs, then we have no choice but to fail. Because these same ports/protocols used by Microsoft’s APIs in order to communicate with the Service Control Manager are the same ones required to install, remove, start, or stop the MRC Client Agent Service on the remote machine.
However, please also click on the Copy button on the Winsock Error Dialog, then send me this information (paste it into this email) back to me for examination. Also include a screen shot of the actual Winsock Error dialog as well so I can review it.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Mon Sep 17, 2007 6:19 am
Hi Bryan,
Thank you for your response.
I have some additional information that may help to try to resolve this issue.
I can use MRC on the servers themselves to connect to my own machine, but am unable toconnect from my machine to the servers using MRC.
When i try ot connect to the server using MRC i first get a message saying the following:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
I select OK but then get the following error:
"Unable to start Service
System Error: 2
System Message:
The system cannot find the file specified"
When I RPC'ed onto the server and checked the DameWare Mini Remote Control service is was not running. When i selected to start it i get the error:
"Could not start the DameWare Mini Remote Control service on Local Computer
Error 2: The system cannot find the file specified."
When i checked the path to the executable 'C:\WINDOWS\system32\DWRCS.EXE -service' the DWRCS.EXE was not in there.
I have tried to load DameWare again but get the same errors. It seems that this executable has been deleted for some reason. How can i retrieve it or load it again?
Thank you for your time and effort.
Kind Regards
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Mon Sep 17, 2007 10:37 am
Hi threeofspades,
You're welcome and thank you for this additional information. It was very helpful...
As you have already found, Microsoft's System Error: 2 means File not found, and that's definitely due to the DWRCS.EXE file being missing in the System32 folder.
However, all you should have to do is re-copy the DWRCS.EXE file from your local DameWareInstallation folder to the System32 folder on this remote machine. Then you should be able torestart the Service again.
But you might also want to do a little extra research to find out how this file could have been deleted.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Tue Sep 18, 2007 4:43 am
Hi Bryan,
I took your advice and copied the DWRCS.EXE file from my local machine to the WINDOWS\system32 folder on the server.
When i tried to MRC onto the server i got the request:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
I selected OK and it came up withthe message:
"Service Start Status:
Starting service....."
I thought that this was looking good but unfortunately it came back to the above message:
"The DameWare Mini Remote Control is not running on onyxctx2.
Would you like to start it now?
Host: onyxctx2".
It seems that the service is starting but is tehn stopping several seconds later.
I RPC'ed onto the server to check out the DameWare Mini Remote Control service. It was setto automatic and was not started. i set it to start and it did so. But about 5 seconds later it just stops.
Not sure what is going on but something is stopping the service from running.
Any ideas?
Kind regards
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Tue Sep 18, 2007 1:46 pm
Hi threeofspades,
Thanks very much for the update. This is some great information.
I believe you're right. There appears to be something else here that's stopping the Service from running. What other software do you have running on this machine? Do you have anything like CA eTrust, or Pest Patrol, or Pest Patrol remote (look for ppRemoteService.exe in Task Manager under Processes)?
If this is the cause, then additional information on how to configure the appropriate exception within Pest Patrol is also available in another thread on our forum:
The Dameware mini remote service is not running on XXX.
http://forums.dameware.com/viewtopic.php?f=8&t=47
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 20, 2007 5:42 am
Hi Bryan,
Thank you for all your help.
We do have eTrust running on our systems and when i placed the DameWare exception into the Management Console i got DameWare back working on all but one server. But i will check it out and see if i can figure out where the problem is. I'm sure it's just something simple but the service still seems to be stopping on that particular server.
Thanks again for all your help and it was very much appreciated.
Kind Regards
Granting remote control rights to non-admins
by abentley on Wed Sep 09, 2009 4:38 am
Try as I might, I have been unable to get non-admin users to be able to remote controlcomputers. I am running Windows Vista Enterprise SP2 and MRC 6.8.1.4. I have read a lot of posts on the subject and understand that the default dwrcs.ini settings need to be altered during MSI creation so that non-admins will be able to connect (after permission is granted) and i'm pretty sure I've got the settings correct, but only users with admin rights are currently able to connect successfully.
What I want is for members of a specific domain global group to be able to connect to any MRC client. All of the members of this group are at the very least members of the local 'Users' group on each computer (becuase they are members of Domain Users which is in-turn a member of the local Users group). Some members of the domain group have local admin rights on computers, and it is only these accounts that are able to authenticate and connect.
I require all connection attempts to prompt for permission when someone is logged on to the target computer, and for any connection to a locked or un-logged-on computer to be automatically accepted.
I have tried both Encrypted Windows Logon and Windows NT Challenge Response authentication methods without success. I'm pulling my hair out now as I really need some users who can't have local admin rights the ability to remote control with MRC.
Here is my INI file (I am not using registry settings), can anyone spot anything wrong with it?
CODE: SELECT ALL
[Settings]
Port=6129
Adgang NTLM=Yes
Adgang 1=
Adgang 2=
Adgang 3=0
Notify On New Connection=Yes
Notify On Disconnection=No
No Notify Sound=No
Notify On New Connection Timeout Value=30
Notify Dialog Caption=Remote Control
Notify Dialog Text 1=Remote Control Notification
Notify Dialog Text 2 Remote Control=The following user has connected viaremote control.
Permission Required=Yes
Center Permission Dialog=No
Permission Dialog Set Focus On Decline Button=No
Show SysTray Icon=Yes
Enable User Option Menu=No
Option Notify On New Connection=Yes
Option Notify On New Connection Dialog Timeout=Yes
Option On Disconnect Logoff Desktop=Yes
Option On Disconnect Logoff Desktop Force Applications Close=Yes
Option On Disconnect Lock Workstation=Yes
Option Logon At Logon Desktop Only=Yes
Option Logon At Logon Desktop Only Timeout=Yes
Option Enable File Transfer=Yes
Option Enable Chat=Yes
Option Enable Chat Allow Anyone To Initiate=Yes
Option Permission Required=Yes
Option Enable Add Client Connection Menu=Yes
Option Enable DisConnection Menu=Yes
Option Enable Email Notification=Yes
Option Enable Email Notification Change Email Address=Yes
Permission Required for non Admin=Yes
Permission Required for non Admin Disconnect If At Logon Desktop=No
Permission Required for non Admin Force View Only=No
On Disconnect Logoff Desktop=No
Force Applications Close=No
On Disconnect Lock Workstation=No
Logon At Logon Desktop Only=No
Logon At Logon Desktop Only Timeout=Yes
Logon At Logon Desktop Only Timeout Value=20
Enable Add Client Connection Menu=Yes
Enable Disconnection Menu=Yes
Enable Settings Menu=No
Absolute Timeout=0
Requires Explicit Remote Admin Rights=No
Allow Only Administrators To Connect=No
Requires Logon Locally Privilege=No
Must Be Member Of This Local Group=No
Local Group Name=
Must Be Member Of This Global Group=Yes
Global Group Name=DameWare Desktop Remote Control Access
Enable Email Notification=No
Email Notification Address=
Email Notification Server=
Disable Host Lookup=Yes
Socket Logon Timeout=90000
Authentication Type=2
Must Have Logon Locally Rights with Windows Logon=No
SFT: Enable Simple File Transfer=Yes
SFT: Append Host Name=No
SFT: Upload Folder=%SYSTEMROOT%\DWRCS UploadsSFT: User Response Time Out=6000
Disable Version Downgrade=No
Global Group Machine 0=[IP address of Domain Controller 1]
Global Group Machine 1=[IP address of Domain Controller 2]
Global Group Machine 2=[IP address of Domain Controller 3]
Global Group Machine 3=
Global Group Machine 4=
Global Group Machine 5=
Allow All Administrators To Have Control=Yes
Upgrade Information=
Downgrade Information=
Max Access Log Size=10240000
Force Encrypt Data=No
Force Encrypt Images=No
Force Encrypt Files=No
Configuration Version=5.5
[Proxy]
Enable Proxy=No
Require Shared Secret=No
Disable Remote Control=No
[IP Filter]
Enable Filter For Remote Control=No
Enable Filter For Proxy=No
Access Granted=Yes
Questions: Can 'Global Group Name' contain spaces and does it need to be prefixed with 'DOMAIN\' ?
Many thanks in advance
Re: Granting remote control rights to non-admins
by switbro on Wed Sep 09, 2009 6:21 pm
I am having a similiar issue - I have 45 domain controllers and have a group assigned to "Account Operators" so they can remotely access these machines with DMRC. They can access 44 of the 45 but they seem to be in view only mode on the 45th. They cannot connect even when the server is at the login window. The dwrcs.ini file looks the same as all the others, Is there a particular setting I should be looking for that would cause this behavior?
Thanks
Scott
Re: Granting remote control rights to non-admins
by abentley on Tue Sep 15, 2009 2:07 am
Hi, is anyone able to advise on this issue? Thanks
Re: Granting remote control rights to non-admins
by bryan on Fri Sep 18, 2009 1:24 pm
Exactly what error message are you receiving when you try to connect? Because it looks like everything is setup correctly. Spaces in the Global Group name should also be fine (i.e. Domain Admins).
Permission Required=Yes
- all users, even Admins, will require permission from the desktop user
- unless remote machine is at Logon Desktop or Lock Screen
Permission Required for non Admin=Yes
Permission Required for non Admin Disconnect If At Logon Desktop=No
Permission Required for non Admin Force View Only=No
- non-Admins will require permission from the desktop user, unless @ Logon Desktop or Lock Scr.
Please also look for DWMRCS entries in the Operating System's Application Event Log on theremote machine. Copy & paste the entire text from each of these entries back to our support team so they can review them. There should be at least two entries for each failed login attempt.
Once we have this information we whould be able to assist you further.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Granting remote control rights to non-admins
by abentley on Mon Sep 21, 2009 3:14 am
Thanks for the response Bryan. When any non-local admin attempts to connect they get this error immediately:
Authentication failed:
System Error: 5
System Message: Access denied
Event log entries:
CODE: SELECT ALL
Error:
DameWare Mini Remote Control
System Error: -2146893044
Failed to establish a security context. OS Error Code: [SEC_E_LOGON_DENIED] The logon attempt failed. : (srv)
CODE: SELECT ALL
Error: Failed Authentication.
Using Windows NT Challenge/Response.
Date: 09/21/2009 09:02:59
Computer Name: [computername]
User ID: [logged-in username]
Logon As ID: [login credentials username - not the same as username above]
Domain:
Desktop User ID:
Desktop Name:
System Settings Using: INI-File
Desktop State: Unknown
Permission Required: Yes
Access Approved By: N/A
Access Declined By: N/A
Access Request Timeout: N/A
Access Request Disconnected: N/A
OS Product ID: [product id]
OS Registered Owner: [registered owner]
OS Registered Organization: [registered org]
Host Name from Peer: [computername]
IP Address(es) from Peer: [ip address]
Peer Host Name:
Peer IP Address: [ip address]
Protocol Version - DWRCC.EXE: 6.800000-0.000010
Protocol Version - DWRCS.EXE: 6.800000-0.000010
Product Version - DWRCS.EXE: 6.8.1.4
Product Version - DWRCC.EXE: 6.8.1.4
Proxy Host Used: No
Proxy Host:
Proxy Destination Host:
Proxy Destination Port: 0
Proxy Callback Port: N/A
Authentication Type: NT Challenge/Response
Last Error Code: -2146893044
Last Error Code (WSA): 0
Host Port Number: 6129
Host IP Address: [ip address]
Host Name: [computer name]
Absolute timeout setting: 0 minutes
Connect/Logon timeout setting: 90000 milliseconds
AccessCheck:
Registered: No
WTS Session: No
Used RSA Public-Key Key Exchange (1024 bit keys).
Encryption IDs: 26128 (24576,1536,16) [256].
Hashing IDs: 26128 (24576,1536,16).
Used Shared Secret: No
Registration: [registration code]
Re: Granting remote control rights to non-admins
by mbernards on Tue Sep 29, 2009 4:32 am
We have added all global groups in our forests and domains with one name: UG_DWMRC
Universal groups does not seem to work here.
In those groups reside all support personal.
A tip: don't get fooled by the PDC/DC list requirement here, better use the domain names. (6 max)
let DNS find the nearest DC instead of hardwiring nodes here.
We recenly retired a bunch of old DC's and this nuked the authentication process at the clients
You have to force new settings by removing the current remote control agent and installing the new builded MSI file
The repair option does not restart the service for unknown reasons
(I am local admin, but event log says cannot find file)
I also enabled a central log server ( needs a active DWMRCS service )
Domain and enterprise administrators are also allowed to take over machines.
Works great here.
Re: Granting remote control rights to non-admins
by abentley on Wed Oct 07, 2009 5:04 am
Hi, any update on this issue from DameWare support? Thanks
Re: Granting remote control rights to non-admins
by bryan on Fri Oct 09, 2009 9:54 am
See this post for additional information:
http://forums.dameware.com/viewtopic.php?f=8&t=1189
Do those non-Admin credentials have sufficient right to login at the console of this remotemachine? In other words, can these non-Admins physically walk up to this machine and sit down at the console and use their credentials to login? If not, then they won't be able to use those credentials to connect via our software either.
SEC_E_xxxxx errors are produced by Microsoft's SSPI (Security Support Provider) interface within the O/S, which is only used when using NT Challenge/Response authentication. Our software simply passes the necessary information to Microsoft's SSPI interface and the O/S takes over and performs all authentication.
This specific SSPI Error, "Failed to establishing a security context" - SEC_E_LOGON_DENIED, implies there may be some setting within your O/S that's preventing "LAN Manager Authentication" on this machine, possibly a Policy setting (i.e. "Send NTLMv2 response only\refuse LM & NTLM" , etc.).
Therefore, you might want to try using the Encrypted Windows Logon authentication method instead. Using the Encrypted Windows Logon authentication method may resolve your issue, or it may actually generate another error message which may point us in the right direction with regard to this issue. However, presently this behavior appears to be related to some type of O/S configuration issue.
Here are some other things you can check:
- For machines in a Domain, make sure the Net Logon Service is running.
- Make sure the credentials you're using to connect do not have an expired password.
- Check your LanManager Authentication Level policy.
- Try using the Encrypted Windows Logon authentication method instead.
I hope this helps.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Granting remote control rights to non-admins
by abentley on Mon Oct 12, 2009 3:03 am
Thanks Bryan,
I did read the article above and have tried Encrypted Windows Logon before. I have just tried again on several computers and still no joy...
1. The NETLOGON server is running. Confirmed on all computers. All other domain-based authenticaion would fail without this service, so it's definitely running OK.
2. The credentials I am testing with are definitely OK. The account is not expired, locked out and does not require a password change. I can logon interactively at the console of any computer with this test account.
3. LAN Manager Authentication Level is configured using Group Policy to: Send LM & NTLM - use NTLMv2 session security if negotiated. I have also set this to 'Not Configured' so that the default Vista setting (Undefined on workstations) takes effect, this does not help either.
4. Both Windows NT Challenge Response and Encrypted Windows Logon consistently fail for all users who do not have local admin rights. I changed the 'Authentication Type' in the ini file (restarting DameWare service after each change) to 2,4 and 6 to test the different scenarios.
Here's the event log of a failed Encrypted Windows Logon attempt:
Error: Failed Authentication.
Using Encrypted Windows Logon.
CODE: SELECT ALL
Error:
DameWare Mini Remote Control
System Error: 1326
Failed to Logon User (srv)
CODE: SELECT ALL
Date: 10/12/2009 08:46:45
Computer Name: [computername]
User ID: [username]
Logon As ID: [username]
Domain:
Desktop User ID:
Desktop Name:
System Settings Using: INI-File
Desktop State: Unknown
Permission Required: Yes
Access Approved By: N/A
Access Declined By: N/A
Access Request Timeout: N/A
Access Request Disconnected: N/A
OS Product ID: 89579-236-0200203-71402
OS Registered Owner: [owner]
OS Registered Organization: [org]
Host Name from Peer: [client computer name]
IP Address(es) from Peer: [client ip address]
Peer Host Name:
Peer IP Address: [client ip address]
Protocol Version - DWRCC.EXE: 6.800000-0.000010
Protocol Version - DWRCS.EXE: 6.800000-0.000010
Product Version - DWRCS.EXE: 6.8.1.4
Product Version - DWRCC.EXE: 6.8.1.4
Proxy Host Used: No
Proxy Host:
Proxy Destination Host:
Proxy Destination Port: 0
Proxy Callback Port: N/A
Authentication Type: Encrypted Windows Logon
Last Error Code: 1326
Last Error Code (WSA): 0
Host Port Number: 6129
Host IP Address: [host ip address]
Host Name: [host computer name]
Absolute timeout setting: 0 minutes
Connect/Logon timeout setting: 90000 milliseconds
AccessCheck:
Registered: No
WTS Session: No
Used RSA Public-Key Key Exchange (1024 bit keys).
Encryption IDs: 26128 (24576,1536,16) [256].
Hashing IDs: 26128 (24576,1536,16).
Used Shared Secret: No
Registration: [reg code]
Dameware install in linux? If not, have hold map for new version for this system operation. ?
Hi All,
Does Dameware DRS also use VNC agent to remotely connect to the Windows Workstations ?
At the moment my workstations has got VNC installed and running so I wonder if I can safely uninstall it without affecting Dameware client remote assistance functionality.
Thanks.