Is there a planned update for the mirror driver included with the v12.0.3.0 DameWare Mini Remote Control Service. Not only does it no display correctly in Windows 10 Device Manager, the driver date is over 8 years old. There is also some concern that it is causing issues with displaylink connected displays using HumanScale USB 3.0 docking stations.
Mirror Driver in DameWare Mini Remote Control is outdated
CTRL-ALT-DELETE doesn't work when I'm attached to a client's machine
When I'm using Dameware V10 to remote into a client's machine, it always starts with the following message "Configuring the remote system for first time use. This may take as much as two minutes. Please wait..." It allows me to get to the client's machine but then the CTRL-ALT-DELETE function doesn't work and I can't log in. I've also tried to use the Send "CTRL+ALT+DELETE" option. I've installed and re-installed the Dameware Software at least 3 times but it still has the same issue. What would be causing this problem? Thanks.
Dameware v9 and Citrix
We use Dameware v9 on aCitrix Silo server. The licensing information will not stay in the product. Users have to enter the info every time. Any way around that?
Locking Advanced Screen
Hi,
I was wondering if it was possible to lock the Advanced Screen settings with the Server IP/Hostname so the users wont get a chance to make changes to this.
We are using Dameware Mini Remote Control v11.2.0.91.
DameWare v12.0 HotFix 1
Please note we have released Hotfix 1 for Dameware version 12.0. This hotfix is available on your customer portal.
Hotfix 1 addresses the following issues:
- ZDI-CAN-3125 vulnerability (Thanks to Andrea Micalizzi aka rgod, working with HP's Zero Day Initiative, for identifying this issue.)
- Upgrading MRC agents on remote machine failed.
- MRC was not able to connect to remote machine using "MRC Ping" feature.
- DRS Service installation failed in DRS.
- Event log does not show content in DRS.
Hotfix 1 requires SolarWinds DameWare Mini Remote Control version 12.0.0.509. Hotfix 1 can be applied to both 32-bit and 64-bit installations or SolarWinds DameWare Remote Support version 12.0.0.509.
You can find more details in README file included in hotfix.
Now go and download the hotfix now.
Dameware Mini remote Control - Removing Autostart
OK .. I think I am missing something simple in XP but I have been unable to find the auto start for Mimi Remote Control. We installed the new version 12 on my laptop and apparently selected the startup folder as part of the install. It is working as expected in that Mini Remote Control starts every time the laptop boots but I now have somany other things starting that it takes like 5 minutes to boot. I looked in both my startup folder and the all users startup folder but I did not see anything there. I also dod not see anything in the program settings to enable / disable this. Am I just looking in the wrong place or just not seeing it.
Brent
Dameware to Direct access client over ipv6
Any thoughts on how to make this work?
Auto open in fullscreen (NOT JUST MAXIMIZED)
Does anyone know how to create a shortcut to open to a host into fullscreen?
i.e "C:\Program Files\DameWare Development\DameWare Mini Remote Control 7.5\DWRCC.exe" -c: -md: -x: -m:xxxxxxx (WHAT ELSE)
Im making a computer that auto boots, and logs into multiple virtual machines and displays them on seperate monitors. I've got everything except for figuring out how to make dameware open fullscreen. I can't find any options or anything. The closest I can get is having the screen maximized
Is there an update to virtual keyboard emulation driver dwvkbd64.sys?
Hi,
Were tracking down some random BSOD's that occurred after rolling out Microsoft Lync 2013 client. It's a BAD_POOL_HEADER (19) error in w32k.sys called from csrss.exe.
One of the similarities when looking at crash dumps with other people with the same problem is a driver dwvkbd64.sys, dated April 11 2007. THats a few years old, so just wondering if this could possibly be the cause of the BSOD's. I'm looking for a driver update for this file that is higher than version 1.0.0.1 and newer than 2007. Is there one? I just pushed version 10 to my laptop to check, but went into devmgmt.msc and it still shows the 2007 era driver.
Here's a thread where another person at answers.microsoft.com suggested to check into this file:
You'll see on there a a link to my skydrive public that has two crash dumps if you want to look and see if Dameware is the cause.
Thank you.
Dameware v9 Mouse Movement on Window Focus.
I'm using Dameware MRC v9 on Windows 7 remoting to other Vista/Windows7 Computers. My issue is that if I connect, minimize the window, then later click on it in the task bar, the remote client's mouse moves toward the bottom of their screen nearest to where my mouse pointer is. It does this even though my mouse pointer is outside of the Dameware Window. So while I'm doing remote support on an issue if I click on another window or minimize that dameware session, then later go back to it....it moves their mouse around. Which has become quite anoying. Usually my mouse is below the Dareware window and it moves their mouse to their taskbar or clock popping up a preview window or tray icon description or who knows what. Then they have to move their mouse back again.
While the Dareware window continues to have focus I can move my mouse around outside of the dameware window and it doesn't effect the remote client's mouse. It seems to be only when the Dameware MRC window gets focus again after losing it. Whether it gains focus back from an Alt+Tab, Windows+Tab, or a Click to that window from the taskbar it does this....and...its....driving...me...crazy.... :-)
Any other Remote Control software I have used does not move the Client's mouse unless my mouse goes within the border of their screen within the application.
Does anyone else have this issue? Anything I can do about it?
DameWare MRC v6.1 does no longer work on client computers
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
Why does Dameware MRC v9.0.1 get stuck at the initializing desktop screen when trying to connect to certain computers? Even after uninstalling the service and reinstalling the issue continues, there is no firewall turned on for the machines with this issu
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.
Dameware NT utilities blocked by firewall ?
Hi there,
When I want to remotely install Dameware NT utilities (version 7.5.9.1) on a PC running Windows7 or server running Windows2008 and the windows firewall,is active, it just won't work.
I don't even 'see' the machine in the left hand pane of the interafe.
Note : I can't ping the machine either.
As soon as I switch of Windows' firewall everything works fine (ping=OK, install=OK) , but this is not the initial setting of the firewall.
Same goes when Dameware is already installed but Windows firewall was activated afterwards for some reason : no Dameware, no ping.
What rules or ports do I need to create or open to be able to install Dameware without switching off the firewall ?
Thx.
Bart
Dameware V7.5.6.1 and Windows 8.1
I am having issues with Dameware not connecting to our new Windows 8.1 hardware. Can someone tell me if there is a compatibility issue with the version we are using and Windows 8.1
We are running Dameware V7.5.6.1
When or if I do get it to connect it typically drops the connection after a few minutes and then I have a bugger of a time getting it reconnected again.
The other thing I see when it does finally allow me to connect is a message about having to restart the system. It never does, but does allow me to finally get connected to the hardware.
We are running Windows 8.1 on DELL Venue Pro tablets and Acer Aspire E 15 laptops.
CTRL-ALT-DELETE doesn't work when I'm attached to a client's machine
When I'm using Dameware V10 to remote into a client's machine, it always starts with the following message "Configuring the remote system for first time use. This may take as much as two minutes. Please wait..." It allows me to get to the client's machine but then the CTRL-ALT-DELETE function doesn't work and I can't log in. I've also tried to use the Send "CTRL+ALT+DELETE" option. I've installed and re-installed the Dameware Software at least 3 times but it still has the same issue. What would be causing this problem? Thanks.
Dameware Centralized Server - Useless?
Hi all,
i am sorry but i have to say i really expected more from Dameware Centralized Server. I installed the Centralized Server today (no proxy, no gateway), but this tool is just useless in my opinion.
Installation was easy yes, but after an hour i have to say: It is only usefull for centralized license management, thats all! If you have just a few licenses, dont waste your time and manage them manually.
Things i am really missing (and i think i am not alone requesting such features)
- only AD User Import, no real AD integration. Hence you have to manage your users manually.
- no Rights Managment - only admin or no admin
- no centralized config management
- no autologin with DRMC or DRMS
Global host list:
- No rights management (user only should have access to a few hosts / folders)
- no centralized and advanced settings for hosts entries (only connect with RDP to a specific host) settings will be ignored if you connect via DRMC
- its just a list of your favourites, not more not less.
Is there a wishlist for product improvement? When is the next update planned?
Thanks
Peter
Dameware Command Line Issues
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!
DameWare Mini Remote Control - Connect Authenitcation failed:
Dameware v12 on Server 2012 attempting to connect to a Win7 64bit which I've unistalled and reinstalled latest client agent.
Tried connecting via Active Directory, Microsoft Windows Network and by IP address all 3 fail with this message.
"DameWare Mini Remote Control - Connect
Authenitcation failed:
Remote Message: System Error: -2146893048
System Message:
The token supplied to the function is invalid
Please check the event log on the remote machine for a possible cause"
Has anyone had this issue and solved it?
All help, hints and advise gratefully received as I can't get to the remote machine to check for a possible cause.
Thanks in advance
DWMRC Connect from commandline to Remote Host
We have DWMRC install in central admin mode and see there is a dwrcc://<hostname> command you can use to quick launch a host, but it only works with the WebHelpdesk module or can this be used to integrate with any helpdesk? Also is there any way to use the Command Line Functionality to connect to a host that is listed under the Remote Host List? if I try to specify a host it just bombs out that it can't connect
dwrcc.exe -m:somehost -bh:central-server01 -bpn:6133 -bu:mycentralid -bps:mycentralpassword
It appears it's just trying to connect to the host not the host that's listed under the Remote Host List via the Central Server.
Thanks in Advance!
How to add Monitor 2 to toolbar
Running mini remote control 9, when customizing the toolbar there is an option to add a button for Montior 1... but not for any other monitors... Is there a way to get a Monitor 2 on the toolbar? We have a lot of users with multiple monitors, and yes there is the monitor drop down menu but having them on the toolbar would save some hassle and since Monitor 1 is an option I feel like maybe I'm missing something and there IS a way to get monitor 2 on there.
Thanks!