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.

MRC Properties?
by KarbonKopy on Thu Jan 13, 2011 4:27 pm

I know in MRC in 6.x you should set the defaults for the MRC agents that would automatically roll out to them during a install etc. It was under install options on MRC's default host properties. Has this been moved somewhere? I need to be able to change those values.
________________________________________
Re: MRC Properties?
by ukwalnuts on Fri Jan 14, 2011 11:34 am

I'm also looking for this. Trying to disable 'Notify Dialog' but can't find option anywhere.

I've emailed support but still waiting on reply.
ukwalnuts
________________________________________
Re: MRC Properties?
by Marty on Fri Jan 14, 2011 4:02 pm

Version 7.x no longer uses a DWRCS.INI file for the settings of the service and therefore the option to copy that file over to the remote machine has been removed.

The settings for the MRC client agent service can be customized using the new and improved MSI Builder.

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

________________________________________
Re: MRC Properties?
by ukwalnuts on Sat Jan 15, 2011 5:24 am

Hi Marty,

Thanks for help so far.

I've looked at MSI builder but still can't see how to apply changes I want to my existing desktops.

When I connect to desktops which has version 6 agent installed Dameware asks me if I want to upgrade. If I click yes it upgrades agent to v7 but there isn't any option to choose which msi installer it should use or profile.

If I go to File > Install Service again I can't choose which msi or profile Dameware should use.

Other than manually going to each desktop and installing customized msi. How do I get agents upgraded on my desktops with settings I want?

Thanks
________________________________________
Re: MRC Properties?
by KarbonKopy on Sun Jan 16, 2011 11:37 am

I am in the same boat Marty, I want the default install to be able to be set before I roll out the client. At the moment I'd have to either build a MSI and deploy it or customize after the fact on the client itself.
________________________________________
Re: MRC Properties?
by bryan on Sun Jan 16, 2011 7:26 pm

Hey KarbonKopy,

There is two ways you can do it.

1. Build an MSI Package with all your custom settings and then distribue this MSI package to all your users via any of your existing distribution methods. The MRC Client Agent Service will be installed using the custom settings you specified.

2. Install the MRC Client Agent Service on your own machine. Then right-click on the MRC SysTray icon and select the Settings context menu. Once you've made all your settings changes, you can then export the following Registry key for the v7 Client Agent Service into a .REG file:

[HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\Mini Remote Control Service]

Once you have your .REG file, you can then distribute this .REG file to all your remote machines prior to installing the MRC Client Agent Service on those machines. By importing the .REG prior to installing the Service, when the Service is eventually installed it will automatically start using these custom settings (not default settings).

I hope this helps.

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

________________________________________
Re: MRC Properties?
by bryan on Sun Jan 16, 2011 9:36 pm

**Update: Our developer is currently working on a function that will allow you to copy/merge settings from a DWRCS.reg file during Client Agent Install/upgrade. This functionality should be available shortly, and we will notify everyone when it's available.

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

________________________________________
Re: MRC Properties?
by Marty on Mon Jan 17, 2011 6:07 pm

We have just released an update, 7.0.1.0, that includes an option to push out a DWRCS.reg file to the remote machine with your preconfigured settings.

You will need to install the MRC client agent service on your local machine, configure it to your specifications, then export the [HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\Mini Remote Control Service] registry key and name it DWRCS.reg. Place that file in your DameWare installation directory and when you push out the service, you should have the option to “Include Configuration File DWRCS.reg.”

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

________________________________________
Re: MRC Properties?
by KarbonKopy on Tue Jan 18, 2011 11:03 am

I can confirm this works, thank you! If I had any suggestion, it would be a easier way to include the settings much like v6 did.
________________________________________
Re: MRC Properties?
by ukwalnuts on Tue Jan 18, 2011 1:47 pm

KarbonKopy wrote:I can confirm this works, thank you! If I had any suggestion, it would be a easier way to include the settings much like v6 did.
100% Agree. Thanks for sorting this out so quickly.

Re: MRC Properties?
by Maverick on Tue Jan 18, 2011 1:51 pm

Ditto!

Mav
________________________________________
Re: MRC Properties?
by Roger on Wed Jan 19, 2011 4:19 pm

Just curious, but now that Dameware is 64 and 32 bit, does this reg import account for both locations of the keys since 64bit stores in a different location when a reg import is executed from a 32bit process? It may need to write to both unless you use the registry api flags to make both 32 and 64 bit read/write from/to the same location. May only apply to a 32bit MRC updating the reg of a 64bit machine.
________________________________________
Re: MRC Properties?
by Marty on Wed Jan 19, 2011 4:50 pm

Hi Roger,

The registry key for both 32-bit and 64-bit are in the same location. Do not use any keys from the “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node” on 64-bit machines. Always use “HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\Mini Remote Control Service” on any machine. Lastly, don’t use a 32-bit application for registry import or export on a 64-bit machine.

I hope this information helps.

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

________________________________________
Re: MRC Properties?
by Roger on Wed Jan 19, 2011 5:05 pm

How does the 32bit version of MRC import the .reg file on a remote 64bit machine? Does it pass the file to the 64bit app and let it import it?
________________________________________
Re: MRC Properties?
by Marty on Wed Jan 19, 2011 7:31 pm

Hi Roger,

Even when you are using the 32-bit application, the service on a 64-bit machine will be the 64-bit service and the service is what imports into the Registry.

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

________________________________________
Re: MRC Properties?
by arasg on Thu Jan 20, 2011 9:39 am

KarbonKopy wrote:it would be a easier way to include the settings much like v6 did.
I agree. I have been using this for many years and it was much easier the old way.

Please add this back.
________________________________________
Re: MRC Properties?
by zack1010 on Thu Jan 20, 2011 11:27 am

Hey DameWare Guys,

Thanks for making this DWRCS.Reg enhancement. This new functionality is so much better than the way it was in older versions. I don't know about the rest of you here on the forum, but so many times I pushed out config files to my agents, only to find out later someone had enabled the setting to use the Registry instead, which meant my INI file was being ignored anyway. Now the settings are only in one place (the Registry) instead of multiple places (INI file or Registry), so no more confusion.

Zack

________________________________________
Re: MRC Properties?
by MTheile on Tue Jan 25, 2011 9:21 am

Hi,

is there a way to set the option to include Configuration File DWRCS.reg as a default setting?
Our supporters often forget to set this option, it was easier for us to deactivate it, when we don´t need it.

Thanks

________________________________________
Re: MRC Properties?
by Ragil on Wed Jan 26, 2011 10:48 am

MTheile wrote:

Hi,

is there a way to set the option to include Configuration File DWRCS.reg as a default setting?
Our supporters often forget to set this option, it was easier for us to deactivate it, when we don´t need it.

Thanks

Same here!!! This option must be added...

Thanks
________________________________________
Re: MRC Properties?
by dustino on Wed Jan 26, 2011 6:24 pm

We just got 7.0.3.0 installed and have been trying to get all the desired settings set in the MRC. However, everytime we make our changes to the settings, we click OK and all the settings get reset back to default.

Is this normal behavior? We are trying to follow the procedure outlined by Marty to push our MRC settings to other computers via the .reg file.

Thanks in advance.

Re: MRC Properties?
by bryan on Wed Jan 26, 2011 11:04 pm

Hi dustino,

Thanks for your feedback.

Just to make sure we understand you correctly, you've already installed the MRC Client Agent Service on this machine, and then you right-click on the MRC Tray Icon and select Settings. You then configure all your custom settings, however, after selecting OK all the settings revert back to default. Is this correct ?

By any chance, is this machine running XP or 2003 Server ? If so, after clicking on the MRC Tray Icon's Settings context menu, you should have been presented with a Run As dialog asking if you want to "Run this program with Restricted Access". If you do not clear this checkbox before selecting OK then any changes you make will not be saved.

Your feedback is appreciated.

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

________________________________________
Re: MRC Properties?
by ukwalnuts on Thu Jan 27, 2011 8:27 am

I've come across this issue.

When I right-click on the MRC Tray Icon and select Settings I get window pop up saying "Which user account do you want to use to run this program"

For some reason domain administrator account doesn't work but if I enter local administrator account settings are saved correctly.

This is happening when I'm logged in as domain administrator on XP or Server 2003 machine.
________________________________________
Re: MRC Properties?
by dustino on Thu Jan 27, 2011 1:17 pm

Bryan wrote:

Hi dustino,

Thanks for your feedback.

Just to make sure we understand you correctly, you've already installed the MRC Client Agent Service on this machine, and then you right-click on the MRC Tray Icon and select Settings. You then configure all your custom settings, however, after selecting OK all the settings revert back to default. Is this correct ?

By any chance, is this machine running XP or 2003 Server ? If so, after clicking on the MRC Tray Icon's Settings context menu, you should have been presented with a Run As dialog asking if you want to "Run this program with Restricted Access". If you do not clear this checkbox before selecting OK then any changes you make will not be saved.

Your feedback is appreciated.

The check box was the problem Bryan. We had not unchecked the "Protect my computer and data from unauthorized program activity". Once we unchecked this and made our desired changes, the MRC popped up a notification that "The client agent is in the process of configuring". Then it retained the settings we changed.

FYI we are running Windows XP.

Thanks, Bryan.
________________________________________
Re: MRC Properties?
by bryan on Thu Jan 27, 2011 5:54 pm

You're most welcome, and thank you very much for your feedback. I'm glad we were able to help.

Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: MRC Properties?
by jpflepsen on Fri Jan 28, 2011 11:24 am

I have to agree with some of the previous posters - this having to save a .REG file after making settings changes on the host is a much more time consuming & convoluted way of deploying settings to clients. Especially when you want the client settings to be different from how you want your host to behave. I'd sure like to see the return of the v6 way of pushing these settings to clients.
jpflepsen
________________________________________
Re: MRC Properties?
by bryan on Mon Jan 31, 2011 5:41 pm

Hi Everyone,

Just FYI, we're looking into adding some new functionality in the next release of the software, which will be v7.1.0.0, where you can optionally configure and save the DWRCS.Reg file via a GUI during service installation. I will update everyone here as more information becomes available.

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

________________________________________
Re: MRC Properties?
by KarbonKopy on Wed Feb 02, 2011 1:47 pm

Awesome to hear Bryan!
________________________________________
Re: MRC Properties?
by KarbonKopy on Thu Feb 03, 2011 5:38 pm

Just saw the 7.1.0 install...and can confirm you can now set the options in MRC. Thanks! If I may add one more suggestion it would be the option to set a default...either include or exclude the .reg file.
________________________________________
Re: MRC Properties?
by Ragil on Fri Feb 04, 2011 1:33 pm

KarbonKopy wrote:

Just saw the 7.1.0 install...and can confirm you can now set the options in MRC. Thanks! If I may add one more suggestion it would be the option to set a default...either include or exclude the .reg file.

I want it too!!!

Hello,

My company recently purchased 50 licenses (150 seats) of Dameware DRS. I have been tasked with coming up with a standard configuration of this software for all of our IT staff worldwide. I have specifically configured, namely the MRC settings, for use in our environment. My issue is that I am not confident all of my staff will be able to configure the software or be compliant to the corporate standards I have put in place.

My question: is there a way I can deploy the DRS software to global IT staff with a standard configuration?

Thank you,

Tyler

Hi!

Tell me please, support server "reverse connection" via the command line.

Thank you.

Can I map a drive on the remote client from within DRS?

We are still using the DameWare RS 9.0V where I work and I had to reload DameWare on to my system the other day.  When I loaded DMRS onto my system I received a "SolarWinds.MRC.Licensor has stoppped working" error.   When I click on the "Close the program", the entire program closes.  What is the fix for this error?

Thank you

Tawna

We've updated the DameWare - Updated April 11, 2014 support page.  This serves as a one-stop shop for all your DameWare documentation, how-to's, troubleshooting, and more.  You can add the page to your "links" or bookmark the page so you'll always have it handy.

Hope this helps, as always!

Danielle!

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.

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.

System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 1:13 pm

Hello everybody, i got this error today:

AUthentification failed:
System error: 5
System message: Access Denied
Please check the event log on the remote machine for possible cause

And the event gives me this:

Date:01/30/0823:55:21
ComputerName:DJ0DJ0
UserID:DjoDjo
LogonAsID:
Domain:
OSProductID:55274-642-5926024-23226
OSRegisteredOwner:Dj0Dj0
OSRegisteredOrganization:Dj0Dj0
HostNamefromPeer:dj0dj0
IPAddresse(s)fromPeer:192.168.0.17
Host:
IPAddress:(HIDDEN)
ProtocolVersion-DWRCC.EXE:6.650000-2.000000
ProtocolVersion-DWRCS.EXE:3.600000-0.600000
ProductVersion-DWRCS.EXE:3.63.1.0
AuthenticationType:NTChallenge/Response
LastErrorCode:0
LastErrorCode(WSA):0
Absolutetimeoutsetting:0minutes
Connect/Logontimeoutsetting:90000miliseconds
AccessCheck:
  0 LfLes
º G
º G  ^^* DWMRCSSERVER_NECH
DameWareMiniRemoteControl
SystemError:10061
Unabletoconnecttomailserver-Error:100610 (    """"3333DDDD0 ¸t (

I don't know if the last part (SystemError:10061
Unabletoconnecttomailserver-Error:100610 (    """"3333DDDD0 ¸t ()
is really part of the log concerning DWRCS because the event log was corrupted so ...

I thought it was due to the Absolute timeout setting put to 0 but i don't know..

I hope you'll be able to help me. Thanks in advance

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by bryan on Wed Jan 30, 2008 1:31 pm

The remote machine appears to be running a much older version of the software that we no longer support (i.e. version 3.x).

Therefore, I would suggest you first remove this older version of the Service and install your current version of the Service on the remote machine.

If you still receive the Access Denied error using the current version, then either paste those logs back here again, or send them to our support staff at support@dameware.com for review. There should also be multiple DWMRCS entries, so send the entire text from each entry.

Your feedback is appreciated.

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

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 1:40 pm

But... i managed to access this remote machine yesterday and then i DIDN'T touch anything (neither settings nor anything else) and now it doesn't work.. So it's not a problem of too much old version.

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by bryan on Wed Jan 30, 2008 2:02 pm

According to the log you posted, this remote machine is running version 3.63 of the MRC Client Agent Service.

ProtocolVersion-DWRCS.EXE:3.600000-0.600000
ProductVersion-DWRCS.EXE:3.63.1.0

... and you will not be able to connect to version 3.x of the Client Agent using any 6.x version of the software.

Therefore, please remove the MRC Client Agent from this machine and install the current version. Then you should be able to connect.

You may also want to check the logs on this machine to see if someone else connected after you did and downgraded the Client Agent to this older version. That's the only explanation I can offer at this time.

I hope this helps.

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

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 2:09 pm

In fact, i connected yesterday for the 1st time to this machine with the DWRCS CLIENT version 3.60.... so i installed the version 3.60... on the remote machine... and it worked! i didn't upgrade the remote version.. (today i tried with both versions of the client and none worked)

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 2:33 pm

And i forgot to say i had a "Access denied" with DNTU 6.6 !! for the remote command view and a Error for the event logs ...
So it's not linked to DWRCS in fact :s

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by bryan on Wed Jan 30, 2008 3:24 pm

If you in fact connected with version 6.x of the software to a 6.x Client Agent service on the remote machien, then send me the log files from that connection just as I asked you in my original response. Because without that information I cannot help you. Also send me all of the DWMRCS log entries associated with this failed login attempt, not just the connect or disconnect entry.

- What rights do you have within the O/S security on the remote machine?
- What O/S and Service Pack level is installed on both the local & remote machines? If it's XP or Vista, also distinguish the exact version of the O/S as well (i.e. XP Home, XP Pro, etc...).
- Are these machines located on the same LAN, over the WAN, accross the Internet?
- Can you access the Admin$ share on the remote machine (net use \\remotemachine\Admin$) via a CMD prompt on your local machine?

Also, just FYI, DNTU uses a completely different set of ports & protocols and wouldn't have anything to do with your behavior via MRC. Microsoft's APIs used within DNTU use what's called NT "Pass-Through" authentication. Therefore, if you receive Access Denied errors using Remote Command View or Event Log View, this means your current O/S logon credentials don't have sufficient rights within the O/S security on the remote machine. Therefore, you would have to establish an authenticated connection to this remote machine using sufficient credentials (i.e. Administrator), either within the O/S itself or by using DNTU's LogonAs feature.

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

Re: System Error: 5 Acces is Denied ??? [I PUT LOGS]
by Mrconnard on Wed Jan 30, 2008 3:44 pm

- What rights do you have within the O/S security on the remote machine?
Administrator rights in theory..
- What O/S and Service Pack level is installed on both the local & remote machines? If it's XP or Vista, also distinguish the exact version of the O/S as well (i.e. XP Home, XP Pro, etc...).
Both XP Pro
- Are these machines located on the same LAN, over the WAN, accross the Internet?
Across the Internet
- Can you access the Admin$ share on the remote machine (net use \\remotemachine\Admin$) via a CMD prompt on your local machine?
No.. Error 1219

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.

Disable automatic saved hosts
by boucherjeanfra on Fri Jan 21, 2011 2:06 pm

Hi,

In the version 7 of Mini-Control, is it possible to disable the "automatic" save to a new host ?
I verified twice in the settings but found nothing.

Thanks for your help,

Cheers,

Re: Disable automatic saved hosts
by bryan on Mon Jan 24, 2011 4:01 pm

Hi boucherjeanfra,

Anytime you start typing while the Host field is selected the New Host dialog will be displayed, to allow you to create a new Saved Host entry. If you're trying to modify an existing entry, select the desired entry in the Saved Host List, then right-click on this entry and select Rename Host. This will allow you to modify the existing entry without creating a new one.

I hope this helps.

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

Re: Disable automatic saved hosts
by Siggi on Wed Jan 26, 2011 5:18 am

Hello there,

I just installed the MRC7 and have the same problem as boucherjeanfra. I also want to get the "automatic-saving-a-new-host" feature disabled because in the past I always connected to a remote host by only typing in the adress. The hosts don't need to be saved. It's faster for me than selecting the host from a list.

Hope you got what I mean.

Re: Disable automatic saved hosts
by williaa on Wed Jan 26, 2011 4:01 pm

@Bryan, what we're wanting to know is if there's any way to disable the New Host dialog from displaying anytime you start typing while the host field is selected. It's more convenient for this to not happen when using the Mini Remote Control.

Re: Disable automatic saved hosts
by bryan on Wed Jan 26, 2011 5:36 pm

Thanks everyone for your feedback.

Presently there is no way to turn this functionality off. MRC v7 will automatically create a new Host Entry when you start typing, whereas v6 would create a (Temporary) entry. (Temporary) entries no longer exist in v7.

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

Re: Disable automatic saved hosts
by Siggi on Thu Jan 27, 2011 3:12 am

Perhaps, it could be an idea to add a "Quick connect" adressbar to the next version of MRC for those who want to connect in that specific way?

Re: Disable automatic saved hosts
by bryan on Mon Jan 31, 2011 5:35 pm

Hi Everyone,

Just FYI, we're looking into adding some new functionality in the next release of the software, which will be 7.1.0.0, where you can turn off the Host Entry "Auto Save" feature. I will udpdate everyone as more information becomes available.

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

Re: Disable automatic saved hosts
by KCarney on Tue Feb 08, 2011 2:14 pm

So has it been added?

Re: Disable automatic saved hosts
by bryan on Tue Feb 08, 2011 3:17 pm

The new "Disable Auto Save" functionality was implemented in v7.1.0.0. On the MRC Remote Connect dialog (not from the main menu) first select the Edit menu, then enable the "DisableAuto Save" setting. This will instruct the software not to display the "new host" dialog when you modify the HostName/IP-Address of an existing Host Entry. Instead, a new temporary entry will be created, designated by a red circle with an x in the icon's lower right corner. If you close the MRC Remote Connect dialog, or simply Connect then Disconnect, this temporary entry will now be gone.

I hope this helps.

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

Re: Disable automatic saved hosts
by KCarney on Tue Feb 08, 2011 4:57 pm

When "Disable Auto Save" option is enabled "reconnect" no longer functions properly, it now displays the last computer I connected to when the option was disabled. Please fix this

Re: Disable automatic saved hosts
by bryan on Tue Feb 08, 2011 5:35 pm

This is exactly how the reconnect option is designed to function, and this is the same way it worked in v6.x as well. By default only Saved Host entries are added to the Reconnect list, because we only have settings stored for the entries in your Saved Host list. There are no settings stored for any type of "temporary" entries, therefore, they are not added to the Reconnect list. If you need custom settings stored for any remote machine, then you must save it to your Saved Host List.

With that being said, there is a setting on the Local Global Options dialog called "Add only savedhost entries to Reconnect list". If you choose to disable this setting, then any machine you connect to will be added to the Reconnect list. However, since no custom settings exist for any of these non-saved machines, you may not be able to successfully reconnect.

If all of these non-saved machines use the same default credentials & settings, then you should be able to add these default credentials and settings to the Default Host Properties dialog. These Default Host settings are used when you create a new Host Entry. However, if you highlight an existing Saved Host Entry and then change the HostName or Ip-Address, then the settings from this Original Host Entry (not default) are used to create your new Temporary entry.

I hope this helps.

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

Re: Disable automatic saved hosts
by KCarney on Wed Feb 09, 2011 2:39 pm

and this is the same way it worked in v6.x as well.

No, it didn't. It randomly picked a host that was connected to by any number of open DMRC windows, it was a little annoying at times but worked. This new version seems a lot cleaner

If you need custom settings stored for any remote machine, then you must save it to yourSaved Host List.

That makes sense.

With that being said, there is a setting on the Local Global Options dialog called "Add onlysaved host entries to Reconnect list". If you choose to disable this setting, then any machine you connect to will be added to the Reconnect list. However, since no custom settings exist for any of these non-saved machines, you may not be able to successfully reconnect.

That is exactly how it worked in 6x, I will give that a try. Thanks for explaining! 

Re: Disable automatic saved hosts
by KCarney on Mon Feb 14, 2011 1:24 pm

Works great now in 7.2.0.0, thank you!

Re: Disable automatic saved hosts
by KCarney on Fri Feb 18, 2011 11:10 am

Correction, this works *sometimes*. After a week of using it disconnecting from a host and attempting to reconnect results in blanked out connection options. I have to enter the previous host manually to reconnect.

Re: Disable automatic saved hosts
by bryan on Fri Feb 18, 2011 3:02 pm

Just because you connected the first time doesn't mean you can immediately Reconnect to any machine when it's not saved in the Saved Host List. This is exactly why we did away with this feature initially for version 7.x, for all machines not saved to the Saved Host List.

When a machine is saved in the Saved Host List, we have all the settings necessary to Reconnect (UserID, Password, Port, etc...). However, when a machine is not saved to the SavedHost List, there are no settings we can use to Reconnect. Once you click on Disconnect, all those settings are now gone. We no longer have any settings for this machine. Therefore, by design, they will be blank settings exactly as you mentioned previously when you try to Reconnect, and the connection will fail.

The only way "Reconnecting" to a machine that's not explicitly saved to the Saved Host List will ever work would be if you enter the correct settings (UserID, PW, Port, etc..) under the Default Host Properties dialog (i.e. View / Default Host Properties from the main menu). Just keep in mind that these default settings would be the same settings used for all "Reconnect" attempts when a machine is not explicitly saved to the Saved Host List.

I hope this helps.

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

Re: Disable automatic saved hosts
by KCarney on Mon Feb 21, 2011 9:18 am

When a machine is saved in the Saved Host List, we have all the settings necessary to Reconnect (UserID, Password, Port, etc...). However, when a machine is not saved to theSaved Host List, there are no settings we can use to Reconnect. Once you click on Disconnect, all those settings are now gone. We no longer have any settings for this machine. Therefore, by design, they will be blank settings exactly as you mentioned previously when you try to Reconnect, and the connection will fail.

I would agree with you, however, I have set my default settings to "NT Challenge/Response" and "Use Current Logon Credentials" selected. *Sometimes* when I launch DMRC all settings are blank and "Encrypted Windows Logon" is selected with no machine name as host. So as you can see I don't need any saved settings, I don't want hosts automatically saved, and this should be working but is not.

Re: Disable automatic saved hosts
by bryan on Mon Feb 21, 2011 2:04 pm

Based upon the screen shots you sent to support, the software is working exatly as it should.

In your screen shot there is no Host Entry selected, instead, the Root folder (i.e. Saved Host List) was selected. When MRC starts up it will try to locate and highlight the last entry you connected to. However, when that entry cannot be found (i.e. it was not saved), then the root folder is selected. Therefore, by design, since a folder is currently selected and not a host entry, MRC will not go through all the work of pulling the default host properties just to populate the RC dialog. So the fact that you see Encrypted Windows Logon shown in the RC dialog while a folder is selected when you’ve selected NT Challenge/Response as default doesn’t mean there is an issue with the software.

Also, the fact that you say this only happens *sometimes* means that these other times when this does not happen, there must be an existing host entry already with this same name. So when you click on reconnect, those settings from the existing entry will be used and not default settings.

I hope this helps.

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

Re: Disable automatic saved hosts
by TrafficTech on Fri Mar 04, 2011 11:09 am

I have a few comments to make on the Saved Host List of version 7.3.0. I currently have my settings to "Disable Auto Save" and I have disabled the "Add Only Saved Host Entries to Reconnect List". I seem to have found a little bug in the process.

1) If I enter a new temporary entry, it indeed populates in the reconnect list. I can go back and connect to another temporary address and that also goes into the reconnect list. I notice the reconnect list has only unique entries (If I reconnect to a previous entry using the Connect button and not the reconnect button. However, if I use the reconnect drop-down, the entries are no longer unique. Furthermore, when I close and reopen the application, my reconnect entries have vanished, the button is grayed out. This happens every time I use the reconnect button.

2) If I leave the Auto Save feature on, I would like to have an option to have unique entries in the Host List. The list can get long and I don't necessarily want to go through it every time, but I do not want to duplicate my entries either

3) I can understand that if I select a Saved Host entry and decide afterwards I want to connect to a temporary host instead, the Alias from the previous entry is still shown. What I don't like is that if I inadvertently left the alias there and connected, the entry listed in the reconnect drop down shows as ALIAS (HOST). I am more interested in the host and don't really want to see the alias entry (especially since I mistakenly left it in during the temporary entry previously).

David M
Systems Admin
Traffic Tech

Re: Disable automatic saved hosts
by bryan on Thu Mar 10, 2011 11:10 am

Hi David,

Thanks very much for all the info you provided. This should be now be resolved in v7.4.

Your feedback is appreciated.

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

Hi!

Tell me please, support server "reverse connection" via the command line.

Thank you.

Can I map a drive on the remote client from within DRS?

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.

Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 13, 2007 5:34 am

Hi All,

We are currently having issues with logging onto some of our machines using the DameWareMini Remote Control. We recently installed some Microsoft patches on the machines and this has resulted in us having to log onto the machines using Remote Desktop rather than DameWare. Do you know of any Windows updates that may affect DameWare connection? When we try toconnect using DameWare we get the Winsock error:

Connect Error:
System Error: 10061
System Message: No connection could be made because the target machine actively refused it.

We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.

Any help would be greatly appreciated.

Kind regards.

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Fri Sep 14, 2007 11:13 am

Hello threeofspades,

Are you sure you're specifying the correct TCP port in your Host settings?
Is the MRC Client Agent Service already installed & running on these remote machines?
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?

Because a Winsock 10061 error typically means the MRC Agent Service was not listening on the TCP port that you specified (default is TCP 6129). Then a subsequent attempt at interrogating the Servcie Control Manager on the remote machine failed for some reason (insufficient rights, ports blocked, file & printer sharing not enabled, etc…). This process of interrogating the Service Control manager requires the Operating System's Installed Protocols (File & Printer Sharing - UDP 137, UDP 138, TCP 139, TCP 445) to be open between the loal & remote machines, and it also requires Administrator rights within the O/S security on the remote machine.

Therefore if we cannot connect to the MRC Client Agent on the remote machine using the specified TCP port, and then we also cannot communciate with the Service Control Manager on the remtoe machine using Microsoft’s APIs, then we have no choice but to fail. Because these same ports/protocols used by Microsoft’s APIs in order to communicate with the Service Control Manager are the same ones required to install, remove, start, or stop the MRC Client Agent Service on the remote machine.

However, please also click on the Copy button on the Winsock Error Dialog, then send me this information (paste it into this email) back to me for examination. Also include a screen shot of the actual Winsock Error dialog as well so I can review it.

Your feedback is appreciated.

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

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Mon Sep 17, 2007 6:19 am

Hi Bryan,

Thank you for your response.

I have some additional information that may help to try to resolve this issue.

I can use MRC on the servers themselves to connect to my own machine, but am unable toconnect from my machine to the servers using MRC.

When i try ot connect to the server using MRC i first get a message saying the following:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

I select OK but then get the following error:

"Unable to start Service
System Error: 2
System Message:
The system cannot find the file specified"

When I RPC'ed onto the server and checked the DameWare Mini Remote Control service is was not running. When i selected to start it i get the error:

"Could not start the DameWare Mini Remote Control service on Local Computer

Error 2: The system cannot find the file specified."

When i checked the path to the executable 'C:\WINDOWS\system32\DWRCS.EXE -service' the DWRCS.EXE was not in there.

I have tried to load DameWare again but get the same errors. It seems that this executable has been deleted for some reason. How can i retrieve it or load it again?

Thank you for your time and effort.

Kind Regards

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Mon Sep 17, 2007 10:37 am

Hi threeofspades,

You're welcome and thank you for this additional information. It was very helpful...  

As you have already found, Microsoft's System Error: 2 means File not found, and that's definitely due to the DWRCS.EXE file being missing in the System32 folder.

However, all you should have to do is re-copy the DWRCS.EXE file from your local DameWareInstallation folder to the System32 folder on this remote machine. Then you should be able torestart the Service again.

But you might also want to do a little extra research to find out how this file could have been deleted.

I hope this helps.

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

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Tue Sep 18, 2007 4:43 am

Hi Bryan,

I took your advice and copied the DWRCS.EXE file from my local machine to the WINDOWS\system32 folder on the server.

When i tried to MRC onto the server i got the request:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

I selected OK and it came up withthe message:

"Service Start Status:

Starting service....."

I thought that this was looking good but unfortunately it came back to the above message:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

It seems that the service is starting but is tehn stopping several seconds later.

I RPC'ed onto the server to check out the DameWare Mini Remote Control service. It was setto automatic and was not started. i set it to start and it did so. But about 5 seconds later it just stops.

Not sure what is going on but something is stopping the service from running.

Any ideas?

Kind regards

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Tue Sep 18, 2007 1:46 pm

Hi threeofspades,

Thanks very much for the update. This is some great information.

I believe you're right. There appears to be something else here that's stopping the Service from running. What other software do you have running on this machine? Do you have anything like CA eTrust, or Pest Patrol, or Pest Patrol remote (look for ppRemoteService.exe in Task Manager under Processes)?

If this is the cause, then additional information on how to configure the appropriate exception within Pest Patrol is also available in another thread on our forum:

The Dameware mini remote service is not running on XXX.
http://forums.dameware.com/viewtopic.php?f=8&t=47

Your feedback is appreciated.

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

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 20, 2007 5:42 am

Hi Bryan,

Thank you for all your help.

We do have eTrust running on our systems and when i placed the DameWare exception into the Management Console i got DameWare back working on all but one server. But i will check it out and see if i can figure out where the problem is. I'm sure it's just something simple but the service still seems to be stopping on that particular server.

Thanks again for all your help and it was very much appreciated.

Kind Regards

The updated DameWare app v10.1 for DameWare DRS customers is now available on itunes store. This release is an update on the existing iOS app and provides several improvements and bug fixes.

What’s New and Improved in Version 10.1

• Improved several drawing issues

• Host list now refreshes with each new use

• Slide animation on successful connect

• Fixed screen issue switching between docked and split mode

• Additional “Shift” button functionality

• Fixed “View only for this account types” button functionality

• Fixed keyboard limiting drop-down menu

• Ability to use “Enter” button on when using Cmd Prompt

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.

The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 5:28 pm

The full text of the message is The Dameware mini remote service is not running on xxx. Would you like to start it now? I answer OK and get "Unable to Start Service; System Error 2; The system cannot find the file specified. It started on a server this morning. After doing a random check of the computers on our domain I have found that it is random. Some machines are ok, some I can't access. It is not dependent on a specific operating system. Can anyone help?

Thanks.
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Mon Jul 09, 2007 6:02 pm

Hello Jodi,

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

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

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

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Mon Jul 09, 2007 7:12 pm

Bryan,

The DWRCS.exe file is version 5.1.1.0. We are using 32 bit computers running Windows 2000 SP4 and Windows XP SP2.

One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest. Some of the machines don't have the file at all.

Our AntiVirus software is Computer Associates and it checks for updates each day and will download them to the individual computers if needed on a daily basis.

Thanks for your help.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 3:30 am

Hi Jodi,

You're welcome.
One of the machines we can't access has the DWRCS.exe file but it has been renamed to DWRCS.exe.manifest
Actually, the manifest file is a valid file, so it appears your DWRCS.EXE file has been deleted, not renamed. So this is most likely due to your CA eTrust software, either within the Anti-Virus portion of the software, or within the Pest Patrol portion of the software.

Therefore, all you should have to do is define an exception for our software in either portion of the CA software (AV or Pest Patrol) so it does not delete any files for our software.

I hope this helps.

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

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Tue Jul 10, 2007 9:33 am

Hi again Jodi,

Here is some additional information I received from another customer on this. Many thanks go out to Zac T. for this information. Hopefully this will help you out:
Here is what worked for me…

1. Log into the E-Trust management console
2. click on the policy management tab at the top of the page
3. under the policies section, change the application dropdown to eTrust PestPatrol and the Type dropdown to Pest Exclusion
4. on the right side of the page change the tab to “Pests” and click the change button.
a. In the box type DameWare and click search.
b. Highlight “DameWare Mini Remote Control” and hit the over arrow so it moves to the Excluded Pests box on the right
c. To close click the “Set Exclude List” button at the bottom
d. Click apply in the Policy Management tab to save those settings
5. Change the tab to “Paths”
a. Click Add
b. Type “Program Files\DameWare Development\DameWare NT Utilities” in the box and click “Set Exclude Path”. (I also added “c:\windows\system32\dwrcs.exe” but I don’t know if that is necessary)
c. Click apply in the Policy Management tab to save the settings
6. the last step is to assign the group to these policies
a. click the “Assign” button
b. navigate to the organization to assign the policy to, move the group to the right and click “assign branches”

that should do it…

This is what worked for us and I hope it helps someone else out that might experience similar issues.

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

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by Jodi on Tue Jul 10, 2007 12:11 pm

Thanks Bryan and Zac T,

We excluded the dwrcs.exe in Pest Patrol and everything is back to normal (at least on the computers we have copied the file back to). Your help has been much appreciated.

Jodi
________________________________________
Re: The Dameware mini remote service is not running on XXX.
by bryan on Wed Jul 11, 2007 6:53 pm

Hi Jodi,

You're absolutely welcome, and thanks so much for letting us know this resolved your issues.
I'm glad we were able to help out.

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

________________________________________
Re: The Dameware mini remote service is not running on XXX.
by wuliping0011 on Fri Apr 16, 2010 8:39 pm

Bryan wrote:Hello Jodi,

Exactly what version of the MRC Client Agent Service do you have installed on these remote machines (right-click on DWRCS.EXE, then select the Version Tab)?

Also, what Operating System and Service Pack level is installed on these remote machines? Are these 64-bit Operating Systems?

Also, did you recently install, or update definitions for any type of Anti-Virus or Anti-Spyware software? Because it could be that this software is mistakenly flagging some of the files within the MRC CLient Agent Service.

Microsoft's System Error: 2 basically means File Not Found. So based upon this error it appears that some of the necessary files for the MRC CLient Agent Service may have been deleted on these remote machines somehow. They also could have been mistakenly flagged and deleted by some type of Anti-Virus or Anti-Spyware software on your machine or your network as well.

Therefore, the first thing you need to do is verify that all the files are still there in the System32 folder on the remote machine (SYSWOW64 for 64-bit Operating Systems). If any files are missing, then this is the source of your issues, and you'll have to track down exactly what deleted these files on these machines.

For a listing of necessary files, you can take a look at the following KB article on our website:

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

though that i know a lot.thanks

I know I am able to use DRS to install the DWRCS service on remote computers in a batch job, however is there any way that this job can be scheduled to periodically install the service on all computers in the domain? Thanks

Hello!

We plan to use Dameware DRS in our environment, but we have some issues with this product.

Some of our computers are located at the remote sites and different subnets. When we try to get access to them through (DRS - Active Directory - Active Directory Computers), attempt to connect failing, because DRS trying to get computer using NETBIOS-name.

Can DRS use DNS-names of computers?

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.

remove from system tray?
by JonK on Fri Jun 13, 2008 8:09 am

Installed this on a couple computers here at work - i noticed a red/green icon in the system tray. Can I have that NOT show up on clients? Our clients will flip out if they figure out we're able to connect to their machine (even if its to help them!).

Also - a co-worker ordered two licenses but we didn't receive any e-mail regarding it! He didn't print the order receipt either - who can I contact for help?

JonK
________________________________________
Re: remove from system tray?
by Marty on Fri Jun 13, 2008 9:33 am

Hi JonK,

Unless the software is running in Evaluation mode, you can hide the System Tray icon by disabling the option to "Enable SysTray icon." This setting is on the client agent side (remote machine) and can be accessed by right-clicking on the icon and selecting "Settings." Then select the "Additional Options." If you need help with the other notification settings, please feel free to contact Technical Support at support@dameware.com and they will be more than happy to help.

Also, regarding the purchase of licenses, contact our Sales department at sales@dameware.com or at (985) 871-7519 M-F 9:00am-5:00pm CST and they can tell you the status of your order.

Hope this helps.

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

________________________________________
Re: remove from system tray?
by JonK on Fri Jun 13, 2008 10:25 am

Thank you - is there a setting in a config file or ini file that I can set so that the tray icon is disabled by default when its pushed out to the client?

Also - we got our email about our order - thanks!

JonK
________________________________________
Re: remove from system tray?
by Marty on Fri Jun 13, 2008 11:03 am

To ensure that your custom settings are used and not the default settings when you connect to a remote machine, you will want to perform one of the following functions:

1. Remove, then reinstall the Client Agent Service on the remote machines with the option to "Copy configuration file DWRCS.INI" enabled. This particular *.INI file is only copied during the Client Agent Service installation and is not reconfigured each time a connection is made.
2. Manually copy over a new DWRCS.INI file to the remote machine, then stop & restart the Service for the new settings to take effect.
3. Connect to the remote machine, select View / Remote Server Settings and make any necessary changes.
4. Use the NT utilities software's Services View to batch remove & reinstall the Client Agent on your remote machines.

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

________________________________________
Re: remove from system tray?
by JonK on Fri Jun 13, 2008 12:36 pm

Thanks - but is there a setting in the ini that I can do to disable tray icon by default? I don't see it anywhere.

JonK
________________________________________
Re: remove from system tray?
by JonK on Fri Jun 13, 2008 1:03 pm

Ok I figured out how to keep from notifying that I connect, how to keep the system tray from showing, but how do I make it so the client computer doesn't blink the whole screen black?

JonK
________________________________________
Re: remove from system tray?
by Marty on Fri Jun 13, 2008 2:11 pm

Detailed instructions on each of these notification settings can be found in the following forum post:

Observe user's desktop with their knowledge?
http://forums.dameware.com/viewtopic.php?f=9&t=128

If the screen continues to go black after you have disabled the Desktop Effects, try connecting without the Mirror Driver. If this does not resolve the issue, please write Technical support at support@dameware.com

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

________________________________________
Re: remove from system tray?
by R2D2 on Thu Feb 17, 2011 5:01 am

Sorry that I pull up an old thread to the top...

I have a problem with the newest Version (7.2.0.0) of the MRC-Server for XP 32-bit. I rolled it out yesterday on our clients and I receive phone calls like "what's this icon". I want to hide it, but it doesn't work.

I turned off the checkbox "Show Tray Icon" in the settings window on the "Additional Settings"-Tab. But the tray icon still doesn't hide, also after a reboot.

Has anyone suggestions what I could do?

Thanks

Edit: I don't know why, but now it works.

________________________________________
Re: remove from system tray?
by Carla22 on Sun Jul 17, 2011 3:49 am

thanks to all the info..
i really appreciate it.
thank's again!! 

Best Regards
Carla

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]

For a preview into features coming up with v11 and a chance to try our Beta, please take a look at our Product Blog Post and complete the survey provided there.

Hello guys

how work damware without AD?

I have version 10.