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

Hi,

i'm currently testing dameware central as my main remote system.

I was happy to see that you guys now support remote hosts through a secured internet proxy i can host on my end ! Specially with the unattended access with version 12

After setting up everything in my test environment, and testing the addition of remote hosts from home and multiple sites, i was a bit disappointed that the file transfer was simply... not available ? Did i miss something ? did i forget to open up a port ?

Or is this really not available through internet proxy connection !? If so, is this planned in a very near future version !?

I am currently evaluating where dameware is now vs TeamViewer when it comes to behind NAT connection, ease of use for the staff, pricing and features...

Now although i'm amazed where dameware is now compared to previous version (I have been using dameware since version 4 on internal network at one of my customer's site). I cannot tell my staff that from now on, we'll have to go through more steps (like an FTP or Cloud storage...) to transfer files on the remote system as opposed to a simple, drag and drop

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,

When establishing a DameWare Internet Session, was requested to download the Remote Agent Deployment package. McAfee detected it as a virus and immediately deleted it. Please advise.

Thanks and regards

HI. there is any option in Dameware mini remote control to perform operation on other machine in invisible mode(without his knowledge)?

Hi,

If I want to connect to Windows 81/10 Hyper-V virtual machines, I got the "error 5: access denied"-problem and dameware wants to install the remoteservice, but the remote support service is already installed and started in the virtual machines.

For physical PC and Windows 7-Virtual machines it works, but not for windows 81/10 virtual machines.

What to do?

Will DRS have the ability to open a remote powershell window similar to a remote console? I know powershell has the ability to do remote commands but I would like to keep the solution integrated in to one product.

Now that 11.2 is available, I would like to know:

If we can use the same command line to install new version 11.2 over version 11.1 using the following command line.

(We use SCCM)

msiexec /i DWMRC11x_64.MSI /qn APPDIR="C:\Program Files\DameWare Mini Remote Control\" reboot=reallysuppress SILENT=yes INSTALLSTANDALONE=0 CENTRALSERVERHOSTNAME=LICENCESERVER SA_EMAIL=some@email.com

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!

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

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

I’m happy to announce that DameWare 12.1 is now publicly available.

This release brings several improvements, namely:

• New Mirror Driver -  Customers connecting to Windows^® 10 can now use the brand-new mirror driver. Additionally, DameWare 12.1 now supports 4K monitor resolution and adds support for Java^® and DirectX^® Apps, allowing you to interact with high resolution displays and modern apps.
• TLS1.2 support - which can help ensure the safe transfer of real-time data. TLS 1.2 adheres to PCI and HIPAA industry requirements.
• Refreshed UI -  New, refreshed icons for DameWare Remote Support and Mini Remote Control update the look and feel of both DameWare products.

DameWare 12.1 is available for download on your customer portal for those customers under current maintenance.

If you are not a DameWare user yet, now go anddownload new version from www.dameware.com now!

This is starting to become a regular occurrence with our team when trying to provide remote support using Dameware.  This is happening when connecting to Windows 10 Pro computers in an enterprise environment.  Sometimes it is fixed by having the end user reboot their computers and then we can connect with no problem.

I've seen a couple of threads here with the same issue but there doesn't seem to be a solid solution listed in those threads.  Our settings in windows allow remote connections.

Get Windows Lock Screen when I remote to a machine

Desktop goes to lock screen when I remote in and try to do anything

Thanks for any help or direction to resolve.

Afternoon Everyone.

My name is Marvin. I'm a recently new IT Associate at a small company that utilizes DRS to remotely manage assets. I've noticed the some assets when connected to with Mini Remote Control have a frameless, resizeable window with the undocked toolbar at the top. I was hoping there was a way to disable this as a setting, and leave the remote session in the framed, locked window of DameWare Mini Remote. I would prefer to be able to minimize the remote session if needed, or quickly move it from another monitor over.

This does not happen on every machine. If I'm able to capture a screenshot later, I will add this visual later.

Thanks!

Marvin

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

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

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

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

Hello Jodi,

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

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

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

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

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

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

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

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

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

Bryan,

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

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

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

Thanks for your help.

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

Hi Jodi,

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

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

I hope this helps.

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

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

Hi again Jodi,

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

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

that should do it…

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

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

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

Thanks Bryan and Zac T,

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

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

Hi Jodi,

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

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

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

Bryan wrote:Hello Jodi,

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

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

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

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

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

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

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

though that i know a lot.thanks

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

Tabs in DameWare MRC.
by gpribeg on Wed Oct 17, 2007 5:25 am

Putting tabs in DameWara MRC.

Making remote controled computer in each tab in one main window.

Re: Tabs in DameWare MRC.
by Roger on Mon Oct 29, 2007 1:55 pm

Although with all the various screen sizes and such I end up with, I'm not sure what that would look like unless each tab could change the whole window size.

Re: Tabs in DameWare MRC.
by Marc on Fri Feb 22, 2008 1:24 pm

I wanted to bump this topic. I was working on several servers last night and I counted 9 open, active MRC windows. I'd love to see a single, tabbed window; similar to VMware's appearance.

Re: Tabs in DameWare MRC.
by cblackburn on Tue Jun 24, 2008 8:18 am

Roger wrote::thumbs: Although with all the various screen sizes and such I end up with, I'm not sure what that would look like unless each tab could change the whole window size.

Bump!

The VMware clients handle multiple connections of various resolutions from one console just fine. I pray DW will include this in an upcoming release. I'm sure It'd require a lot of coding/testing on their part, so I have no problems waiting.

Re: Tabs in DameWare MRC.
by Kezzran on Tue Dec 30, 2008 9:57 am

I'm curious if there has been any movement on adding this aspect (tabs) to DameWare, so that all sessions can be controlled using one window? This is probably the only feature I'd really like to see in this excellent product. 

Thanks,
Kezzran

Re: Tabs in DameWare MRC.
by Jezarith on Thu Mar 05, 2009 9:29 am

bump..

I'd like this as well.

Re: Tabs in DameWare MRC.
by schnax on Thu Feb 03, 2011 11:43 am

bump..

I'd like this as well.

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

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

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.

Hey guys,

I'm trying out Dameware as a replacement for Logmein, but it seem to only work locally, with users within the organisation firewall. If a user is outside, he can connect to the DameWare Internet Proxy URL, download the agent, but the Mini Remote Control can't connect with the agent.

In this scenario, the central server is standalone (1 machine) configured using port 11443 (Take note that i tried 443 with same result), the corporate firewall is redirecting this port to the central server and the Mini remote control is on the same subnet as the central server (no firewall). SRV01, a test machine is located outside the corporate firewall. It can connect via the URL to the DameWare Internet proxy URL and installed the agent. It shows as online in the Remote Host.

Steps :

1 - MRC start an internet session

2 - SRV02 manually enter the URL in FireFox

3 - DameWare open, then it show that the session is not avaiable. (The session shown in the administration console status)

My Internet proxy config