Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have this consistent problem of RDSM crashing in Server 2008 R2. It is either really slow to open, sometimes never opens, or after it's been open and working properly for a bit, stops working, and forces an unload of the snap-in. It's done this since the deployment of this server, new hardware, new instance of S2k8. Domain Administrator login.

I am using it to manage 3 Terminal Servers, the other two are S2k3.

I've used it without issues on other 2008 servers.

share|improve this question

3 Answers 3

Defective hardware, bad drivers.

share|improve this answer
    
On the hardware thought, the server is running under VMWare on an ESX machine. Forgot to include that bit. –  milkmood May 27 '11 at 22:43
    
Still, could be. Drivers or some defective RAM. Move he VM to another host, pull that one for testing. –  TomTom May 28 '11 at 4:03

This has nothing to do with hardware. What sort of hardware would only affect this one application? Either way I have ruled out hardware because the problem occurs on many computers. A simple Google search will confirm this; the Internet is overflowing with complaints about this problem (and, humorously, threads that Microsoft marked as "answered" even though people are still complaining that the problem remains).

This is a Microsoft software problem with RDSM for Windows Server 2008 and Windows 7 that I have never been able to solve. This problem has followed me between Win7 computers and even at 3 different companies with completely separate environments.

The problem only appears when you try to manage multiple remote servers. As soon as I add a few servers to the console it will eventually have the problem. It might work for a few minutes, or a day, or 3 weeks. But eventually RDSM will start crashing as soon as I open it. It becomes completely unusable until I delete all the MMC configuration data from my user profile, and start with a clean slate.

share|improve this answer

I have the same problem.

It occurs when one or more RDP servers connected in your MMC to Remote Desktop Services Manager is down.

The only way to get around this is to right-click on the down servers and select "Disconnect".

Also if all servers are up when you open your MSC file, and then you shut several down, the MMC does not crash.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.