When I try to use the "display user logon/logoff information" I receive an error:  "Failed to Get User Information.  System Error:2814 System Message: The service has not been started:" 

Hi All,

Currently evaluating Dameware DRS 11.0.0.1003 for our environment. In past employments I have relied heavily on Dameware for my Team's support operations. I was hoping to employ this tool here in my current role, but I have come across something that may be a deal breaker. The majority(about 2/3) of our staff here use WYSE terminals and login to a session on our Terminal Servers (WIndows 2008 R2). We have been connecting via RDC to the Terminal Server, login then using the TS Admin Tools launch a remote session to the Staff member. I was hoping to use Dameware DRS to actively connected to the session directly. Does anyone know if this is possible and if so how?

Many thanks.

Logan

Can I uninstall software remotely from the DRS interface?  Looked for a "how to", but could not find.  I'd like to uninstall unneeded software from remote computers without logging into them at a specified time.  I am a network admin and have an admin acct. on most of the remote computers.  Thanks.

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.

Computer Comments no longer appear
by Brachus on Thu Apr 30, 2009 7:00 am

We recently upgraded our domain controllers to Server 2008. However, after doing so, DameWare has stopped showing the Computer Comments for the Workstations.
If we right click, go to tools and then computer comments, the information is still there. When we hit OK, it appears next to the workstation as before, but only temporarily. If we restart the program, or even just collapse the Workstations tree, then expand again, they are lost.

Brachus
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Mon May 18, 2009 3:42 am

Hello!

Did you find a solution ? cause we got exactly the same problem yet!

Before we had a 2003 Server for secondary controller and it works and now I ugrade it to 2008 and all comment are lost!

If you go to tools computers comments it comes but only for the session when you close dameware it lose comments again!

I try to put it in Active Directory computer comments but not way to see it in Dameware

Today I update to 6.1.8.5 but still going wrong

Is the support knowing that problem ? any idea how to resolve it ?

We are very frustrating here cause a lot of computer and the name are not really comprensible so we have to lool all the time and search for...

Take a lot of time

Please remedy to that soon as possible or we will change to another software!

Thanks

Kevin
________________________________________
Re: Computer Comments no longer appear
by KarbonKopy on Tue May 19, 2009 12:01 pm

I too had the same problem when I migrated to a 2008 DC. It seems to work randomly, even with testing the AD computer names doesn't seem to make a difference. On a side note where did you get 6.8.1.5? I only see .4 on the download page.
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Wed May 20, 2009 2:22 am

Hello

Sorry for the mistake, yes you right I've the same version as you...

What I see today is if you put any computer in favorite machines IT WORKS!!!!

So now I'm sure it's coming from Dameware software!!!

Is there any dameware technician who read forum ? can you debug it for the next version cause a lot of people will migrate to W2K8 and I think it's really easy to solve for you!

thanks

Kevin
________________________________________
Re: Computer Comments no longer appear
by jfor26 on Thu Jun 04, 2009 2:36 pm

we have the same problem. I dont think they check this place regularly at all. we are looking at a different package for remote admin

http://www.pjtec.com Their Goverlan suite.
________________________________________
Re: Computer Comments no longer appear
by Marty on Thu Jun 11, 2009 3:12 pm

Hi guys,

With regards to Computer Comments and potentially having them displayed, DNTU has the ability to retrieve & display Computer Comments. However, understand that "Comments" are handled & maintained in many different ways (i.e. Local Machine, Windows Network Browser, Domain Controller, Active Directory, etc.) within the O/S itself, and even within the NT Utilities software.

DNTU's Active Directory section will always look to Active Directory to find the Computer Comments. Whereas, DNTU's Microsoft Network section, DNTU's Favorite Machines (formerly non-Browsable) section, and even the Tools / Computer Comments tool (and previous 4.x versions as well) always look to the local machine for the Computer Comments (i.e. Computer Description).

Therefore, if you want the Computer Comments to appear all the time under DNTU's Active Directory browser, you must add the Comments within Active Directory. This is why they appear temporarily, but then disappear when you close and restart, because DNTU once again looks to AD for them. This can also be done via DNTU within the Active Directory browser by right-clicking on the machine in the Tree View (left-hand pane), then selecting Properties, then make the necessary changes in the Description field (which are the AD comments).

If you wish for the Computer Comments to be displayed in parenthesis behind the Computer in the Favorite Machines (formerly non-Browsable) portion of DNTU or the Microsoft Windows Network section, then you would basically modify the Comments directly on the remote machine (right-click My Computer / Properties / Computer Name Tab). This can also be done via DNTU by selecting Tools / Computer Comments, which will actually retrieve & modify the Comments/Description on the actual remote machine.

I hope this helps.
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: Computer Comments no longer appear
by bryan on Fri Jun 12, 2009 10:55 am

What I see today is if you put any computer in favorite machines IT WORKS!!!!

If this is the case then these Comments are actually stored directly on the remote machine itself (i.e. Computer Description), not in Microsoft's Windows Network Browser (i.e. NT Browser). DNTU's Favorite machines list and the Tools / Computer Comments feature retrieve the Comments directly from the remote machine itself, and these Comments will not be dynamically shown in Microsoft's Windows Network Browser.

The Microsoft Windows Network Browser portion of DNTU retrieves the information from Microsoft's Network Browser (i.e. Network Neighborhood, My Network Places) which is part of your O/S & network itself (i.e. the Master Browser). We simply ask your O/S on your local machine for it's Windows Network Browser information, and then we display what's returned back to us. This information is not modified in any way.

When using the Microsoft Windows Network portion of the Browser in our software, DNTU will not attempt to contact the machine directly to retrieve this information (like it does in Favorite Machines), because all the relavent information should already be in Microsoft's Browser. Whatever information is populated within Microsoft's Network Browser itself is the information that DNTU will display in this section of the software.

Microsoft has also documented known issues with NetBios Browsing in Server 2008 (see below).

NetBIOS Browsing and Windows Server 2008 x64 Server Core
http://blogs.technet.com/networking/archive/2008/12/16/netbios-browsing-and-windows-server-2008-x64-server-core.aspx

NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008
http://blogs.technet.com/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx

Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: Computer Comments no longer appear
by Brachus on Mon Jun 15, 2009 8:10 am

Thanks for the information Bryan. This was more helpful than a copy and paste from the manual when we were trying to explain that the MS Network Browser comments stopped working despite all settings being correct.
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Thu Jun 25, 2009 7:52 am

Hello

Sorry you don't really understood what everybody wants

Sure now it's clear how it work's but what we want and I found the solution

It's to see directly computer comments in microsoft windows network

For make it simple directly when we open dameware, cause if you use it all time it's very slow to go each time in the AD, find the good "OU" and so on...

Now if you have the same issue as mine

First go to network neighberhood with a client in XP (not working with vista) and see if there's comment behind computer

If not do theses things

In Windows 2008 and AD environnement without other 2003 server you simply have to disable Computer Brower service in the DC

After little time every comments will be appears again

If you still have Win2003 server you can also transfer Master browser to it and it works!

Thanks to all for your help
________________________________________
Re: Computer Comments no longer appear
by Abbala on Fri Dec 11, 2009 2:13 am

Thanks for taking the time to help, I really apprciate it.

------------------------------------------------------------------
Re: Computer Comments no longer appear
by Marx7 on Wed Jul 07, 2010 10:05 am

I was still a little unclear on how to fix this issue on my network after reading through this discussion, but understood that the master browser was somehow the issue, so I started looking into how to find the master browser. I found the following page that explains very easily how to find your master browser: http://www.ifrankie.com/?p=45 It talks about using XP SP2 support tools, which I found here: http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en I followed the instructions from ifrankie and found that the computer that was the master browser was an XP box that had been on and sitting idle for about 2 months. I rebooted that computer, and everything started working again as a different computer became the master browser.
This is what worked for me. I hope it helps others.

-------------------------------
Debt is normal. Be weird.

Good afternoon,

    I have an administrative token/ smart card that is required to be used when logging into workstations.  I am able to use this to log on remotely to workstations with DameWare.  I am able to open DameWare with the credentials, but when I remote to a machine, it does not see the token credentials.  I have been unable to find any documentation to assist with this.  Can anyone point me in the right direction?

Thanks,

  Craig

I recently upgraded to Windows 10 and DRS 12. Since then I have been getting this in the information tab. On the Browser tab I don't get anything under the Microsoft Windows Network like I used to.

I am new to this forum and trying to search didn't seem to bring anything up. I appreciate any help anyone can be as I don't think I am getting full usage of DRS 12 because of this issue.

Thank You.

When I connect to a Surface Book with Windows 10 1709 installed Dameware doesn't recognize multiple monitors.

All of our systems are Surface Pro 3 / Surface books. Plugged into Surface Docks.

When I connect to the Pro 3's with Win8.1 I can see all three screens.

When I connect to the Pro 3's with Win10-1709 I can see all three screens.

When I connect to the Surface Books with Win10-1607 I can see all three screens.

When I connect to the Surface Books with Win10-1709 I cannot see all three screens.

I am in the process of rolling out 1709 to everything and this is going to become a huge issue really soon. This is in addition to the performance issues with Dameware on 1709.

Hi,

When establishing a DameWare Internet Session, was requested to download the Remote Agent Deployment package. McAfee detected it as a virus and immediately deleted it. Please advise.

Thanks and regards

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,

i'm currently testing dameware central as my main remote system.

I was happy to see that you guys now support remote hosts through a secured internet proxy i can host on my end ! Specially with the unattended access with version 12

After setting up everything in my test environment, and testing the addition of remote hosts from home and multiple sites, i was a bit disappointed that the file transfer was simply... not available ? Did i miss something ? did i forget to open up a port ?

Or is this really not available through internet proxy connection !? If so, is this planned in a very near future version !?

I am currently evaluating where dameware is now vs TeamViewer when it comes to behind NAT connection, ease of use for the staff, pricing and features...

Now although i'm amazed where dameware is now compared to previous version (I have been using dameware since version 4 on internal network at one of my customer's site). I cannot tell my staff that from now on, we'll have to go through more steps (like an FTP or Cloud storage...) to transfer files on the remote system as opposed to a simple, drag and drop

Can I uninstall software remotely from the DRS interface?  Looked for a "how to", but could not find.  I'd like to uninstall unneeded software from remote computers without logging into them at a specified time.  I am a network admin and have an admin acct. on most of the remote computers.  Thanks.

We are currently testing deployment of Dameware Mini Remote Control to the client systems.

With the previous version (11.1), we were able to add a new line to the registry location [HKEY_LOCAL_MACHINE\Software\DameWare Development\Mini Remote Control Service\Settings]

"UseCurrentLogonCredentials"=dword:00000001

This would automatically select 'Windows NT Challenge/Response' and check the 'Use Current Logon Credentials'

This is not seems to be the case with the new version 11.2. When I add the link, nothing seems to happen.

Can anyone suggest solution?

Thanks.

I’m happy to announce that DameWare 12.1 is now publicly available.

This release brings several improvements, namely:

• New Mirror Driver -  Customers connecting to Windows^® 10 can now use the brand-new mirror driver. Additionally, DameWare 12.1 now supports 4K monitor resolution and adds support for Java^® and DirectX^® Apps, allowing you to interact with high resolution displays and modern apps.
• TLS1.2 support - which can help ensure the safe transfer of real-time data. TLS 1.2 adheres to PCI and HIPAA industry requirements.
• Refreshed UI -  New, refreshed icons for DameWare Remote Support and Mini Remote Control update the look and feel of both DameWare products.

DameWare 12.1 is available for download on your customer portal for those customers under current maintenance.

If you are not a DameWare user yet, now go anddownload new version from www.dameware.com now!

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.

Computer Comments no longer appear
by Brachus on Thu Apr 30, 2009 7:00 am

We recently upgraded our domain controllers to Server 2008. However, after doing so, DameWare has stopped showing the Computer Comments for the Workstations.
If we right click, go to tools and then computer comments, the information is still there. When we hit OK, it appears next to the workstation as before, but only temporarily. If we restart the program, or even just collapse the Workstations tree, then expand again, they are lost.

Brachus
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Mon May 18, 2009 3:42 am

Hello!

Did you find a solution ? cause we got exactly the same problem yet!

Before we had a 2003 Server for secondary controller and it works and now I ugrade it to 2008 and all comment are lost!

If you go to tools computers comments it comes but only for the session when you close dameware it lose comments again!

I try to put it in Active Directory computer comments but not way to see it in Dameware

Today I update to 6.1.8.5 but still going wrong

Is the support knowing that problem ? any idea how to resolve it ?

We are very frustrating here cause a lot of computer and the name are not really comprensible so we have to lool all the time and search for...

Take a lot of time

Please remedy to that soon as possible or we will change to another software!

Thanks

Kevin
________________________________________
Re: Computer Comments no longer appear
by KarbonKopy on Tue May 19, 2009 12:01 pm

I too had the same problem when I migrated to a 2008 DC. It seems to work randomly, even with testing the AD computer names doesn't seem to make a difference. On a side note where did you get 6.8.1.5? I only see .4 on the download page.
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Wed May 20, 2009 2:22 am

Hello

Sorry for the mistake, yes you right I've the same version as you...

What I see today is if you put any computer in favorite machines IT WORKS!!!!

So now I'm sure it's coming from Dameware software!!!

Is there any dameware technician who read forum ? can you debug it for the next version cause a lot of people will migrate to W2K8 and I think it's really easy to solve for you!

thanks

Kevin
________________________________________
Re: Computer Comments no longer appear
by jfor26 on Thu Jun 04, 2009 2:36 pm

we have the same problem. I dont think they check this place regularly at all. we are looking at a different package for remote admin

http://www.pjtec.com Their Goverlan suite.
________________________________________
Re: Computer Comments no longer appear
by Marty on Thu Jun 11, 2009 3:12 pm

Hi guys,

With regards to Computer Comments and potentially having them displayed, DNTU has the ability to retrieve & display Computer Comments. However, understand that "Comments" are handled & maintained in many different ways (i.e. Local Machine, Windows Network Browser, Domain Controller, Active Directory, etc.) within the O/S itself, and even within the NT Utilities software.

DNTU's Active Directory section will always look to Active Directory to find the Computer Comments. Whereas, DNTU's Microsoft Network section, DNTU's Favorite Machines (formerly non-Browsable) section, and even the Tools / Computer Comments tool (and previous 4.x versions as well) always look to the local machine for the Computer Comments (i.e. Computer Description).

Therefore, if you want the Computer Comments to appear all the time under DNTU's Active Directory browser, you must add the Comments within Active Directory. This is why they appear temporarily, but then disappear when you close and restart, because DNTU once again looks to AD for them. This can also be done via DNTU within the Active Directory browser by right-clicking on the machine in the Tree View (left-hand pane), then selecting Properties, then make the necessary changes in the Description field (which are the AD comments).

If you wish for the Computer Comments to be displayed in parenthesis behind the Computer in the Favorite Machines (formerly non-Browsable) portion of DNTU or the Microsoft Windows Network section, then you would basically modify the Comments directly on the remote machine (right-click My Computer / Properties / Computer Name Tab). This can also be done via DNTU by selecting Tools / Computer Comments, which will actually retrieve & modify the Comments/Description on the actual remote machine.

I hope this helps.
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: Computer Comments no longer appear
by bryan on Fri Jun 12, 2009 10:55 am

What I see today is if you put any computer in favorite machines IT WORKS!!!!

If this is the case then these Comments are actually stored directly on the remote machine itself (i.e. Computer Description), not in Microsoft's Windows Network Browser (i.e. NT Browser). DNTU's Favorite machines list and the Tools / Computer Comments feature retrieve the Comments directly from the remote machine itself, and these Comments will not be dynamically shown in Microsoft's Windows Network Browser.

The Microsoft Windows Network Browser portion of DNTU retrieves the information from Microsoft's Network Browser (i.e. Network Neighborhood, My Network Places) which is part of your O/S & network itself (i.e. the Master Browser). We simply ask your O/S on your local machine for it's Windows Network Browser information, and then we display what's returned back to us. This information is not modified in any way.

When using the Microsoft Windows Network portion of the Browser in our software, DNTU will not attempt to contact the machine directly to retrieve this information (like it does in Favorite Machines), because all the relavent information should already be in Microsoft's Browser. Whatever information is populated within Microsoft's Network Browser itself is the information that DNTU will display in this section of the software.

Microsoft has also documented known issues with NetBios Browsing in Server 2008 (see below).

NetBIOS Browsing and Windows Server 2008 x64 Server Core
http://blogs.technet.com/networking/archive/2008/12/16/netbios-browsing-and-windows-server-2008-x64-server-core.aspx

NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008
http://blogs.technet.com/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx

Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

________________________________________
Re: Computer Comments no longer appear
by Brachus on Mon Jun 15, 2009 8:10 am

Thanks for the information Bryan. This was more helpful than a copy and paste from the manual when we were trying to explain that the MS Network Browser comments stopped working despite all settings being correct.
________________________________________
Re: Computer Comments no longer appear
by kfluckiger on Thu Jun 25, 2009 7:52 am

Hello

Sorry you don't really understood what everybody wants

Sure now it's clear how it work's but what we want and I found the solution

It's to see directly computer comments in microsoft windows network

For make it simple directly when we open dameware, cause if you use it all time it's very slow to go each time in the AD, find the good "OU" and so on...

Now if you have the same issue as mine

First go to network neighberhood with a client in XP (not working with vista) and see if there's comment behind computer

If not do theses things

In Windows 2008 and AD environnement without other 2003 server you simply have to disable Computer Brower service in the DC

After little time every comments will be appears again

If you still have Win2003 server you can also transfer Master browser to it and it works!

Thanks to all for your help
________________________________________
Re: Computer Comments no longer appear
by Abbala on Fri Dec 11, 2009 2:13 am

Thanks for taking the time to help, I really apprciate it.

------------------------------------------------------------------
Re: Computer Comments no longer appear
by Marx7 on Wed Jul 07, 2010 10:05 am

I was still a little unclear on how to fix this issue on my network after reading through this discussion, but understood that the master browser was somehow the issue, so I started looking into how to find the master browser. I found the following page that explains very easily how to find your master browser: http://www.ifrankie.com/?p=45 It talks about using XP SP2 support tools, which I found here: http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en I followed the instructions from ifrankie and found that the computer that was the master browser was an XP box that had been on and sitting idle for about 2 months. I rebooted that computer, and everything started working again as a different computer became the master browser.
This is what worked for me. I hope it helps others.

-------------------------------
Debt is normal. Be weird.

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.

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]

Can anyone help us. We are running dameware version 12.0.0.509 and when we remote into a Windows 10 Device (1703) and its at the login screen it is extremely slow to respond. Once we get logged in its fine however the login screen is extremely slow. How can we fix this.

I have a couple Windows 10 computers that when I remote to them, as soon as I even move the mouse to do anything, the desktop locks and I have to have the user unlock it.  Then as soon as I try to do something again, it locks up the desktop again.  It's a never ending cycle.

I have uninstalled and re-installed the Dameware client on the machines a couple of times, but it still isn't working.

Any ideas?

Dameware 12.0.4 via a Centralized Server

We have a license for DW 9 and been using it for many years. No one can remember when and how it was bought.

But now we faced a problem: if technician is logged on using his account from another domain than DW says there is no license. Does DW license binds to local domain name?

How can we check it? How can we make it work in another domain?

To be clear:

One administrator's PC. DW 9 installed with license key for all users. Windows 2012 R2.

User1: user1@domain1.lan - license works

User2: user2@domain2.lan - license does not work.

Any help will be appreciated.

Thanks in advance.

I just recently upgraded one of my work PC's HDD to a SSD and now my dameware shows eval mode and when I enter the license it states not valid. Is there a fix for this?