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.

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

Hotfix 1 addresses the following issues:

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

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

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

Now go and download the hotfix now.

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.

Global domain group access
by Verrry on Thu May 15, 2008 1:59 am

Good day!
During testing DNTU v.6.7.0.9 I have collided with a following problem: When i check the option "Must be member of this global group" in Access tab, i can login into remote machine only if there is a "logon screen" (locked or not logged in). When the user on remote machine logged in locally the mistake stands out: "The remote system is not currently at the Logon Desktop. Your credentials do not allow for access at the current desktop state. Please contact your Administrator for more information"
At Access tab no other options are checked.
At General tab only next options are checked: "Allow Windows NT Challenge/Response" and "Allow Encrypted Windows Logon"
At Additional setting tab no one option is checked.
The idea was to permit use DNTU only members of the global domain group.
How can i provide access only to members of the global domain group and not only from "logon screen"?

Re: Global domain group access
by bryan on Thu May 15, 2008 2:27 pm

Hello Verrry,

This specific message "The remote system is not currently at the Logon Desktop. Your credentials do not allow for access at the current desktop state" is not related to using a Local or Global Group. It has to do with what rights these users have within the O/S security on the remote machine.

Most likely these users do not have Admin rights within the O/S security on this remote machine, and you also disabled the "Permission Required for these Account Types" setting, at the bottom of the Access Tab.

Non-Admins will always require explicit permission from the Desktop User before they can connect, but if you turn off the "Permission Required for these Account Types" setting, then any non-Admin will simply be denied access to this machine, without even prompting the Desktop user to Accept their connection.

I hope this helps.

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

Re: Global domain group access
by Verrry on Fri May 16, 2008 2:10 am

Well, thanks Bryan for your answer.
I understand, that if user wants to connect to remote host, he must be a member of the local administrator group or must ask the permission on local user to login.
But in case the security service wishes to look silently the remote desktop, there is no ways to provide them this ability without adding to local admin group.
And for what global groups are in that case used?

Re: Global domain group access
by bryan on Fri May 16, 2008 11:49 am

Hi Verrry,

When a remote machine is not at the Logon Desktop or Lock screen, in order to connect without requiring explicit permission from the Desktop User then you must have Administrator rights within the O/S security on that machine. Otherwise if you don't have Administrator rights, then you will require permission before you can connect.

The only other possible work-around (to allow non-Admins to connect without requiring explicit permission) I can think of and I don’t necessarily recommend it, would be to allow these users to connect via the Proprietary Challenge/Response authentication method instead. This method of authentication used a fictitious hard-coded UserID & Password instead of your O/S credentials.

I hope this helps.

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

Re: Global domain group access
by TheCat on Fri May 08, 2009 9:07 am

Well i guess that answers my question !

But why would i be able to configure such a setup to only find out through support (not even with a correct error message) that this configuration is useless ?

Seriously, you can make your local group setup and all, but still cannot get it to work because your not a local admin.

I dont know about you, but if i setup a "must be in this localgroup", it's obvious that's because i dont want them to be local admin group... If i do not allow an admin to have remote access with dameware, they will just logon locally and setup their account to use remote desktop (as they have the right to do so as admin...)

Right now we're working on the PCI-DSS certification, so i ended up removing all level 1 tech admin rights to our POS system, giving them appropriate "power user" rights.

Part of there jobs, require them to logon remotly to remote pc's without having to ask for permission (as they sometimes work off-hours, or on call when there is no one to answer the connection request). For the PCI-DSS requirement, i cannot give them a generic username/password. Even you folks dont recommand me to use such a settings.

Sorry... i guess i'm just a little mad that i just spent the last 2 hours trying to figure out what went wrong, thinking i had the right config setup (and according to the setting description i had) but to find out later that this is a normal behavior. You can set it up, but it will not work... wow...   

It's like telling you i build you a car, gave you the key to it, tell you to go pick me something with that car. But when you'll hit the "start engine" it wont work and it's normal because your not the car owner...

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

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

Hello,
Over the last few days I have been trying to get Windows PE to run Dameware.
What I have done is install the client onto a base PC, copy off the drivers I think are required (below) copying them to PE in X:\Windows\System32\ and then started DWRCS.exe - install /-service.

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

I can ping the PC with PE (firewall switched off on both computers) and it authenticates and it even tells me the keyboard set is in a different language but it then gets stuck on "initializing desktop, please wait"

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

Many Thanks!

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

Bump...
Anyone have any ideas at all?

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

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

Also, since my last posting there, I found a somewhat simplier way to do things. Use the "DameWare Mini Remote Package Builder" to build an MSI, including configuration for Proprietary Challenge/Response, then extract that resulting .MSI with 7-Zip, and then within there, you will find a Cabs.dwrcs.cab. Extract that to your WinPE's \windows\system32 folder. That contains everything you need to run the client. Lastly, you will need to add a line to run "\windows\system32\DWRCS.EXE -install" within WPEINIT.

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

dcc

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

mmm...thanks for info

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

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

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

Thanks for your help so far!

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

Any Ideas

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

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

dcc

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

Thanks for that...
At least I know I'm not being stupid now if someone else can replicate the issue I have.
It's as shame as I'm sure it's something fairly simple to fix as it's -almost- working....
Anyone from Dameware - Are you reading ?

Re: Damware Remote on Windows PE?
by guy on Wed May 12, 2010 7:56 am
Just to update further.... It seems that becuase Dameware required Terminal Services this will never work....
PE is just too stripped down to allow anything like this to work 
I guess it's time to look at an open source application for PE.... 

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

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

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

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

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

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

dcc

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

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

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

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

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.

Windows 7 - Cannot End Process
by laurin1 on Fri Dec 18, 2009 4:03 pm

When I attempt to do this, I get an error:

Failed to terminate process: iexplore [4016]
System Error: 2
System Message:
The system cannot find the file specified.

This occurs with all processes.

Re: Windows 7 - Cannot End Process
by laurin1 on Fri Dec 18, 2009 4:09 pm

I just realized the problem is the NT Utilities service is not running. I tried to start it and the service fails:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 12/18/2009
Time: 3:08:03 PM
User: N/A
Computer: KDAVIS.pridedallas.com
Description:
The DameWare NT Utilities 2.6 service failed to start due to the following error:
%%2

For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

Data:

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 3:06 pm

Hi laurin1,

"System Errors" are actually Microsoft Operating System Errors, not DameWare Errors, and a “System Error: 2" basically means that a required file was not found, therefore, the Service was unable to start. Please make sure all the necessary files are located in the System32 folder on the remote machine (SYSWOW64 folder for 64-bit).

The files for the Client Agent Service are:

DWRCS.EXE
DWRCS.INI (may or may not be there)
DWRCK.DLL
DWRCSET.DLL
DWRCST.EXE
DWRCShell.DLX (or .DLL) (or DWRCSh32 for newer versions) DWRCShell64.DLX (or DLL) (only on 64-bit systems) (DWRCSH64 for newer versions)

If you do find that some of these files are missing from the System32 folder on the remote machine, then I would suggest you check within any type of AntiVirus, AntiSpyware, or Security type software you have installed on your machines, or on the network. This error is typically related to some type of false positive detection, which means all you should have to do is create an exception in this other software.

I hope this helps.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by laurin1 on Mon Dec 28, 2009 3:11 pm

I understand all ofthat, however, we have not had this problem until we started using DW on our Windows 7 machines (all are 64 bit.)

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 3:21 pm

Hi laurin1,

Are you using the latest release (6.8.1.4)? If not, please try to duplicate this behavior in the latest release.

However, regardless of which O/S you are using, this system error indicates that the issue is with your anti-virus/anti-spyware preventing the client agent service from starting, usually because it has blocked or deleted one of the necessary files. For the NT Utilities client agent, it is actually just one file (DNTUS26.EXE).

You should be able to create or define an exception in your security software to resolve this problem. Also, I would recommend trying a manual install of the client agent service per the following directions:

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

I hope this helps.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by laurin1 on Mon Dec 28, 2009 3:45 pm

Ijust checked and DNTUS26.EXE file is not in the SYSWOW64 folder, but it's in the System32 folder. I disagree with your analysis. I do not think the Antivirus software is the culprit here. I am going to do some testing to find out for sure. I copied the DNTUS26.EXE into the SYSWOW64 folder, but that had no effect (same errorr.) I will try an exception as well for the AV.

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 3:51 pm

Hi laurin1,

Let us know how it works out.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by laurin1 on Mon Dec 28, 2009 3:55 pm

AV exception did not work. I believe whatever process you call use to call the service cannot find the file and here's why:

We've had some of the same problems with 32 bit applications on Windows 7 64 Bit not installing their files in the correct folder, or not installing the registry settings in the correct location.

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 4:03 pm

Hi laurin1,

Please send an email to support@dameware.com and include the following information:

What version of the software are you using?
What type of antivirus/antispyware do you have installed on your local machine and the remote machine?
If Windows 7 is the remote machine's O/S, what is the O/S on your local machine?

Thanks.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by balbright on Thu Dec 30, 2010 11:21 am

I am having the same problem on Windows 7 64 bit boxes. I would like to know the resolution once one is found.

We are using Dameware version 6.9.0.4.

Re: Windows 7 - Cannot End Process
by laurin1 on Thu Dec 30, 2010 11:50 am

6.9.0.04 fixed the problem for us.

Let the community know how impressed you are with DameWare Remote Support and earn a $25 Amazon gift card!  Simply post your review in Spread The Word with the questions answered below:

1.       What was life like before using SolarWinds? (Include what you were using and why you decided it was time for a change)
2.        Which SolarWinds product(s) saved your bacon?
3.        Did you consider other options, and why did you choose SolarWinds?
4.       How has life been since you've rolled out SolarWinds in your environment?

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

Thanks in advance for any help!

We are taking over a couple other companies.  One of those also uses Dameware.  Currently they have 8 licenses and we have 13.  I'm not sure of their setup yet, if they are running stand-alone or if they have a centralized server like I have set up for us.  When I take ownership of their licenses, will I be able to create a centralized server for them that will tie into my current server and I can manage all the licenses together or will I need to keep them on a separate license key?

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

We recently replaced our domain controller which was running Windows server 2003 and replaced it with Windows Server 2012 at one site. After that change, I noticed that all the workstations from that site, Damware does not show as active. However, If I select one that I know its online, I am able to remote in with no problem with Dameware including RDP. I do noticed after 15 or 20 minutes, Dameware starts to show that group of PCs as a blue icon instead of the green icons at least for those pc that are on the network. It feels like its a browsing issue because when I click on Network, it does not show those computer in which they are on the network.

Hello DameWare users!

Here is a brief guide to shows how to gather information from computers in your network or domain using the DameWare Exporter tool included with DameWare Remote Support.

Objectives:

1- Get "Installed Software" data from computers in my network to create a report.

2- Get the information in a CSV file format so it can be easily imported into an Excel spreadsheet

3- Get the information from several computers in a single file

First, you have to launch the tool. You can find it in the same location as the main DameWare Remote Support application (Start > Programs > SolarWinds > DameWare Remote Support 9.0 > DameWare Exporter). You can recognize it easily by the colors in the icon (blue/yellow) :

In the Exporter tool you must change the settings so the files created have the CSV format instead of XML (which is used by default). In this example we want to get "Standard" information (which basically means we are pulling data from the machine instead of Active Directory) so that's the tab we need to modify:

NOTE: The "Single File" option here indicates that a single file will be made per-machine including all properties selected. It DOES NOT mean a single file will include each computer.

Once the output file type is set, do the following:

1- Under "Task List" uncheck everything except for Standard Properties - Software.

2- Click the "Add Machines" button to include the computers you want to survey.

3- Make sure all the systems in the "Computer List" are checked

4 - Click on "Start Exporting"

After this you will end up with a .csv file for each computer you surveyed. Unfortunately, DameWare Exporter doesn't feature an option to generate a single file for all the computers. However,  CSV files are easily merged using the Windows copy command. Place all the files in the same folder and run the following command in the Command Prompt:

copy *.csv allcomputers.csv

This line will create a new file, "allcomputers.csv" (you may use the name of your choice) that will be a merging of all .csv files found in that folder.

We are are Mac based company and have recently acquired 200 Windows 8 machines.  Rather than get a server I opted for Dameware Remote Support.  I've used Dameware in the past in its early stages.  I'm having trouble pushing out an install the the Windows 8 machines.  I'm trying to push the install from a Windows 7 machine out.  I'm under a super tight deadline so I've not much time to trouble shoot this.

If possible change standalone client of DRS to client / server version?

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.

We are busily working on the next release and among many things we are looking at, there are also unattended internet sessions!

If you would like to influence this feature and Dameware in general and if you are interested in this particular feature, go ahead and sign-up for beta now!

Please note this Beta is NOT suitable for production environment and you need a separate test system.

This Beta is focused on small, but high quality feedback and you will be rewarded by crazy number of Thwack points!   First come, first served!

After you sign up and confirm Beta agreement, I will contact you shortly,

Peter

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:

• Over the Internet (OTI) unattended sessions for Dameware Centralized users
  • Allows you to remotely support users on the move, and assist remotely without the presence of the end user
  • Deploy agents with OTI unattended support to end-points
  • Manage agents for OTI unattended sessions to maintain high security and control
• Search Hosts in Mini Remote Control
• Support for Windows 10
• Ability to switch between the Standalone and Centralized versions without reinstallation
• And many other improvements and bug fixes

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!

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

Hotfix 1 addresses the following issues:

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

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

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

Now go and download the hotfix now.

Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out.  I can't get it reinstalled - keep getting the message   "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.".

So far, I've tried:

• Re-downloading the zipped installation files
• Installing to a different directory
• Rebooting
• Removing the \Program Data\Solarwinds files
• repairing my .net installation

I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs.  I can see two DRS10... processes running in task manager, but they never do anything.

Not sure what to try next.

Ideas?

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 am new to Dameware and have found the install/configuration very frustrating.  I have called support three times in the process (last call was 2 hours), so now I will try this forum.

I got the server setup and want to deploy DRS to the techs.  I found a link to this kb on using the msi to install, but I do not see the msi - only the exe (the kb was for ver 9.)

In order to keep working I just installed DRS with the gui but then it prompts me for the license (which is fine), BUT it does not give the option of pointing the install to the central server to get the license.

Can someone provide guidance?  I have read the install manuals but they do not seem to be oriented to an enterprise admin.  Really an Getting started / best practice document would be helpful to someone new to the product.

Thanks.