I'm owner of Dameware NT Utilities (Version 6.9.0.4) And found security issue with it
This was tested also on New Dameware remote support ver 11.2.0.84
With same Problem
The Issue is when changing group membership in AD (Under "Microsoft WIndows Network" -> Groups
Their is no audit in the Security event log of the Domain controller's (Changing with Microsoft tools is audit & Event 5136 is recorded)
we have AD 2008 R2
Anyone else notice this ?
Thanks in advance
Hi all - my name is Chris Moyer and I'm the Dameware Information Developer. Pleased to meet you!
Over the last few months I've revamped the Dameware documentation, and wonder how you like it. We now have two installation guides (centralized vs. stand-alone), two getting started guides (centralized vs. stand-alone), and an administrator guide. Click the links to check out the new docs. Would love to hear what you think!
Thank you,
Chris
Dameware Centralized Installation Guide
Dameware Stand-alone Installation Guide
Dameware Centralized Getting Started Guide
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
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.
If possible change standalone client of DRS to client / server version?
I get this error when I use Dameware SSH client for windows(Ver: 1.0.0.0) to ssh to some of my ESXi servers. Any idea how it can be resolved?
Error Message: connection error: Could not negotiate diffie-hellman-group1-sha1
Any help appreciated..
Regards,
S.G.K !
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
I’m thrilled to announce that Dameware 12.0 is now publicly available. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. Technicians can now support end-user in company network as well as in Internet anytime.
This release brings several bigger and smaller improvements, so let me highlight a few of them:
Dameware 12.0 is available for download on your customer portal for those customers under current maintenance.
If you are not a Dameware user yet, now go and download new version from www.dameware.com now!
Hi there. I'm wondering if there is a way to install Dameware Mini Remote Control so that no one would be able to tell that it's installed on the computer. Thanks!
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?
HI. there is any option in Dameware mini remote control to perform operation on other machine in invisible mode(without his knowledge)?
I'm working with central server Dameware 11.1 and trying to get it to work with smart card connectivity in windows 10. It keeps kicking out an error "SmartCard Driver was installed but requires a system reboot (5.5.105.2)." They remote system was restarted in an effort to troubleshoot, however, the event logs do not show anything else other than
System Message: The operation completed successfully.
(srv 64 bit)
Has anyone seen this yet?
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.
Your logon request was declined. Disconnecting...
by fabvit on Fri Jan 14, 2011 4:23 am
I'm using the invitation mechanism in DWMRCS v7.
I've noticed that if I leave checked the Require Permission while creating an invitation, later on when I try to connect to this machine I got a dialog:
Your logon request was declined.
Disconnecting...
Request for permission to remote control encountered an error.
- [0]
If I remove the check from Require Permission while creating an invitation, later I can connect to this machine.
What is the purpose and how to setup the Require Permission mechanism.
--
tanks, fabio
Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 3:47 pm
Thanks very much for your feedback on this.
We were able to reproduce this issue and we should have it fixed shortly.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by bryan on Fri Jan 14, 2011 5:51 pm
Hello Fabio,
We wanted to let you know we just finished updating all the files on our website. Since this is only a minor update, you will have to remove the old MRC Client Agent from your remote machine, then remove your current MRC v7 install on your local machine. Next, download and install the most current files from our website. Then you can reinstall this newer Client Agent Service onyour remote machine.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Wed Feb 23, 2011 4:22 am
I have the same problem while trying to connect to one specific client running Windows 7 x64. After a few seconds I get the message "Your logon request was declined", but there was norequest shown on the users screen.
I'm running DameWare Mini Remote Control 7.2.0.0 x64 and I have installed the latest agent on the client. I have enabled the option "Permission required" on the client agent.
In some cases in the past, it worked to restart the DameWare MRC Service on the client or to reinstall the service. In this case, it didn't At the moment, I can advise the user to lock his screen, then I can connect to the desktop without requiring a permisson.
Re: Your logon request was declined. Disconnecting...
by Siggi on Tue Mar 01, 2011 10:45 am
No ideas?
It's a big problem for us at the moment and we're thinking about going back to v6...
Re: Your logon request was declined. Disconnecting...
by bryan on Tue Mar 01, 2011 11:09 am
Have you tried the most current version of the software, which is 7.3 not 7.2 ? You must also update the Client Agent on the remote machine to v7.3 as well.
It souds to me like the DWRCST.EXE (SysTray Icon) process is not running on the remote machine for some reason. You can open Task Manager and check for this process. It should be running anytime there is a user currently logged into the desktop on a remote machine, and the remote machine is not currently at the Logon Desktop or Lock Screen.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 03, 2011 3:40 am
I've just tried the 7.3 today. I also removed the old Client Agent on the remote machine and installed the current one. I checked the DWRCST.EXE process in the task manager, it is running.
The problem stays the same.
Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 10, 2011 4:45 pm
Please try downloading and installing v7.4 of the MRC software, and then please make sure you update the MRC Client Agent Service on the remote machien to v7.4 as well. We found an issue with a socket API that could return different results on some OS’s.
Your feedback is appreciated.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Fri Mar 11, 2011 4:35 am
It does not work with 7.4 Same problem.
Re: Your logon request was declined. Disconnecting...
Marty on Fri Mar 11, 2011 12:21 pm
Hi Siggi,
We are still unable to reproduce this behavior in our environment, however we would very much like to resolve this issue. With that said, can you email support@dameware.com so we can provide you with some customized troubleshooting steps for your environment?
Also, if there are any DWMRCS application event log entries on the remote machine, forward those back to us in your email as well.
Thanks so much and we appreciate your help!
Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by bryan on Wed Mar 16, 2011 10:00 am
With the help of one of our customers (Thank You Frank !!!) we have confirmed this issue will be resolved with the release of v7.5 of the software.
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Siggi on Thu Mar 17, 2011 9:55 am
It works!!! Thank you so much, Bryan (and Frank )
Very little new issue: The version number in the NT Utilities application is shown as "7.4" even in the 7.5 package, so we were a little confused with the update process.
Re: Your logon request was declined. Disconnecting...
by bryan on Thu Mar 17, 2011 2:06 pm
Hi Siggi,
You're most welcome, and thanks very much for your feedback on this. We really appreciate it.
With regard to the version, please try this out for me. First remove your existing install of DNTU via Add/Remove programs. Then download and install v7.5 again from our website to see if you can still reproduce this behavior.
Your feedback is appreciated.
Best Regards,
Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
Re: Your logon request was declined. Disconnecting...
by Adrian on Mon Nov 28, 2011 10:56 am
Hi, I am having the same problems as this. The slight difference is my PC is Windows 7 64 bit and the client is 32bit XP. If I use a Windows 7 32 bit it works fine
Thanks
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
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
Bonjour,
J'ai recemment eu un problème avec dameware, dès que je connecte sur un poste à distance, cela ferme la session qui était ouverte.
Est ce qulqu'un a déjà eu ce problème?
Os: Windows 10
Hello DameWare users!
Here is a brief guide to shows how to gather information from computers in your network or domain using the DameWare Exporter tool included with DameWare Remote Support.
Objectives:
1- Get "Installed Software" data from computers in my network to create a report.
2- Get the information in a CSV file format so it can be easily imported into an Excel spreadsheet
3- Get the information from several computers in a single file
First, you have to launch the tool. You can find it in the same location as the main DameWare Remote Support application (Start > Programs > SolarWinds > DameWare Remote Support 9.0 > DameWare Exporter). You can recognize it easily by the colors in the icon (blue/yellow) :
In the Exporter tool you must change the settings so the files created have the CSV format instead of XML (which is used by default). In this example we want to get "Standard" information (which basically means we are pulling data from the machine instead of Active Directory) so that's the tab we need to modify:
NOTE: The "Single File" option here indicates that a single file will be made per-machine including all properties selected. It DOES NOT mean a single file will include each computer.
Once the output file type is set, do the following:
1- Under "Task List" uncheck everything except for Standard Properties - Software.
2- Click the "Add Machines" button to include the computers you want to survey.
3- Make sure all the systems in the "Computer List" are checked
4 - Click on "Start Exporting"
After this you will end up with a .csv file for each computer you surveyed. Unfortunately, DameWare Exporter doesn't feature an option to generate a single file for all the computers. However, CSV files are easily merged using the Windows copy command. Place all the files in the same folder and run the following command in the Command Prompt:
copy *.csv allcomputers.csv
This line will create a new file, "allcomputers.csv" (you may use the name of your choice) that will be a merging of all .csv files found in that folder.
Hi all.
I work as IT support at an offshore branch. The main headquarters uses Dameware Mini Remote Control Server (V 11.2.0.91) and we have 4 backup PCs located at HQ. My constant argument with the HQ IT department is that we require remote access permanently while they insist that only HQ should be responsible for the devices there.
My question is this: is it possible in Dameware to be provided with access to a specific PCs only? Am I dealing with a technical limitation here? I would like to explain to them if there is a method where I would be provided with access to only the specified PCs and nothing else.
Appreciate your help, thanks.
I have been running on Windows 10 for quite a while (since last fall) and using Dameware Remote Support (11.0.0.1003). Recently I upgraded to the latest W10 version (1607). Unfortunately, this broke the remote clipboard. I have a co-worker who had the same experience. The only difference between the two was that his mini-remote worked fine, then he upgraded to the "full-version" (as we call it).
Any ideas about how to fix this? I would have thought a reinstall of the application, but with the fresh install that was broken that didn't seem like a solution. Any thoughts?