Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We find that on our new servers VNC runs very slow and the screen does not update correctly

When I connect to or disconnect from servers using MSTSC, it sometimes causes our running app to abort with an exception somewhere in the .NET code. Also, it's annoying to have to login to the box each time.

Can anyone recommend a decent remote admin solution which does not max out the CPU, or make your apps unstable?

share|improve this question

closed as too localized by Skyhawk, Mark Henderson Dec 1 '11 at 4:15

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Just a minor point but isn't MSTCS using RDP not VNC as the protocol? – 3dinfluence Dec 17 '09 at 15:16
Try adjusting the "Experience" tab in the settings of the MSTSC connection to optimize for a lower bandwidth connection and see if that makes a difference in the perceived speed. This will disable things like the desktop background, font smoothing, desktop composition, etc. – pk. Dec 17 '09 at 15:43
We've tried MSTSC/RDP and VNC, both have drawbacks. Thanks to all for the suggestions. I was also going to look at RADMIN. Any thoughts? – Anonymous Dec 17 '09 at 20:34
You might also like to see about either getting that app fixed or replace it with a less buggy one. It clearly has some problems. Additionally, if it should be running as a service to avoid log ons/ log offs affecting it. – John Gardeniers Dec 17 '09 at 21:35

Dameware is fairly decent, but I'd really try to fix your MSTSC problems and use that.

share|improve this answer
+1 for Dameware. You only pay for the management console and not the agents and the agents can be pushed to each server, so no manual install is needed. – joeqwerty Dec 17 '09 at 13:28
+1 for fixing the underlying problem, this is NOT normal. I'd be concerned. – Kara Marfia Dec 17 '09 at 15:38
@Kara: It may be perfectly normal for the application to crash in a TS environment. Not every application is written for and not every developer codes for Terminal Services. – joeqwerty Dec 17 '09 at 18:04
@joeqwerty I don't think ignoring the underlying problem will help, this may manifest with Dameware was well, its unknown. User might be able to log in as /admin (/console pre 2008 TS) to see if there is any difference. – Jakub Dec 17 '09 at 18:29

I've been always using RDP for windows servers. I don't think anything beats it in terms of speed and availability. So definitely try to figure out why isn't it working properly.

share|improve this answer

I use No Machines NX server and client and find they work great. Like you are sitting in front of the machine even across the internet. They also work great in a mixed environment as they have server and client systems for both Linux and Windows.

share|improve this answer
NX version 4 will have a Windows server component, but the current version (3.5) supports Windows clients only. Server components are available for Linux and Solaris. – Skyhawk Dec 1 '11 at 4:07
You are correct I only used it to connect with Linux servers using both the Linux and Windows client I did not realize that there was no Windows server – Nunya Dec 29 '11 at 19:04