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:

• Over the Internet (OTI) unattended sessions for Dameware Centralized users
  • Allows you to remotely support users on the move, and assist remotely without the presence of the end user
  • Deploy agents with OTI unattended support to end-points
  • Manage agents for OTI unattended sessions to maintain high security and control
• Search Hosts in Mini Remote Control
• Support for Windows 10
• Ability to switch between the Standalone and Centralized versions without reinstallation
• And many other improvements and bug fixes

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!

All,

I did a fresh install of Windows 8.1 and tried to install DW9. The installation goes all the way through until it seems to start modifying registry keys. It throws an error that "There is a problem with the Windows installer package. A program required for this install to complete could not be run."

I've installed every vc++ redistributable known 2005,2008,2010,2012, and I've installed .net 2, 3.0, 3.5, and 4.0 - 3 - 4.5 is installed via Programs and Features. I've also installed various versions of DirectX just to see if it had something to do with that and no-go. I've got full admin rights on this box, and another person that I work with is having the same problem. The users that upgraded from Windows 8.0 to 8.1 are not having an issue, so it looks like Windows 8.0 may have something that 8.1 doesn't have? What in the world is it??

I believe we have 32-bit, but I'm not sure if there's a separate 64-bit version. The 32-bit has installed on every 64-bit OS in the office except this one.

Any ideas for me to look at? Error logs don't show me anything. It doesn't even show the application that it's 'required' to run and cannot find/launch:

Action start 12:19:36: InstallFinalize.

MSI (s) (BC:9C) [12:19:36:766]: Note: 1: 2265 2:  3: -2147287035

MSI (s) (BC:9C) [12:19:36:767]: User policy value 'DisableRollback' is 0

MSI (s) (BC:9C) [12:19:36:767]: Machine policy value 'DisableRollback' is 0

MSI (s) (BC:9C) [12:19:36:777]: Note: 1: 2265 2:  3: -2147287035

MSI (s) (BC:9C) [12:19:36:783]: Note: 1: 1721 2: APPDIR 3: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 9.0\ 4: ""     <---- The 4: is the command that was ran and it's blank

Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: APPDIR, location: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 9.0\, command: ""

MSI (s) (BC:9C) [12:19:38:105]: Product: DameWare Remote Support 9.0 -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: APPDIR, location: C:\Program Files (x86)\SolarWinds\DameWare Remote Support 9.0\, command: ""

Thank you!!

Need help with host list conversion mrc.dbf (v6.9) to mrccv2.db (v10)

My mrccv2.db is always blank. I have tried deleting and the conversion dialog appears for a moment, but the end result is always a blank host list.

This issue started about a month ago with a group of machines. There is no apparent link to these machines which did not have the issue prior. I have read many forums and discussions relating to a firewall issue, but there is no firewall turned on internally. There are other machines on the same switches which work without issues, as well as other states and building which have no issues. We have tried to uninstall the software and service, remove all related folders,  and reinstall everything fresh with the same issue following.

When we encounter this issue on a machine, we use the remove service feature in Dameware, then close the application and open again and try to connect. We are then prompted to reinstall the service, which will then allow us to connect, and will continue working correctly until the machine is restarted. This does not fix the problem, and each time we must do the same steps to connect to the problem machines.

The service is currently set to automatic on all machines. When we tried to set it to manual, we could connect but would have to install or start the service first, which does not work well. When we set it to delayed start, we are able to connect after 2 few minutes after reboot. we have also tried to register the service again and it did not help.

When looking in the event logs for the problem machines, the following data shows in the failure entry.

"

Error:

DameWare Mini Remote Control

No Link-Local or Site-Local Cloud Available (Local).

System Error: 10091

System Message: WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.

(srv 64 bit)

"

Any help on why this is happening or what could be the cause would be greatly appreciated.

I had a Dameware batch file I used to remote into computers. I have updated dameware and now my batch file no longer works. I did change the the path so the path is correct. When I run this, I get an error saying Authentication Failed Remote Message: System Error: 87 The parameter is incorrect.

I use this because I have a Local Admin account on all computers on our Network, but I wasn't able to Remote into the machines when I was logged in with my Domain user account. So I ran this batch file, and entered my local admin username, and it would ask me for a password, and then it would conect.

Can someone tell me what I need to do?

Here is the Batch File:

@echo Dameware Login
@Echo --------------
@Echo Off

Set /p PC="Connect To:"

set /p inputone="Username:"
C:\Windows\System32\runas.exe /user:%inputone% "C:\Program Files\SolarWinds\DameWare Mini Remote Control 11.0 x64\DWRCC.exe -c -h -a:2 -m:"%PC%

Thanks for your help!

I have a server  Windows server 2008 that I use to be able to conect to via Dameware. However now when I try I get an error that says

Unable to install the Client Agent. The following file is missing:

.

System Error: 2

System Message

the System cannot find the file specified

I can manually install the service and then I can connect, but it is my companies policy that we have to remove the service on disconnect. After I disconnect, and try connecting again I get the same error message.

Can someone please hlep me with this?

Thanks!

I have installed Dameware Centralized Server RC12. It works great! But it created a certifikat that is a problem. I installed DCS RC12 on our main server, which is a  Windows Small Business server 2011 Standard.

Now every time one in the company opens there Outlook, a certifikat warning pops up. It says that the company that made this certifikat is not trusted, but the date is valid.

I know that under the installing of DCS, i was promptet about it creating a certifikat, but did not think it could be a problem.

I changed my default port on all the clients from the standard 6129 to another port. However, the MRC control app defaults to the standard. I can change this in the settings for each pc I connect to but I can't find a way to globally change the port it tries to connect over first. Is there a way to do this?

I currently use Dameware MRC version 9. I need to allow a specific domain user to remotely control several specific workstations. I thought this would be an easy task, and maybe it is, but I cannot seem to figure out which buttons to click. Can someone tell me how to set this up step-by-step? Also, I need to retain the ability to connect as an administrator.

More information:

• Windows 2008 domain
• Workstations are all Windows 7 Pro
• All connections are internal, so no firewall or gateway is in the mix
• User is a member of the domain group Authenticated Users

FYI, I attached a screenshot of a message I received when I tried to connect to the remote computer using the non-admin domain user. I think I am close.

When I run the DameWareMRC32-St-v11.1.exe or DameWareMRC64-St-v11.1.exe,  It appears to "unpack the binaries" then just quits.

I had it installed and working before the holidays.When I returned I ran a PC cleaner. Afterwards, Dameware claimed that the licence had expired. I uninstalled the software at the request of IT and attempted to re-install with the results above. Any Ideas??

The PC cleaner may or may not have had any influence in the situation. I did not run DWMRCS before the cleaner. So, I don't know if it worked directly before. I mention it only to provide a clear picture of the situation.

Mark A Conway

Director - Applied Technology

Gilmore & Associates 

When Windows Firewall is enabled stealth mode is enabled by default and there is no supported method to turn this off.

Is there any way to fix this problem on the client side without installing dameware on every single computer.

So what happens is you connect to a computer with dameware the connection spends several very noticable seconds before it promts you to install the client. This is because it seems to assume the client is always installed. And this is why stealth mode causes a problem.

Is there any way for the dameware client to do a check for the client service first and then connect or install the client?

Is this problem solved in any of the recent versions of the software? I belive we are a few versions behind.

I'm having an issue where Symantec data loss prevention is keeping dameware mini remote from loading. I attempt to connect I get the negotiations on the task bar but the screen goes white or freezes at initializing. 

We have recently started using Dameware and Mini Remote.  When I use  Mini Remote to connect to a users pc I'm finding that it changes their desktop display settings. These changes are tied to mini remote because they were reported within a minute of me connecting to their pc for the first time.  And, it was reported by users in the order in which I connected to their pc's.   One right after the other.   I'm aware of two specific changes:   the color scheme changes (minor in the big picture but it's the little things that keep them happy), the task bar for example was a deep blue now it's a muted gray color.    The biggest complaint is that the windows preview when you mouse over an application icon in the task bar changes from window previews to a list.   Previously, if you had multiple word documents open and had it set to not combined icons it would show one Word icon in the task bar.  If you would mouse over the Word icon it would pop up little windows for each document you had open and as you mouse over each window preview it would temporarily display that document maximized on the screen.  Now, it only pops up a list, that's in, no interactive preview or anything.

With my previous employer I used mini remote extensively and did not see this happen.  Please help, my name is mud with several users because of this.

Your insight and expertise is appreciated.

Joatta Sayles

Hello, hoping I can explain our issue and get some assistance, my brain is currently fried.

Having an issue with a Dameware v9 on our domain. Currently the Helpdesk users (3 users) have no problems connecting to what we call Host computers.. but they are admins of those boxes (32 bit XP)

Currently we are expanding the ability of remote support to Directors and Regional folks (~20 users), all have the same v9 client installed as the Helpdesk users, but are NOT admins of the Host computers. Previously (and currently) these users were using PCAnywhere to connect to the Host machines, but with the addition of Windows 7, we have decided to not move forward with that and use Dameware exclusively.

To facilitate this and control who can connect to what, an administrator built an MSI package that included AD security group that had job titles for the directors and regional folks nested in it. All was good, so we rolled out the package via SCCM to all the XP host computers, and no one could connect to the XP hosts, not even the Helpdesk folks it would give an error message " Lost Connection. Would you like to try to reconnect? Lost connection to computer XXXXXXXX, System Error 10054 System Message: An existing connection was forcibly closed by the remote host." To fix this so the Helpdesk folks could get in, I used RDP to get into the computers to re-install the MSI package and now the Helpdesk can get in. But no one else can (presumably because they cannot start the service that is supposed to be started... but is supposed to be started) Soooo......

The Hosts still have the PCAnywhere software listener installed and Directors still have the full PCAnywhere install installed (as they need working remote support for XP boxes) . So we troubleshot, 2 worked after a installation by hand for a director, the rest didn't. The administrator and I worked with various folks today and learned a few things.. 1) most times the Dameware service is set to start automatically, however will not start. So logically, you start the service manually.. when you attempt to connect to the computer, the service stops. Re-installation does nothing. Administrator attempted to create another package and was left with an install that would hang on almost 100%... and never finish until you killed the process it was running, then it would say finished.. but it clearly was not finished, 

So yeah.. today was a long day, lol. The funny thing is, the Directors and such have the same access to our Windows 7 Host machines, and have zero issues. A similar package was made for them.. same security, etc. Works like a champ.

I'm confused!!

Hello Everybody

I have a Problem starting the Mini Remote Control on Windows 7 64 Bit.

Description:

Installed Newest version (mrc 9.0.1)

Start MRC -> Seeing hourglass -> nothing happens hourglass disapears , i can see the process (DWRCC.exe) running.

I can wait now for hours and nothing will start but whe i hibernate the computer in this state the Gui is started as soon as i turn it on again.

Things I tried:

Installed latest version 64 bit / 32 bit, restarted computer several times.

Ive also tried running it with antivirus disabled.

Ive found a support page entry which looked very promising:

http://support.dameware.com/kb/article.aspx?ID=400132

A nice Sales member from solarwind pointed me to this link for download:

http://downloads.solarwinds.com/solarwinds/Release/HotFix/DWMRC-v9.0.1-HotFix2-CAC.zip

But unfortunately it fixes nothing.

It seems not to be releated to the os because my collegue (same os) can start it immediately.

Another collegue has the same problem.

I dont find any logs to provide, but if you could point me in the right direction i could post them here.

Kind Regards and Thanks in Advance

Lukas Fenner

WHen I try to install DameWare Mini Remote Control 9.0, I get  "there is a problem with this windows installer package. A program run as part of teh setup did not finish as expected." I checked teh app log and get :

Product: DameWare Mini Remote Control 9.0 -- Error 1722. 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.  Action APPDIR, location: C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\, command: "C:\Program Files\SolarWinds\DameWare Mini Remote Control 9.0\SolarWinds.MRC.Licensor.exe"

The description for Event ID 0 from source Installer Registerer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ErrorReference:IECookie Error:ErrorCode:12

I tried loading version 10 qand get the same thing.  Any ideas?

Good Morning,

I have been using DameWare MRC for quite some years now and all of a sudden I get the following error:

Winsock Connect Error:

System 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.

I believe there were settings changed in the group policy that does not allow a client to respond to the remote calls because it stopped working from 1 day to the next.

Still the same OS Windows 7.

I do not have any problems at all to install/uninstall the service via network on the client computers thru the MRC.

Using it on my servers it works perfectly.

Since my domain administrators are glueless what change they could have done with the group policy to prevent the clients from responding and I do not know either I would like to find out thru this route if anyone is outthere that would have idea which setting needs to be switched on the client computers.

Thank you for your time and possible assistance.

Regards.

          Hoagie

Hello NG,

I come from this site http://forums.dameware.com/viewtopic.php?f=17&t=3065 , which resulted in opening a support case.

Our systems experience lots of the following error entries in Windows event viewer, application log:

##################################################################
Error:
DameWare Mini Remote Control
No Link-Local or Site-Local Cloud Available (Local).

System Error: 0
System Message: Der Vorgang wurde erfolgreich beendet.

(srv 64 bit)
##################################################################

We want to get rid of the messages. Can you help?

Our Dameware version is 7.5.9.0, we run Windows 7 64bit Ultimate SP1 fully patched. Our systems have IPv6 disabled in properties of the NIC configurations.

Thanks in advance!

Best Regards,

Bob

I have one user machine (windows 7 64 bit) that only gives me a black screen when I connect. MRC works fine with the xp machines on the network. Is there some setting I need to change?

or am I missing something else?  Thanks

I know the "floating" DameWare MRC control toolbar which exists once you're connected to a remote host can be moved around or dismissed with the X, however I do not always remember how to get it back.

Is there a setting such that it can auto-hide to an edge or corner of the controlling machine's screen until the mouse goes to that edge or corner, similar to the way the Windoze taskbar or OSX dock can hide until the mouse goes to the edge of the taskbar's or dock's edge of the screen where the taskbar/dock  then reveals itself?

If it doesn't exist, make it exist!