netoide

DameWare working in next generation systems! Awesome! I hope we see many people participating.

Congratulations jimmyyen! Seeing is believing, as they say!

I'm glad somebody brought this up. This is a VERY relevant point which (probably due to lack of knowledge) the press hasn't discussed much.

Yes! All the user need is to have permissions for remote control instead of "View Only". If you right click the DMRC Client Agent icon in the tray and look for "Who is Connected..." you can find see if the user connected has permissions for control. Also, you don't have to have DRS for this feature. If you only have a DMRC…

OK, I'm inclined to think the issue is in VMWare Player . Shut down the VM working and look for the .vmx configuration file. Open it with notepad and add the following line: keyboard.typematicMinDelay = "2000000" This delay is set to microseconds so 2 000 000 would be 2 seconds, which should be more then enough. Save the…

rob.hock is correct, Server 2012 isn't supported yet. However, we have been able to make it work and face similar situation. Here is what you can do: - Uninstall the MRC Mirror Driver from the server's Device Manager - Remove the MRC Client Agent - Create a custom MSI installer for the MRC Client Agent using the DameWare…

Try changing the VNC settings in DameWare Mini Remote Control (blue wrench icon). Test if reducing the color depth and limiting the bandwidth helps. I suggest using 16bit and using 128 kbit/s bandwidth:

I looks like you may be missing .NET Framework on that machine. If you have it but are using 4.0 or higher I suggest you try installing 3.5 SP1. Here's a link to the MS download site: http://www.microsoft.com/en-us/download/details.aspx?id=22

Hello ccoho! Have you tried modifying the following registry key: HKEY_CURRENT_USER\Software\DameWare Development\Mini Remote Control\Settings\MRC db Path Modifying that value allows me to have the saved host list database in a network location. I haven't tested it with multiple users, though.

Error 1726 could indicate something is blocking the LDAP call used by DRS to connect to the DC. Could there be a firewall between your workstation and the server in the remote site? I would suggest that you check for anything blocking TCP port 389 (or 636 if you are using an SSL Tunnel).

The SolarWinds LicenseManager doesn't currently have any switched or arguments that you may include using the command line. If I am not mistaken the current licensing system requires that this application connects to the SolarWinds Licensing Server and removes the unique computer identifier from the list of active…

For me, using the "File" menu options to remove and install the service has worked the best. Just keep in mind that DameWare Mini Remote Control uses pass-through authentication during this process. The user you are running the application with must have the necessary permission in the remote system for this to work.

To me it appears that there is still some credentials left from domain2 on the computers (or even of domain1 since there was a trust). locally on those computers, look for the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList Here, you will have sub-keys for each user…

OK, so I reproduced your environment and it is working fine for me. Can you check if you have the DameWare Keyboard driver installed in the computer you are connected to in the first session. You can find that in the Device Manager under keyboards: I think that without that driver the second session may register each…

Where are the characters repeating? In the first or the second session? If it is the second, I suggest you select "Lock Remote Keyboard and Mouse" in the first session.

What you can do is set a GPO that applies a .reg file with the following registry key: HKEY_CURRENT_USER\Software\DameWare Development\Mini Remote Control\Settings Keep in mind however that each installation has to manually register to Solarwinds to activate the license. If you are not confident with the staff you should…

I suggest you try using MSG command, which replaced "net send" after Windows XP. Check the following article for details: Terminal Server Commands: MSG