I took over configuring Dameware 11 and configuring the Internet Proxy (and later the Mobile Gateway) from another admin. He had installed the components on a server which was already running IIS. I can't tell whether it installed web components within IIS or is using another web service. So that would be my first question. How do I confirm whether it is using the default website within IIS? I had setup a second IP on the server to be used only by Dameware so there would be no conflict on ports 80/443 with any previous services using IIS on the server. Now I need to make sure Dameware is only using that IP (I believe I've accomplished that in the settings), and I need to generate a CSR so I can get and install an SSL certificate for Dameware.

Thanks in advance for any help!

People,

How can I deploy Dameware agent to the workstations in the different subnet / VLAN from the central server in my data center ?

Each site offices and user computer objects spread across multiple different OU, so I wonder is there any outage when delivering the agent to the users with any of the way supported by Dameware ?

Thanks.

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?!

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.

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.

version 6.9.0.0 Print Screen
by support on Fri Apr 23, 2010 12:12 pm

My Print Screen button does not work with version 6.9.0.0.
It works in version 6.8.1.4.
Do you know what can cause this function not to work?

Here's what happens:

When the mini-remote window is the active window, and you press the Print Screen button on the keyboard, then try to paste in either Paint or something like MS Word, you either have no option to paste your print screen or in the case of MS Word it pastes an open right paren {i.e. ( }. But, if you click outside the mini-remote window, on the something like the system bar or etc, so that mini-remote is no longer the active window, then you can get a print screen without problems. It's something with the mini-remote being the active window.

Any suggestions or thoughts?
________________________________________
Re: version 6.9.0.0 Print Screen
by Briantir on Wed Apr 28, 2010 10:32 am

Having same issue with the same version. Can't roll it out until this is fixed.
Briantir
________________________________________
Re: version 6.9.0.0 Print Screen
by Kenya on Mon May 03, 2010 12:11 pm

I have the same problem but the workarond for me is to put the dameware screen in
(VIEW ONLY) then print screen works but it's getting annoying and I hope it will be fix soon.
Kenya
________________________________________
Re: version 6.9.0.0 Print Screen
by support on Mon May 03, 2010 1:12 pm

Kenya wrote:I have the same problem but the workarond for me is to put the dameware screen in
(VIEW ONLY) then print screen works but it's getting annoying and I hope it will be fix soon.

For us, View Only isn't an option. What we do as a workaround is click outside the Dameware window (ex: on the system tray or somewhere in secondary screen if you have two screens) to deactivate the Dameware Window (i.e. send it to the 'background' as an inactive window). Then, the print screen will work. But, like you, it's very annoying and an extra step.
support
________________________________________
Re: version 6.9.0.0 Print Screen
by Kenya on Mon May 03, 2010 1:33 pm

support wrote:
Kenya wrote:I have the same problem but the workarond for me is to put the dameware screen in
(VIEW ONLY) then print screen works but it's getting annoying and I hope it will be fix soon.

For us, View Only isn't an option. What we do as a workaround is click outside the Dameware window (ex: on the system tray or somewhere in secondary screen if you have two screens) to deactivate the Dameware Window (i.e. send it to the 'background' as an inactive window). Then, the print screen will work. But, like you, it's very annoying and an extra step.

Yes I understood your workaround from your first post,  for me view only is annoying to activate, do the print screen, then desactivate view only, and I prefer your solution, but my post was more to lead dameware to a solution with all the workaround people experience. also it answer your question that the active windows is not the problem.
Kenya
________________________________________
Re: version 6.9.0.0 Print Screen
by support on Mon May 03, 2010 3:24 pm

Ah, gotcha   Good point about the active window bit not necessarily being the problem.
support
________________________________________
Re: version 6.9.0.0 Print Screen
by bryan on Mon May 10, 2010 4:51 pm

There has to be some little detail that's missing here. I've been attempting to duplicate this behavior in version 6.9, using both PrtScn and Alt-PrtScn and I haven't had any issues with either method. I've tried to and from both Vista and Windows 7 machines, and each time I've been able to paste the contents into Paint. It also works for me when MRC is the Active window, and when it's not the Active window.

So as it looks now, we're going to need a lot more detailed information in order to duplicate this behavior.

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

________________________________________
Re: version 6.9.0.0 Print Screen
by support on Tue May 11, 2010 9:55 am

I'm not sure what more details we can provide. We have tried it on both an XP 32bit box and a Windows 7 32 bit box. For the XP box, the technician uninstalled the old version (6.8.1.4) prior to installing 6.9.0.0, then had the printscreen issue when Dameware was the active window. On the Windows 7 box, we did an upgrade (just installed 6.9.0.0 on top of 6.8.1.4) , but still had the same printscreen problem. When Dameware 6.9.0.0 Mini Remote is the active window, pressing print screen yields a right paren inside MS Word, or no option to paste at all (even doing Ctrl-V) inside Paint. But, if the mini remote window is not the active window, then printscreen works fine.

Are we allowed to attach documents within the forum? If so, how? I'll see if we can get a blackbox recording of the problem on the Windows 7 box.
support
________________________________________
Re: version 6.9.0.0 Print Screen
by noonz78 on Wed May 12, 2010 2:55 pm

You have the absolute worst verification process for member registration.

Turn off UAC Virtualization to resolve this issue.
noonz78
________________________________________
Re: version 6.9.0.0 Print Screen
by support on Wed May 12, 2010 4:34 pm

Thanks noonz78! That worked for us on the Windows 7 box (though we are not too happy with having to turn off UAC completely to get it to work). But, any suggestions for the Windows XP box? As far as we know, the XP box doesn't have UAC virtualization, but it does have the print screen error that the Windows 7 box had. Upgrading that box to Windows 7 is not currently an option due to some specific applications that don't currently work completely under Windows 7 (or XP mode or compatibility mode).

And yes, we agree the Dameware registration process is an experience. 

Re: version 6.9.0.0 Print Screen
by PopeKael on Tue Jun 01, 2010 5:59 pm
Just adding my 2 cents worth - UAC is turned off on my Windows 7 box and the PrtScrn issue is still present. My Windows XP box does not have UAC so i am unable to turn it off yet the problem exists. All systems are patched to Microsoft update cycle -14 days.

The only workaround I can use if to do a full PrntScn then paste into a graphics editor, and then cut out the relevant details for pasting into email or MSWord. This is obviously quite annoying.

BTW - I didn't find the registration process any more challenging than most online forums.
________________________________________
Re: version 6.9.0.0 Print Screen
by jrackler on Thu Jun 24, 2010 3:51 pm

We are currently having the same issue. I have downgraded the user to 6.8.1.4 until this is corrected. We do not have any issues with Vista or 7. My only issue with making the window inactive and doing a screen shot is that most of our users have dual monitors and therefore it captures both monitors. We are simply just trying to catch the one screen.
________________________________________
Re: version 6.9.0.0 Print Screen
by Angelu5 on Thu Jul 15, 2010 6:03 am

jrackler wrote:We are currently having the same issue. I have downgraded the user to 6.8.1.4 until this is corrected. We do not have any issues with Vista or 7. My only issue with making the window inactive and doing a screen shot is that most of our users have dual monitors and therefore it captures both monitors. We are simply just trying to catch the one screen.

Having exactly the same issue.
Happens when upgarding from the previous version & from a completely new install of this version of the product.
Have roughly 25 clients using this software and roughly 80% of them are experiencing this problem where the other 20% are completely uneffected.
Do we have any ideas as to what is causing this problem?

Cheers
Angelu5
________________________________________
Re: version 6.9.0.0 Print Screen
by Jon on Thu Jul 15, 2010 11:51 am

This seems to be a Problem With Windows Xp and this version. any more update on this Problem? as Screen Prints are nice to use for documenting. but the workarounds are not the slution.

Thanks
Jon
________________________________________
Re: version 6.9.0.0 Print Screen
by jpflepsen on Wed Jul 21, 2010 6:21 pm

I'm having the exact same problem with v 6.9.0.0 on WinXP SP3 32bit current with all Windows updates. No option to paste anything into paint, and a right paren only pastes into Word.
jpflepsen
________________________________________
Re: version 6.9.0.0 Print Screen
by xplodr on Thu Jul 22, 2010 11:56 am

Same issue here running Windows Vista Ultimate x86 w/ SP2 and on Windows 7 Pro x86.

Has this been acknowledged yet as a known issue?
xplodr
________________________________________
Re: version 6.9.0.0 Print Screen
by flagscrewer on Mon Jul 26, 2010 5:26 am

This was our solution for this issue:
Start Dameware - select the host - click under file - remove service - click under file - install service - select Copy FIPS Modules. After installation print screen will be available.
flagscrewer
________________________________________
Re: version 6.9.0.0 Print Screen
by Marty on Mon Aug 02, 2010 2:13 pm

Hello,

Another user who reported this also reported that disabling the "Enable Remote Clipboard" setting witihin the application allowed him to Print screen properly.

We appreciate the feedback.

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

________________________________________
Re: version 6.9.0.0 Print Screen
by Cardinalih on Fri Oct 22, 2010 11:44 am

support wrote:
Kenya wrote:I have the same problem but the workarond for me is to put the dameware screen in
(VIEW ONLY) then print screen works but it's getting annoying and I hope it will be fix soon.

For us, View Only isn't an option. What we do as a workaround is click outside the Dameware window (ex: on the system tray or somewhere in secondary screen if you have two screens) to deactivate the Dameware Window (i.e. send it to the 'background' as an inactive window). Then, the print screen will work. But, like you, it's very annoying and an extra step.

Good afternoon,
I made this and it works.

Thank you,
Best regards.
Cardinalih
________________________________________
Re: version 6.9.0.0 Print Screen
by support on Mon Nov 15, 2010 4:32 pm

Cardinalih wrote:
support wrote:
Kenya wrote:I have the same problem but the workarond for me is to put the dameware screen in
(VIEW ONLY) then print screen works but it's getting annoying and I hope it will be fix soon.

For us, View Only isn't an option. What we do as a workaround is click outside the Dameware window (ex: on the system tray or somewhere in secondary screen if you have two screens) to deactivate the Dameware Window (i.e. send it to the 'background' as an inactive window). Then, the print screen will work. But, like you, it's very annoying and an extra step.

Good afternoon,

I made this and it works.

Thank you,
Best regards.

We're note sure what you mean. Did you create a program/script/something that works with Dameware to prevent the issue, or are you saying that you tried our work around and that it worked for you?
support

-------------------------------------------------------------------------------------------------------------------

Re: version 6.9.0.0 Print Screen
by MilkMonster on Mon Dec 20, 2010 10:03 am

If 6.8.1.4 worked and 6.9.0.0 does not, then surely you (DameWare) can do a delta between the two which will show you where in the code the problem lies.

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.

SFT not working
by fabvit on Tue May 17, 2011 3:47 am

SFT not working:

1. I've installed DWMRC v7.5.6.0 on my local windows 7 pro 64 machine.

2. I've installed DWMRCS Agent v7.5.6.0 on the remote pc of one of my customers windows XP Pro 32 bit SP3. Please note that after Installing the Agent I've rebooted the pc. I've installed the Agent after having logged in as Administrator.

If I try to upload from my pc, right clicking on a file on my desktop I can see in the context menu:

DameWare MRCC -> Copy to Remote Host: HOST_NAME

but pressing it does blink and does not upload the file.

On the remote pc things are worse: the DameWare MRCC context menu's menuitem is completely missing.

Please note that on the remote machine I have enabled SFT in the tryicon settings.

This is specific to this connection: I can upload/download files and folders when connected with other customers.

Any idea?

Thank you
fabvit
________________________________________
Re: SFT not working
by DawgBone on Tue May 17, 2011 10:08 am

Does the file get copied when you drag and drop it into the application? (local >remote)
Does the file get copied if you use the SFT Drop window? (hold down shift+blue folder)(remote>local)

This would determine if it is the SFT feature failing or the right click context that's failing.

DawgBone
________________________________________
Re: SFT not working
by fabvit on Wed May 18, 2011 2:51 am

> Does the file get copied when you drag and drop it into the application? (local >remote)

No, the file is not get copied when I drag drag and drop it into the application (local >remote)

> Does the file get copied if you use the SFT Drop window? (hold down shift+blue folder)(remote>local)

No, the file is not get copied if I use the SFT Drop window (hold down shift+blue folder)(remote>local) and an notification dialog appears:

The MRC Client Agent are not ready for file transfer

Some idea on how to solve this issue: SFT is foundamental to my day to day support activity.

Thanks, fv

--
fabio vitale
fabvit
________________________________________
Re: SFT not working
by bryan on Thu May 19, 2011 11:19 am

If there are errors with SFT (or any other feature) there should be 1 or more dwmrcs entries in the Application Event log on the remote machine. Please copy and paste the full text of each of those entries and send this information to our support team at Support@dameware.com so we can review it. Please also send another screen shot of the exact error that's displayed when you try to open the SFT drop window on the remote machine (Shift + blue folder).

So nothing happens when you drag a file/folder from your local machine into the Open MRC connection window?

Also see if the %windir%\dwrcs\sft folder exists.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com
________________________________________
Re: SFT not working
by bryan on Fri May 20, 2011 3:59 pm

Hi again Fabio,

One more thing you might want to try is to update the MRC Client Agent service on the remote machine once you get connected, in case there is some type of file corruption. Make your MRC connection, then select File / Update Client Agent from the MRC main menu. Then try your SFT again.

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

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

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

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

Hi All!

I was wondering if someone knew when Dameware Mini Remote Control v12 is coming out. My boss thought he saw an e-mail about it come out, but he wasn't sure. Just here to see if anyone else saw an e-mail and possibly remember a date (if possible).

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.

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

I am new to Dameware and have found the install/configuration very frustrating.  I have called support three times in the process (last call was 2 hours), so now I will try this forum.

I got the server setup and want to deploy DRS to the techs.  I found a link to this kb on using the msi to install, but I do not see the msi - only the exe (the kb was for ver 9.)

In order to keep working I just installed DRS with the gui but then it prompts me for the license (which is fine), BUT it does not give the option of pointing the install to the central server to get the license.

Can someone provide guidance?  I have read the install manuals but they do not seem to be oriented to an enterprise admin.  Really an Getting started / best practice document would be helpful to someone new to the product.

Thanks.

Hi

We are in the process of migrating to Dameware RS and MRC from Teamviewer.  We are having a number of issues during testing that I don't really want to be landing on the support desk as its going to make a hard job harder for them.

Namely issues arise around Internet sessions.  The thing is we support around 75 companies, all separate, and range in size from 5 to 100 users.  Getting Dameware agent client on all those systems just isn't plausible, so the Internet session option makes full sense.

However we are getting issues with this and wondered if others have gotten over the same:

Windows Firewall - forever blocking the software, sometimes not giving the option to unblock either;

IE Popup blocker - blocking the download connection software page;

Certificate Error - Have installed a GoDaddy SSL certificate on the Internet Proxy, and it does present the certificate to the end user, but its still saying the site/certificate can't be verified, even though the URL etc. all square up.

MAC OS - Seems no way to offer Internet session to MAC OS users?

Any help/advice appreciated.

Thanks Guys.

I took over configuring Dameware 11 and configuring the Internet Proxy (and later the Mobile Gateway) from another admin. He had installed the components on a server which was already running IIS. I can't tell whether it installed web components within IIS or is using another web service. So that would be my first question. How do I confirm whether it is using the default website within IIS? I had setup a second IP on the server to be used only by Dameware so there would be no conflict on ports 80/443 with any previous services using IIS on the server. Now I need to make sure Dameware is only using that IP (I believe I've accomplished that in the settings), and I need to generate a CSR so I can get and install an SSL certificate for Dameware.

Thanks in advance for any help!

To use the unattended OTI, can someone please answer the following questions?

1. Will I need to install the centralized server?

2. Does the server need to be on at all times (determines which machine I'll be installing on)

3. Will the server be the PC I have to access the remote machines from, or will I be allowed a laptop/desktop?

4. If we are allowed a laptop or desktop, how do I notate that it's the machine that will be doing the accessing? (I'm sure I have to notate the machine somehow for licensing)

5. I will be the only person allowed to use Dameware, so we purchased 1 license and a years support and upgrades...
    Is this sufficient for me to run about 100 machines in various locations, as long as I'm the only one accessing them from my machine?

Thanks for all of your help!

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

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?

Running windows 7 Pro and when I try to connect to a new system to send the client I get the following error.

Winsock connect error.10060

System message

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Running dameware 11.2.0.91

I have turned off firewall that didn't solve the issue same error.

Reinstall  dameware same issue.

I'm running 5.5.0.2 on a bunch of windows xp stations but we added a new one that is windows 7. When remoting into that station all I get is a black screen but if I use Windows remote desktop simultaneously Dameware will begin to function properly.

Thoughts?

Thanks!

Hi,

I've just downloaded and install Dameware Remote Support Centralized version and installed it successfully in my VM running on my internal network.

How to perform agentless remote user connection using the Intel AMT feature ?

Most of my HP Desktop got Intel AMT feature sticker in front of it.

Thanks,