Dear sirs,
We are evaluating MRC, establishing a session to a client-computer, then establishing a session from that computer to a second computer causes characters typed to be repeated, it is very difficult to get typed text right since the backspace is often repeated too.
What can be done to solve this problem?
Additional data:
First session: MRC 9.01.247 64-bit
Second session: MRC 7.5.9.0 32-bit
Good Afternoon,
I recently tried installing the Dameware Mini Remote driver onto a Windows Server 2012 machine and it continues to report back "The Operating System has reported that a reboot of the remote machine is required to complete the Mirror Driver installation/update". Once you click ok, it lets you in. But, everytime you remote in with Dameware, it pops up this message. The system has been rebooted multiple times and tried installing the driver multiple ways with no success. How do I get around this? Thanks
We use DMRC 10. We have some non PC admins that need to use DMRC to help users.
Currently checked:
Permission required for these account types
Disconnect if at the Logon Desktop
View Only for these account types
Is there a registry setting we can push via Group Policy to change these settings on an OU?
Or I can add them to a global group, but then I'd need to add the global group to 'Must be member of one of the following groups' and check the box.
Any help would be appreciated.
Thanks!
Tim
Any thoughts on how to make this work?
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
I use Dameware Mini Remote Control to remote into my servers from home. My home PC is WIN 7. I have the free upgrade to Win 10 but do not want to install until I verify DMRC will be compatible with the new OS. I have version 11.1 64bit
We've updated the DameWare support page. This serves as a one-stop shop for all your DameWare documentation, how-to's, troubleshooting, and more. You can add the page to your "links" or bookmark the page so you'll always have it handy.
Hope this helps, as always!
Danielle!
Good Afternoon,
I recently tried installing the Dameware Mini Remote driver onto a Windows Server 2012 machine and it continues to report back "The Operating System has reported that a reboot of the remote machine is required to complete the Mirror Driver installation/update". Once you click ok, it lets you in. But, everytime you remote in with Dameware, it pops up this message. The system has been rebooted multiple times and tried installing the driver multiple ways with no success. How do I get around this? Thanks
I am trying to figure out what the authentication requirements are to use dameware across multiple domains.
I am in Domain1.com and I need to be able to support Domain2.com, but I have to create an account in Domain2.com to be able to support these users.
I want to be able to use my Domain1.com account to manage all users in Domain2.com. I have made my account part of Domain2.com 's built in administrators group but still no luck.
Help please!
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
There's a lots of communication on 49155 port, but I cant guess what is he doing. I cant find started mrc service on machines that he is communicating with. So what is he doing. Is it possible that he is spying that users. Like I said, there is tons of packets on 49155 tcp port.
Windows default is to only show notifications from applications in the system tray. We wish to have the MRC icon always visible, so users can right-click on it and connect to the console of the helpdesk member talking to them. Many times it's easier than trying to figure out their computer's name or IP.
There's a setting (and a GPO) to show all the icons of the system tray, but there's too many useless icons to show them all. It get worst when a user hooks up their laptop to a projector; with the small resolution of the display (most projectors resolution is 1024x768) and the "show all icons" settings enabled, there's hardly enough space in the task bar for two or three applications at the same time.
Users can customize which icons are to be always displayed, but is there a way to automate the process for all users?
Since version 10, the message "Maintenance expires in xx days" appear every time that we launch the software and stay in orange at the top of the main window.
Is there any way to deactivate definitively this as the maintenance is not mandatory with the product ?
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?
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
We're running DW ver 12 with Agent ver 9.
Version 6 of Dameware had an option to install mini without prompting me every single time. I can't find that option on tDW 12 with Mini ver 9. Is there a way to do this?
Sometime when connecting to high resolution clients, my dameware mrc does not let me move the window on my screen. I am connected to two clients right now for example. One is at 1024x768. The dameware "window" has a menu bar (File, Send, Monitor...) and buttons, and the display of this remote machine is integrated within this window. I can minimize, maximize, close or drag this window around no problem.
The other machine I am connected to is 1920x1080. The view of this remote machine is separated from the dameware toolbar in the top middle of my screen. The window border around the view of the remote machine is so thin that there is nothing to grab ahold of to move this window around my screens. I can only really awkwardly resize it to move it to another monitor or another place on my screen. How could I get the view of this remote machine attached with the menu bar and tool bar, like the other machine? There's no way to disconnect either. Well one would have to close it from the taskbar. If you click the little X in the top anchored, centered toolbar that is detached from the remote PC view, that toolbar goes away permanently . unless you close dameware and reopen it.
I am using MRC 9.0
I'm getting this error when trying to dial into one specific site. All the computers at this site give me the same error. I can succesfully log into all of our other sites using Dameware with Windows NT challenge response. I have confirmed that there are other users who are having this problem as well, however strangely some users can still access this site with Dameware and Windows NT challenge response no problem. I found a post on your old forums recommending adding a few lines of code into the INI file, but that must have been for an older version of Dameware that still used one, I think it all goes into the registry now. Has anyone had this issue before? If you need any more info please let me know.
Any help is appreciated!
I'm unable to launch my DMRC console, I can't get past the login. I get an "Internal server error." message. However, I'm able to get into the Dameware Server Administration Console without a hitch.
I've restarted the Dameware Server service and the whole server and it changed nothing, except the first time I tried to log in I got "SOAP parsing error occured. It might be due to incompatible versions of the Server and Console." as the error message and Internal server error afterwards.
Here's the service log entry that appears on each unsuccessful login (server host is in french, so some messages are translated):
2014-09-11 09:09:03,535 [19] ERROR DameWare.Server.Executive.SettingsCache - SettingsCache.GetSetting could not retrieve Setting with name 'CentralServer_TcpServerIpAddress'. Error: La clé donnée était absente du dictionnaire., StackTrace: à System.Collections.Generic.Dictionary`2.get_Item(TKey key) à DameWare.Server.Executive.SettingsCache.GetSetting(String settingName) 2014-09-11 09:09:03,535 [19] ERROR DameWare.Server.RoleCentralServer.Executive.ExecutiveSubSystems - CentralServer.Authenticate service - Unexpected error occured. Error: La clé donnée était absente du dictionnaire., StackTrace: à System.Collections.Generic.Dictionary`2.get_Item(TKey key) à DameWare.Server.Executive.SettingsCache.GetSetting(String settingName) à DameWare.Server.RoleCentralServer.Services.Implementation.CentralServer..ctor(ISettingsCache settingsCache, ISWLogger logger) à DameWare.Server.RoleCentralServer.Services.Implementation.CentralServiceManager.<ConfigureServiceHost>b__1() à DameWare.Server.Common.WcfServiceHelpers.CustomWcfServiceInstanceProvider.GetInstance(InstanceContext instanceContext, Message message) à System.ServiceModel.Dispatcher.InstanceBehavior.GetInstance(InstanceContext instanceContext, Message request) à System.ServiceModel.InstanceContext.GetServiceInstance(Message message) à System.ServiceModel.Dispatcher.InstanceBehavior.EnsureServiceInstance(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) à System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc) à System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
Some translation:
Error: La clé donnée était absente du dictionnaire. = Given key was missing from the dictionnary
I’m thrilled to announce that Dameware 12.0 is now publicly available. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. Technicians can now support end-user in company network as well as in Internet anytime.
This release brings several bigger and smaller improvements, so let me highlight a few of them:
Dameware 12.0 is available for download on your customer portal for those customers under current maintenance.
If you are not a Dameware user yet, now go and download new version from www.dameware.com now!