I recently upgraded to Windows 10 and DRS 12. Since then I have been getting this in the information tab. On the Browser tab I don't get anything under the Microsoft Windows Network like I used to.
I am new to this forum and trying to search didn't seem to bring anything up. I appreciate any help anyone can be as I don't think I am getting full usage of DRS 12 because of this issue.
Thank You.
Hello,
I just installed the Dameware Remote Central Server on a fresh Windows Server 2012R2.
Unfortunately I cannot connect with the admin console and the server is not running properly.
In the wizard it just shows me, that the Server is "Not running, connection problems found". But not any detail about it.
Firewall is off, Server is in AD connected, DNS is fine and works from other machines to the server.
The admin console tells me "DameWare Server was not found on specified location. Please try different IP/Hostname....".
Do I have to do s.th. special to get the server running?
Can't find anything in the documentation.
I'm glad for every hint and help.
Thank you and have a nice day.
Kind regards,
Markus
DameWare 12.1 HotFix 1 is now available for download in your customer portal. Below are the release notes for this hotfix.
Dameware Mini Remote Control 12.1.0 Hotfix 1
=============================================
This hotfix addresses the following issues:
* MRC double-click issues while connecting to remote machines with enabled 'Show remote cursor' option
* Issues with shared sessions when second connected MRC client did not receive screen image from remote machine correctly
* IPv6 connection fixes while connecting to IPv6 remote machines
This hotfix requires Dameware Mini Remote Control version 12.1.0.
Warning: SolarWinds strongly recommends that you edit the files mentioned in this document only as instructed. Any additional modifications to these files may result in system performance issues or may cause an error.
Install the hotfix on DameWare Proxy
===================================
1. Go to the Dameware Proxy machine.
2. Turn off the Dameware Proxy component in the Configuration wizard. If the Dameware Server runs on the same computer, turn it off as well. Do not close the Configuration wizard.
3. Open the DameWareDB.sdf database file using the free CompactView tool.
By default, the file location is as follows: C:\Program Files (x86)\SolarWinds\DameWare Central Server
4. Go to the RoleConfiguration table and clear all check boxes in the 'Status' and 'IsInitialized' columns.
5. Remove all files from the binary folder.
By default, the folder location is as follows: C:\Program Files (x86)\SolarWinds\DameWare Central Server\WebServerStaticContent\binary
6. Extract Hotfix 1 archive, and copy the contents of the Dameware Proxy folder into the binary folder.
By default, the folder location is as follows: C:\Program Files (x86)\SolarWinds\DameWare Central Server\WebServerStaticContent\binary
7. Open Services, and select Stop the Dameware Server service.
8. If you have Dameware Proxy installed on a separate machine (Dameware Server installed on another machine):
a) In the opened configuration wizard, turn on the Dameware Proxy component.
b) Pair the Dameware Proxy component with Dameware Server (on the server side).
9. If you have Dameware Proxy on the same machine as the Dameware Server:
a) In the opened Configuration wizard, turn on the Dameware Proxy component.
b) Turn on the Dameware Server component.
Install the hotfix on Dameware Mini Remote Control
==================================================
If you have MRC x86 version, copy the contents of the MRCx86 folder to the MRC installation folder on the computer.
The default location of the folder for Centralized Version as a part of the Dameware Server installation is as follows: C:\Program Files (x86)\SolarWinds\DameWare Remote Support
If you have MRC x64 version, copy the contents of MRCx64 folder to the MRC installation folder on the computer. By default, the installation folder location is as follows: C:\Program Files\SolarWinds\DameWare Mini Remote Control x64
Warning: If you have the remote control agent already installed on your remote machines from the Dameware 12.1 release, remove and install it manually from MRC (with Hotfix1 applied).
For more information, see https://support.solarwinds.com/Success_Center/Working_With_Support.
My workstation has two monitors. The remote system is a VM on our network. I've been using Windows RDP (mstsc /admin) app to connect to remote system. With this program I am able to work on the remote VM with my two physical monitors, each having their own desktop. This is really nice for development purposes for me. There are no scorllbars and it's full screen with the full resolution my video card can handle. It's as if I was working on the VM directly with two monitors. This is really nice.
Today I had DameWare ver 12 installed by our systems gurus and I was trying to setup the same experience without success. Is this even possible?
The closest I came up with was to stretch DameWare window across my two monitors, but then things get skewed and both vertical and horizontal scrollbars appear which makes development process a pain.
So, is it possible to configure DameWare to use like the windows native "mstsc" program?
Reason for looking at other solutions is due to a global disconnect policy the company has put in place that terminates all my open dev tools after 30 min of inactivity. DameWare ignores that policy.
Thank you.
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]
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?
When I connect to a Surface Book with Windows 10 1709 installed Dameware doesn't recognize multiple monitors.
All of our systems are Surface Pro 3 / Surface books. Plugged into Surface Docks.
When I connect to the Pro 3's with Win8.1 I can see all three screens.
When I connect to the Pro 3's with Win10-1709 I can see all three screens.
When I connect to the Surface Books with Win10-1607 I can see all three screens.
When I connect to the Surface Books with Win10-1709 I cannot see all three screens.
I am in the process of rolling out 1709 to everything and this is going to become a huge issue really soon. This is in addition to the performance issues with Dameware on 1709.
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
Does anyone know of a quick way to change the settings on the clients on PCs and Laptops so that when a connection is may they have to accept the connection and not let the connection take place without user imput
Dameware Mini Remote Control 12.1.0 Hotfix 3
is now available for download in your customer portal. Below are the release notes for this hotfix.
This hotfix addresses various security issues and crashes in Dameware Mini Remote Control version 12.1.0.
Hotfix 3 also includes all fixes from Hotfix 1 and Hotfix 2 for Dameware Mini Remote Control version 12.1.0.
Warning: SolarWinds strongly recommends that you edit the files mentioned in this document only as instructed. Any additional modifications to these files may result in system performance issues or may cause an error. Make a backup of the files mentioned in the instructions below if you want to uninstall this hotfix later.
Install the hotfix on DameWare Proxy
Install the hotfix on Dameware Mini Remote Control
Install the hotfix on Dameware Remote Support
Uninstall the hotfix
For more information, see https://support.solarwinds.com/Success_Center/Working_With_Support.
Last year when we renewed our licenses we upgraded from ver 9 to version 11. I put together a Centralized server which everyone now logs into to use DameWare. However, when I tried to enter the keys into the License Activation program it wouldn't accept them and I had to open a service request to get it resolved so we could use DameWare. Earlier this year I expanded my license count, and again, when I tried to update using the License Activation program it wouldn't accept the keys so I had to open another service request.
I just upgraded to the new Version 11.2 and renewed my licensing again for another year. However, it is not reflecting in either the Server Admin Console or the Activation program. Both still show the license is only valid through the middle of next week and the Admin Console comes up w/ warnings that there is only 7 days left. When I click the "I Already Paid" button in the warning it just opens the web page for me to sign into. I found the License Manager out there and downloaded it. I ran the sync on that and it comes back fine, shows that I'm good through next year. Still not updating in the Admin console. I can enter the keys from my info on the customer portal in the Activation program and at least it shows that it takes them - used to always fail. However, the dates are still showing that my licensing is about to expire.
What am I missing?!! Why isn't it updating the date info for me so I'm not seeing the errors in the Admin console any longer?!
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?
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
I recently upgraded to Windows 10 and DRS 12. Since then I have been getting this in the information tab. On the Browser tab I don't get anything under the Microsoft Windows Network like I used to.
I am new to this forum and trying to search didn't seem to bring anything up. I appreciate any help anyone can be as I don't think I am getting full usage of DRS 12 because of this issue.
Thank You.
Can anyone help us. We are running dameware version 12.0.0.509 and when we remote into a Windows 10 Device (1703) and its at the login screen it is extremely slow to respond. Once we get logged in its fine however the login screen is extremely slow. How can we fix this.
Hi.
In my company there are internal and external users. As far as I understand we need Dameware Centralized with Dameware Internet Proxy to support external users.
Also my company has several remote offices in several cities. In remote offices there are computer technicians (they will use DRS or DMRC if my company buy your soft )
I have a question: If one of our remote offices will lost connection to the central office (with Dameware Central Server) will be able a computer techician in that remote office use DRS or DMRC to support users in the same remote office?
(That is, if we use Centralized Installation can we then run DRS or DMRC without connection to Dameware Central Server?)
My workstation has two monitors. The remote system is a VM on our network. I've been using Windows RDP (mstsc /admin) app to connect to remote system. With this program I am able to work on the remote VM with my two physical monitors, each having their own desktop. This is really nice for development purposes for me. There are no scorllbars and it's full screen with the full resolution my video card can handle. It's as if I was working on the VM directly with two monitors. This is really nice.
Today I had DameWare ver 12 installed by our systems gurus and I was trying to setup the same experience without success. Is this even possible?
The closest I came up with was to stretch DameWare window across my two monitors, but then things get skewed and both vertical and horizontal scrollbars appear which makes development process a pain.
So, is it possible to configure DameWare to use like the windows native "mstsc" program?
Reason for looking at other solutions is due to a global disconnect policy the company has put in place that terminates all my open dev tools after 30 min of inactivity. DameWare ignores that policy.
Thank you.
Hello everybody,
we are running the actual version of DameWare 11.1.0.170 for our Administrators to have some smooth remote support ability.
There is only one problem/missed function, we want to have.
We want to see which user is logged into a machine, when we are checking our "Active Computer list" in DameWare.
Also I know this can be done via the Active Directory (add to the description field on the computer), but then we have some double maintenance.
Is there any functionality on DameWare to check which user is logged into. For example is DameWare able to readout the "User and Groups" of Windows or the registry to check whether which user has logged in today?
Thanks for any answer.
Hopefully you can help me.
Best Regards,
Philipp
Hi
Does anyone know of a quick way to change the settings on the clients on PCs and Laptops so that when a connection is may they have to accept the connection and not let the connection take place without user imput
hello support,
i need to found the old version 6.9.0.4 of dameware because want to upgrade the my current license version of this product 6.8.0.4
anyone know where this old version is available ?
very thanks for support
francesco