Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out.  I can't get it reinstalled - keep getting the message   "There is a problem with this Windows Installer Package.  A program run as part of the setup did not finish as expected.  Contact your support personnel or package vendor.".

So far, I've tried:

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

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

Not sure what to try next.

Ideas?

Hello,

in all computers in the shutdown menu does not appear running applications ( Running Application View shows empty ).
Thanx for your help.

We currently have Dameware for remote access. When expanding the server it lists all the machines/workstations that are listed in AD. However in AD all those machines are categorized in OUs, but the OUs are not showing up in Dameware. As I have to remote in it would cut down on time not having to search the whole list for that persons computer number. Instead I can just go into their OU that we have by department and find it.

Thanks

I'm happy to share with you we are coming very close to the next public Beta of Dameware. Before we will have bits available I'm looking for help on getting early feedback on our next Beta. This Beta is focused on Web Help Desk (WHD) integration and I will demonstrate the integration feature during short call. I'm also keen to hear feedback on some early thoughts of next release scope, so if you are interested to participate, provide feedback on WHD integration and also on release after that please let me know in comments!

Please note, that this is a Beta Demo and I will organize calls on first comes first serves basis . However I will make sure to include anyone else in second Beta and will share installation bits.

Looking forward to hear from you!

Hi!

Is there a way to save the view settings in Dameware browser?

Since we´ve 100s of clients and not the fastest net, retrieving this information via AD is very time consuming. I´d simply like to do a one time scan

and afterwards only when new clients are added to AD.

So all I wish, is to save the settings and not refreshing them every time in Dameware browser.

Thx,

CG

Hello,

I desire to know remote capabilities.  For example, if I desire to share my screen session with a non network computer & I have the DRS software installed, can another computer that I invite, remote into my session even if the DRS software does not exist on that machine?  If so, what are the steps to initiate this?

Thank you.

Kevin

I would drop some of my PDF guides here, leave comments and feedback on how we could improve them. Some of them will be how to's and so on and so forth.

Hope this would be able to help some of you guys!

Centralized Logging Feature - version 11.x.x.xxxx

Guide for using the MSI builder (Guide for agent.pdf)- version 11.x.x.xxxx

Guide for manually joining the internet session - version 11.x.x.xxxx - This came from a customer our thanks

many more to come!

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!

How do I uninstall DameWare DRS  (V. 11.1) and recover the license for another machine

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

I notice after installing the client for DameWare Remote Support that the Remote Support Service 2.6 (DameWare NT Utilities) isn't also installed and has to be manually installed and started on my clients in order to do remote commands etc. Anyway to include that service and automatic start when I'm rolling our clients?

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

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.

one more time about user notify dialog
by MasTiCorE on Mon Nov 19, 2007 3:14 am

i knew FAQ, search do not give me answers.

i want to connect to users without confirmation notify dialog.
i've entered key into dmware nt utilities, also, as it in FAQ, i tryed ro re-activate dameware mini remote control. Also ths not helped.
before install i've editied configuration file, set no notify dialog, and installed service with this configuration.
Not helped. Why?

PS: sorry for my bad english, no practice..

Re: one more time about user notify dialog

by bryan on Mon Nov 19, 2007 4:33 am

Is this a "Permission" dialog that the user must click on "Accept" to allow you to connect? Do you see the text "Waiting for CLient to Accept the Connection" dispalyed within your Status bar at the bottom of your MRC window?

Or is this the Notify dialog that is displayed in the lower right-hand corner of the screen after you have already connected? Do you see the text "Evaluation" displayed within this Notifywindow?

Your feedback is appreciated.

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

Re: one more time about user notify dialog
by MasTiCorE on Mon Nov 19, 2007 7:58 am

Bryan wrote:Is this a "Permission" dialog that the user must click on "Accept" to allow you to connect? Do you see the text "Waiting for CLient to Accept the Connection" dispalyed within your Status bar at the bottom of your MRC window?

yes. I want to hide it.
user do not see icon of dmware in tray, no menu
but "Permission" dialog is showing every time that i want to connect.
user can click on "Decline". But i want, that user do not know about connected people to his computer.

Bryan wrote:Or is this the Notify dialog that is displayed in the lower right-hand corner of the screen after you have already connected? Do you see the text "Evaluation" displayed within this Notifywindow?

nope, no evaluation enyware.

Re: one more time about user notify dialog
by bryan on Tue Nov 20, 2007 11:19 am

So this is actually the Permission Required dialog, not the Notify dialog.

The need for Permission (Accept/Decline) when connecting to a remote machine using the MRC software is primarily based upon what right you have within the O/S security on that remote machine. However, the current Desktop State on the remote machine, and also some settings within the software itself are also factors in this equation as well.

Therefore, the very first thing you need to examine is what rights your credentials have within the O/S security on this remote machine, Administrator or non-Administrator, and by non-Administrator this refers to everyone that is not a member of the Administrators group on that machine either directly or indirectly via some other group membership.

There is also a "Permission Required" setting within the MRC Client Agent Service on the remote machine as well. Here is some additional information with regard to Permission that will hopefully help you out:

Administrators:

Administrators by default do not require permission in order to connect to any remote machine, unless you enable the “Permission Required” setting within the MRC Client Agent Service (at the top of the Additional Settings Tab). Then any Administrator would also require permission to connect. However, this does not apply when the remote machine is currently at the Logon Desktop or Lock screen. There is no way to prevent any Administrator from connecting to a remote machine when it is currently at this Desktop state.

Non-Admins:

Non-Admins cannot connect to any remote machine without requiring explicit permission from the Desktop user, regardless if the “Permission Required” setting was enabled or not. This is built into the software. The only time a non-Admin could possibly connect without requiring permission would be if the remote machine was currently at the Logon Desktop or Lock Screen. Then access would be Allowed or Denied based upon the “Disconnect if at Logon Desktop” setting (at the bottom of the Access Tab).

There are also several settings within the Client Agent that pertain to non-Administrator accounts that affect permission. If you look at the bottom of the Access Tab within the Client Agent Service, you will see three settings. "Permission Required for these Account Types", "Disconnect if at Logon Desktop", and "View only for these account types", and each of these settings only pertain to non-Administrators (not Administrators).

Another thing to keep in mind is that when you connect to a remote machine, it will be in one of two states:
1. Machine is sitting at the "Logon Desktop" or "Lock" Screen. Hence a user is not present on the remote machine.
2. Machine is not at the Logon Desktop or Lock screen, hence a user is currently logged into the desktop.

Scenario 1:
A non-Administrator tries to connect and the remote machine is currently at the Logon Desktop or Lock Screen. The non-Administrator will only be allowed to connect if the "Disconnect if at Logon Desktop" feature has been disabled (it is enabled by default). If it's enabled, their connection request will be denied with a dialog box stating: "The remote machine is currently at the Logon Desktop. Your credentials do not allow you to access the remote machine at the current desktop state". (just as you were presented with below)

Scenario 2:
A non-Administrator tries to connect and the remote machine is NOT currently at the Logon Desktop or Lock Screen (hence user is logged in). Then you must look at the "Permission Required for these account types" field.

A. If "Permission Required for these Account Types" is enabled, then whoever is currently logged into the desktop of the remote machine will be presented with a Permission Required dialog box asking to Accept or Decline this non-Administrator's connection request. If they press the Accept button, then the non-Administrator will be allowed to connect. If they press the Decline button, or if the dialog times out with no response, then the non-Administrator will not be allowed to connect.

B. If "Permission Required for these Account Types" is NOT enabled, then the non-Administrator's connection will be immediately denied with a dialog box stating: "The Remote machine is not currently at the Logon Desktop. Your credentials do not allow you to access the remote machine at the current desktop state".

I hope this helps.

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

Re: one more time about user notify dialog
by MasTiCorE on Mon Jan 14, 2008 8:21 am

thanks for your answer! It's helped to understand. 

Re: one more time about user notify dialog
by bryan on Wed Jan 30, 2008 4:10 pm

You are absolutely welcome.
It was my pleasure helping you out.

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

Re: one more time about user notify dialog
by lufoxe on Wed Apr 23, 2008 11:48 am

Hi Guys, I am having the same issue, I am a local administrator on the machine, however I am still getting the dailog box   is there anyway to force that off? remotely. I have tried remove and installing the service, also the DWRCs.ini file with the setting unchecked. any help?

Re: one more time about user notify dialog
by bryan on Wed Apr 23, 2008 1:23 pm

Hello lufoxe,

Admin vs. non-Admin rights are not a factor for determining if the "Notify on connection" dialogis displayed when you connect. So are you speaking about the "Notify on connection" dialog that is displayed in the lower right-hand corner of the remote machine when you connect? Or are you speaking about the Permission Dialog, which requires the desktop user on the remote machine to physically press the Accept or Deny button for your MRC connection? If it's the Permissiondialog, then please see my previous post in this thread to resolve this behavior.

With regard to the Notify dialog, the first thing you must look at is if your local copy of the Mini Remote Control program is currently registered, or if its running in Evaluation Mode (Help /About DameWare MRC). Because if it's running in Evaluation Mode, then the notify dialog will always be displayed on the remote machine when you connect, no matter what settings are currently in the DWRCS.INI file. You will also see the text "Evaluation" displayed within the notifydialog as well.

The only other factor would be the actual configuration settings for the Client Agent Service itself, which are located on each individual remote machine. These configuration settings will either be stored in the Registry, or in the DWRCS.INI file, depending on how you configured the Service. During startup, the Service will first look to the "Use Registry for all Settings" key. If this is set to 1 (one), then all the additional settings will be retrieved from the Registry and the DWRCS.INI file will be ignored. If this key does not exist, or is set to 0 (zero), then the settings will be read from the DWRCS.INI configuration file instead.

[HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\DWRCS\Settings]
"Use Registry for all Settings"=dword:00000001 or dword:00000000

However, are you looking at the DWRCS.INI file on your local machine, or in the System32 folder on the remote machine? Because the one on your local machine (in your DameWare Installation folder) is only pushed out the remote machine during Service installation, and then only if you also enable the "Copy configuration file DWRCS.INI" setting during the install. It is not copied to the remote machine each time you connect.

During the installation of the Service, click on the Install Options button then enable the "Copy configuration file DWRCS.INI" setting. Now click on the Edit button to modify the DWRCS.INI configuration file on your local machine. On the Properties dialog, select the "Notify Dialog" Tab and disable the "Notify on Connection" setting. Now click on OK twice to return back to the Service Installation dialog. Click on OK to complete the install of the Service, including your new DWRCS.INI configuration file.

I hope this helps.

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

Re: one more time about user notify dialog
by lufoxe on Thu May 01, 2008 5:52 pm

Thank you,
That has been a great help. I was reffering to the prompt not the eval version dialog.
Thank you very much

Re: one more time about user notify dialog
by bryan on Fri May 16, 2008 11:51 am

Hi lufoxe,

You are most welcome.
I'm glad we could help.

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

Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out.  I can't get it reinstalled - keep getting the message   "There is a problem with this Windows Installer Package.  A program run as part of the setup did not finish as expected.  Contact your support personnel or package vendor.".

So far, I've tried:

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

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

Not sure what to try next.

Ideas?

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

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

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

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

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

about half of the windows 7.1 workstations are not showing up with the OS version (the icon)  so the icon in the domain list looks a little different (grey vs blue computer icon).  the firewall, on or off, doesn't seem to be a difference.  all the workstations are the same release (pro) and patch/SP levels.   most are in the VLAN and like the firewall, seems to be mixed on the icon.

any idea's?  but fix?

When our IT remotes to our Windows PCs they leave behind the DameWare Development Mirror Driver. This driver causes problems with at least one software application, and so it needs to be removed after the remote IT session is ended. How can this be automated?