Dameware Mini Remote Control Registry Settings
Ahmend Studioz
We just rolled out Dameware 11 (we were on 9 before). This is standalone, not the centralized server model yet. I noticed even though I used the MSI builder and configured the settings, they didn't seem to apply to everyone. For example we have just started testing removing "Domain Admins" from our IT support people and in order to still be able to use Dameware we had to push out settings for only allow these specific groups to connect to not only DOMAIN\Domain Admins, but also DOMAIN\Information Technology. At least one person's dameware was asking them for permission and even when granted we couldn't take control (view only). A few others we could not connect at all with our windows credentials unless I ran MMC as a domain admin, managed that particular computer and put Information Technology in as a local admin.
So I did some digging with Regshot and found all the settings seem to be saved at HKLM\Software\DameWare Development\Mini Remote Control Service. So I got all the settings how I want them, tested them and then exported this branch in regedit. I imported it into Dell Desktop Authority so these registry keys are imported to the PC if the dwmrc.exe file version is equal to 11.0 or greater. So far it seems to work. Are there any caveats to doing this? Again it seems to be working fine but I wanted to post it out there just as an FYI.
Dameware Remote Support (DRS) 12.2.4 and later versions feature security improvements that affect the protection mechanism of saved host credentials. As a result, you need to back up your DRS registry settings and saved hosts from previous Dameware release(s). This action is required on the first DRS launch after the upgrade from Dameware 12.2.3 or earlier versions to 12.2.4 or later versions. This is because a password-protected archive with REG and DBF files for each current Windows user is created according to the procedures explained in this topic.
You must have elevated privileges to preserve your saved host credentials in Windows Local System Authority (LSA) storage. Generally, users without administrative rights do not have credentials stored with LSA, so they will not be notified by UAC. Note that subsequent DRS launches do not require elevated privileges.
SolarWinds recommends that you create a strong password. You must then re-enter your password correctly for validation. If you do not enter it correctly in the confirmation field, you are prompted to try again.
I tried to connect with MRC 9 and got the below error. I tried again on 11 and got the same thing. Another PC with MRC is having the same issue. Other remote PCs are fine. I removed the remote service and the issue persists. Any ideas?
I am setting up Dameware 10 Remote Control Tool on a few systems and am having an issue getting connected to remote systems using my CAC. We have both admin and regular certs on the CAC but will be using the admin cert to do the remote control assistance.
After inspecting the security logs on the client system I see that the error is because its attempting to use my regular user account, not my admin account. Even tho we are running the MRC tool using admin cert credentials.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
I have an issue with the Remote option 'Show Remote Cursor' not working on many clients even though I have activated the setting under Default Host. It doesn't work even though I connect to new target PC's after the change of setting or modifying an existing client-setting.
It seems to happen when I try to use the miniremote to remote into some computers, not all remote clients. It seems to happen after a sudden disconnect or reboot of the remote machine. It doesn't matter where I do it, so it not computer/profile specific. And I can get co-workers to login to the same remote system w/o issue, so it seems to be my issue.
I can use dameware NT utilities to access all the tools for the respective computer but a soon as I try to use MiniRemote and try to login I get the error. I can use other remote desktop apps and windows RDP w/ smart card authentication w/o errors.
I've tried uninstalling and reinstalling the program on my pc, the service and drivers on the remote PC w/ Dameware software. I've tried manually adding and removing the conents %windir%\dwrcs folder on the remote system w/o issue.
I'm getting this error when trying to dial into one specific site. All the computers at this site give me the same error. I can succesfully log into all of our other sites using Dameware with Windows NT challenge response. I have confirmed that there are other users who are having this problem as well, however strangely some users can still access this site with Dameware and Windows NT challenge response no problem. I found a post on your old forums recommending adding a few lines of code into the INI file, but that must have been for an older version of Dameware that still used one, I think it all goes into the registry now. Has anyone had this issue before? If you need any more info please let me know.
I recently tried installing the Dameware Mini Remote driver onto a Windows Server 2012 machine and it continues to report back "The Operating System has reported that a reboot of the remote machine is required to complete the Mirror Driver installation/update". Once you click ok, it lets you in. But, everytime you remote in with Dameware, it pops up this message. The system has been rebooted multiple times and tried installing the driver multiple ways with no success. How do I get around this? Thanks
Yes, I just started using Dameware MRC. I created a custom MSI file to deploy. I can run the file on a workstation and it works fine.. Now I need some assistance on running that file on a remote workstation using PSexec and running it in silent mode without any assistance from the end user.
This never used to happen. Now it is happening and I cannot find any settings so I think it has to be due to something else. Let me know if there is some setting that I could change to not make it log off the remote user when I exit remote control. I already tried it without removing the service. Thanks
I'm trying to find out if the "Encrypted Windows Logon" is using Kerberos as the underlying protocol. I'm assuming the "NT Challenge/Response" is using NTLM but it would be great to know if that is the case for sure.
Second part of the question would be if there is a way to turn on Pass-Through authentication for "Encrypted Windows Logon". It grays out the check box for "Use Current Logon Credentials" when I choose it.
We have a problem on a W2K8 R2 STD server. The Dameware Mini Remote Control service is not installing automatically. All files are copied to the local folder but it seems that registry entries are missing in
The Dameware console (trying to install it) shows us an error, asking for a user and a password. After clicking cancel it gives the error "unable to install service. System Error: 5, System Messagae: Access is denied"
We have checked if the admin has all needed rights and it seems so. We have tried with a local administrator and a domain administrator. It isn't working either way. We could install it on another server with the local administrator (with identical rights), it seems that only this server has an issue.
Hi, running version 11 of remote control client, can someone post example of registry settings to turn off clipboard feature? When trying to copy and paste on a Windows 2012 R2 Server using remote client, it always crashes Server manager, this is the exception error :
Last year when we renewed our licenses we upgraded from ver 9 to version 11. I put together a Centralized server which everyone now logs into to use DameWare. However, when I tried to enter the keys into the License Activation program it wouldn't accept them and I had to open a service request to get it resolved so we could use DameWare. Earlier this year I expanded my license count, and again, when I tried to update using the License Activation program it wouldn't accept the keys so I had to open another service request.
I just upgraded to the new Version 11.2 and renewed my licensing again for another year. However, it is not reflecting in either the Server Admin Console or the Activation program. Both still show the license is only valid through the middle of next week and the Admin Console comes up w/ warnings that there is only 7 days left. When I click the "I Already Paid" button in the warning it just opens the web page for me to sign into. I found the License Manager out there and downloaded it. I ran the sync on that and it comes back fine, shows that I'm good through next year. Still not updating in the Admin console. I can enter the keys from my info on the customer portal in the Activation program and at least it shows that it takes them - used to always fail. However, the dates are still showing that my licensing is about to expire.
I'm running 5.5.0.2 on a bunch of windows xp stations but we added a new one that is windows 7. When remoting into that station all I get is a black screen but if I use Windows remote desktop simultaneously Dameware will begin to function properly.
We are in the process of migrating to Dameware RS and MRC from Teamviewer. We are having a number of issues during testing that I don't really want to be landing on the support desk as its going to make a hard job harder for them.
Namely issues arise around Internet sessions. The thing is we support around 75 companies, all separate, and range in size from 5 to 100 users. Getting Dameware agent client on all those systems just isn't plausible, so the Internet session option makes full sense.
Certificate Error - Have installed a GoDaddy SSL certificate on the Internet Proxy, and it does present the certificate to the end user, but its still saying the site/certificate can't be verified, even though the URL etc. all square up.
c80f0f1006