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

Hi,

we've enabled Microsoft's Security Baseline via GPO to our Windows 10 computers. If we now like to use dameware 12 to  remote control a computer the authentication is not working through.

No matter which protocol from the dropdown list (Windows NT Challange / Response, Encrypted Windows Logon, ...)  is used it all fails.

Somebody meet this situation and knows what to do? Is there a configuration in dameware that can be changed to work with the basline or did u change a setting on the baselines?

Windows Security Baselines | Microsoft Docs

I have checked the application log of the remote machine and found these events:

I know that NTLM version 1 is deactivated via Security Basline, but I assume Damware is using Version 2?

Thanks in advance

Ruben

Hi,

We try to subscribe to Dameware 12.1 Beta, but we have an error message, while our license is active.

It appears you do not have a license for DameWare Mini Remote Control, or you are no longer under active maintenance. In order to participate in the Dameware 12.1 Beta 1 Beta program, customers need to ensure their license(s) are under active maintenance. If you feel this is a mistake, please contact customersales@solarwinds.com.

We have several problem with Remote Support and Windows 10 1709.

Thanks you.

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.

Your logon request was declined. Disconnecting...
by fabvit on Fri Jan 14, 2011 4:23 am

I'm using the invitation mechanism in DWMRCS v7.

I've noticed that if I leave checked the Require Permission while creating an invitation, later on when I try to connect to this machine I got a dialog:

Your logon request was declined.
Disconnecting...
Request for permission to remote control encountered an error.
- [0]

If I remove the check from Require Permission while creating an invitation, later I can connect to this machine.

What is the purpose and how to setup the Require Permission mechanism.
--
tanks, fabio

Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 3:47 pm

Thanks very much for your feedback on this.

We were able to reproduce this issue and we should have it fixed shortly.

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

Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 5:51 pm

Hello Fabio,

We wanted to let you know we just finished updating all the files on our website. Since this is only a minor update, you will have to remove the old MRC Client Agent from your remote machine, then remove your current MRC v7 install on your local machine. Next, download and install the most current files from our website. Then you can reinstall this newer Client Agent Service onyour remote machine.

Your feedback is appreciated.

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

Re: Your logon request was declined. Disconnecting...
by Siggi on Wed Feb 23, 2011 4:22 am

I have the same problem while trying to connect to one specific client running Windows 7 x64. After a few seconds I get the message "Your logon request was declined", but there was norequest shown on the users screen.

I'm running DameWare Mini Remote Control 7.2.0.0 x64 and I have installed the latest agent on the client. I have enabled the option "Permission required" on the client agent.

In some cases in the past, it worked to restart the DameWare MRC Service on the client or to reinstall the service. In this case, it didn't   At the moment, I can advise the user to lock his screen, then I can connect to the desktop without requiring a permisson.

Re: Your logon request was declined. Disconnecting...
by Siggi on Tue Mar 01, 2011 10:45 am

No ideas?
It's a big problem for us at the moment and we're thinking about going back to v6...

Re: Your logon request was declined. Disconnecting...
by bryan on Tue Mar 01, 2011 11:09 am

Have you tried the most current version of the software, which is 7.3 not 7.2 ? You must also update the Client Agent on the remote machine to v7.3 as well.

It souds to me like the DWRCST.EXE (SysTray Icon) process is not running on the remote machine for some reason. You can open Task Manager and check for this process. It should be running anytime there is a user currently logged into the desktop on a remote machine, and the remote machine is not currently at the Logon Desktop or Lock Screen.

Your feedback is appreciated.

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

Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 03, 2011 3:40 am

I've just tried the 7.3 today. I also removed the old Client Agent on the remote machine and installed the current one. I checked the DWRCST.EXE process in the task manager, it is running.

The problem stays the same.

Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 10, 2011 4:45 pm

Please try downloading and installing v7.4 of the MRC software, and then please make sure you update the MRC Client Agent Service on the remote machien to v7.4 as well. We found an issue with a socket API that could return different results on some OS’s.

Your feedback is appreciated.

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

Re: Your logon request was declined. Disconnecting...
by Siggi on Fri Mar 11, 2011 4:35 am

It does not work with 7.4   Same problem.

Re: Your logon request was declined. Disconnecting...
Marty on Fri Mar 11, 2011 12:21 pm

Hi Siggi,

We are still unable to reproduce this behavior in our environment, however we would very much like to resolve this issue. With that said, can you email support@dameware.com so we can provide you with some customized troubleshooting steps for your environment?

Also, if there are any DWMRCS application event log entries on the remote machine, forward those back to us in your email as well.

Thanks so much and we appreciate your help!

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

Re: Your logon request was declined. Disconnecting...
by bryan on Wed Mar 16, 2011 10:00 am

With the help of one of our customers (Thank You Frank !!!) we have confirmed this issue will be resolved with the release of v7.5 of the software.

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

Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 17, 2011 9:55 am

It works!!! Thank you so much, Bryan (and Frank  )

Very little new issue: The version number in the NT Utilities application is shown as "7.4" even in the 7.5 package, so we were a little confused with the update process.

Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 17, 2011 2:06 pm

Hi Siggi,

You're most welcome, and thanks very much for your feedback on this. We really appreciate it.

With regard to the version, please try this out for me. First remove your existing install of DNTU via Add/Remove programs. Then download and install v7.5 again from our website to see if you can still reproduce this behavior.

Your feedback is appreciated.

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

Re: Your logon request was declined. Disconnecting...
by Adrian on Mon Nov 28, 2011 10:56 am

Hi, I am having the same problems as this. The slight difference is my PC is Windows 7 64 bit and the client is 32bit XP. If I use a Windows 7 32 bit it works fine
Thanks

Why is DameWare Central Server v12 Admin Console using TLS 1.0? Is there a way to change it to only use TLS 1.2?

You seem to have a strict "no public timelines" policy which while very unhelpful to begin with, is becoming a big problem for us with the TLSv1.2 issue and our need to comply with PCI. Can you tell me if you will have support for TLSv1.2 completed prior to June 30th of this year per PCI requirements? If this is not something you can answer then we need to start shopping for a new remote support tool now. If you are able to answer this question, I do hope that your time-frame is much sooner than end of June so we have time to upgrade. This really should have been done a long time ago but we like the product enough that we've patiently waited. Out patience is now running thin and with the 1709 issues, it's even thinner now. Please provide your customers with the information they need to make decisions or you will start losing them.

We are migrating away from Dameware and I'm looking for a process that would help me uninstall the program either remotely or via GPO when a user logs in. Is there anything out there like this?

Thanks!

Until recently, DRS has been working great. Then I applied the November update to Windows 10 and no the Microsoft Windows Network no longer displays anything in DRS.  I am using version 12 with both hot patches applied.  Other than applying the update nothing had changed in our environment.  I can still find computers through the Active Directory, but it isn't nearly as convenient.  It is particularly troublesome to find the few computers that are not part of the domain.

Any suggestions for a fix?

Thanks,

Chris

When I am in Dameware, I expand the tree on my Domain Controller, and go to SESSIONS.  I should be able to open SESSIONS and see the users that are logged on.   I get a Error 5- Access is denied error.  I am a admin on this system   Can someone lead me in the proper direction to correct this?

Thanks

Dameware install in linux? If not, have hold map for new version for this system operation. ?

Having some issues figuring this one issue out. Our County users use a remote connection from Parallels to connect to a particular program through a Terminal Server. When a user has an issue that requires support, remote access from our help desk using DameWare closes that application. This did not occur with our previous TS connection program, 2X. Interestingly, if our support uses DameWare to log onto a workstation, and then Parallels makes the connection to the program all will work normally, UNTIL the DameWare session is disconnected, then it kills the app as before. Any thoughts on why this is occurring? Windows logs show nothing unusual occurring. The application just closes, and Parallels will try to re-establish the connection but will not be able to until the DameWare session is closed.

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.

So after upgrading my M.2 240ssd to a 1TB m.2 I figured I would reinstall windows 10 and go with the latest creators version 1709. After installing Dameware Remote Support 12.05.6002 I no longer saw the MS network section expanded in the master browser with all my windows devices like it had in previous versions of windows, including previous windows 10. 1703

Well after contacting solarwinds support and working through the issue, as well as searching on google for this issue. I came across  Microsoft disabling smbv1 in windows 10 1709 by default. After I went in to contol panel, add/remove programs, and windows features turn on/off I renabled the smbv1 protocol and now the MS windows network section is once again populating.  Ive attached a screen shot of the place to check.

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

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

I've built a support CD that is based on BartPE with Sherpya's XPE plugin interface, using Windows Server 2003 R2 (so SP1) media, that allows us to either boot machines via PXE into BartPE, or using a ramdisk, boot.ini and winnt.sif on the machine's hard drive, boot a copy of our ISO image from a folder. I started out integrating DWMRC into my BartPE image back with version 6.4.0.5. I generally update my ISO image every month or so with the newest DWMRC, antivirus defs, other drivers, etc, and have never had issues using DWMRC until 6.7.0.x. Now when we attempted to connect to the machine booted with BartPE, we are getting the message that theMirror Driver is not able to load, or the machine needs to reboot for it to become active. Yeah, I know we can click by it, but it is a pain, and the performance over DSL to some client locations is less than acceptable.

To integrate DWMRC into the BartPE image, I have created a folder on the ISO image (\Programs\Dameware) and into there, I have placed DWRCK.dll, DWRCS.exe, DWRCSET.dll, DWRCSI.dll, and DWRCST.exe. Next, I've modified the start init for BartPe (actually I'm using Sherpya's XPE interface over top of BartPE) that adds two entries the Microsoft\Windows\CurrentVersion\RunOnceEx key:

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

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

So, my question is, what has changed in the mirror driver installation between 6.6.x.x and6.7.x.x and how do I go about integrating the mirror driver of 6.7.x.x into my BartPE ISO. I thought it may just be a matter of adding DamewareDisp.dll to system32 and DamewareMini.sys to drivers, and that they would already be there when the mirror driver tries to install, but that did not help. If I had a copy of the registry entries that DWMRC creates when it installs themirror driver, then I could embedded those in the system hive that exists prior to BartPE booting.

dcc

Dean Colpitts
Members IT Group
Salisbury, NB

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

Hi Dean,

Basically nothing has changed in the Mirror Driver itself. The only thing new was the addition of the actual message, letting you know the Mirror Driver couldn't be initialized during this connection for some reason. For example, in a non-standard machine config when the Terminal Services Service has been disabled.

Previously under conditions like this the software would just connect without using the MirrorDriver when it couldn't be loaded for whatever reason. In other words, it would just automatically switch over to non-Mirror mode without notifying you. In this latest version we decided to notify the user of this condition, but all you should have to do is click on OK to continue your connection.

I hope this helps.

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

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

I used the same method to integrate DWMRC into windows PE 2. After the computer booted from this windows PE CD, DWRCS.EXE was installed fine and DWMRCS service was started as well. From another computer, dameware remote control is able to authenticate to it but the process stucked at "initializing desktop, please wait". This message stayed on screen and dameware remote control could not show the remote desktop. I have tried DWMRC 6.2.x, 6.7.x, 6.8.1.4 and windows PE 2.0, 2.1, 3, but no luck. Did I miss any step or there is some other reason? We are using windows PE CD to image computers at remote sites. It will be great helpful if DWMRCcan work on windows PE CD.

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

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

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

[Version]
Signature= "$Windows NT$"

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

[WinntDirectories]

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

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

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

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

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

I build my code from a mounted Windows 2003 SP1 ISO image on my BartPE development machine (actually it's a VM that I do my building in) and I use Sherpya's XPE 1.0.7 plugin for my user interface instead of the nu2menu. I use a default resolution of 1024 x 768 x 32bit.

Once we have the BartPE image created, we then install it into Windows boot loader (or boot.ini) and we also use it with PXE for reimaging / repairing machines at remote sites across the country. This way we can modify the boot.ini remotely to force the machine to boot the BartPE image without any user intervention, or if the machine's HDD is dead / blank / new, we can have the end user PXE boot the machine for us so we can re-image it / repair it as required.

Actually I used these methods yesterday at one client site to install Windows XP on a desktop that we didn't have an image for by invoking an unattended XP setup from within BartPE and once the pc rebooted, it automatically installed XP and joined the domain, where a GPO pushed the Dameware client to the machine and I was able to finish the software installation and customization of the machine.

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

dcc

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

Hi Dean,

Your method works perfect on BartPE, however windows PE does not like it. I guess MS puts some restrictions on their PE. One benefit of winpe is that it has all device drivers we are using though it is easy to add device drivers to BartPE. I expect some one knows how to fix it on windows pe, otherwise I will switch to BartPE.

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

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

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

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

anyone have any ideas?

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

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

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

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

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

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

The reason I want to use Dameware in PE is that I could remotely boot a PC but then I have no way to dial into the computer and kick off a build or recover a file etc.
Symantec have created PCAnywhere Thinhost for the exact reasons which I want but it's stupidly expensive.

Dameware version 12.0.4 Struck on negotiating version for 15-20 minutes. I tied all settings for lower bandwidth, but still facing issue

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.

Good day!

Help please, about a month drip internet in search of an answer to your question , really hope you can help me .

We have over 10k machine which is still running services and it so happened that the settings apply DWRCS DWRCS.ini (reg) those that were set when you first install the service.

And we have each their gadgets ... Please tell me how to update the file when connecting to a remote machine without removing the service and re- install it.

Ready even in monetary terms from thank brain is melting ...

Thank you.

Hi,

We try to subscribe to Dameware 12.1 Beta, but we have an error message, while our license is active.

It appears you do not have a license for DameWare Mini Remote Control, or you are no longer under active maintenance. In order to participate in the Dameware 12.1 Beta 1 Beta program, customers need to ensure their license(s) are under active maintenance. If you feel this is a mistake, please contact customersales@solarwinds.com.

We have several problem with Remote Support and Windows 10 1709.

Thanks you.

Dameware install in linux? If not, have hold map for new version for this system operation. ?

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?