Hello, I'm starting a new thread for this issue since the one here http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/02a9843f-a977-4061-a0ab-64ebee803855 is marked as "Solved" even though it isn't. The issue is that the performance of the Remote Desktop Services Manager in Windows 7 renders it unusable. I can add servers to the console, but when I start it up, it flickers several times, hangs when I try to click on any of the servers, and sometimes just stops altogether. I've changed the refresh interval to several hundreds of seconds and manual but nothing seems to change. I currently have around 15 servers loaded up in the console which doesn't seem like an extraordinary amount to me. Is anyone else continuing to have this issue in Windows 7? Any suggestions on a fix or perhaps another product that does what this one is supposed to?

Here are some details on an error, in case it helps... Unhandled Exception in Managed Code Snap-in FX:{3FCE72B6-A31B-43ac-ADDA-120E1E56EB0F} Exception has been thrown by the target of an invocation. Exception type: System.Reflection.TargetInvocationException Exception stack trace: at Microsoft.ManagementConsole.Executive.MmcThreadMessageWindow.OnThreadException(Exception e) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.SafeNativeMethods.MessageBox(HandleRef hWnd, String text, String caption, Int32 type) at System.Windows.Forms.MessageBox.ShowCore(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options, Boolean showHelp) at System.Windows.Forms.MessageBox.Show(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options) at Microsoft.ManagementConsole.Advanced.MessageBoxParameters.ShowDialog(IWin32Window parent) at Microsoft.ManagementConsole.Internal.ConsoleDialogHost.ShowDialog(WaitCursor waitCursor, ShowDialogCallback callback) at Microsoft.TerminalServices.Monitor.SnapIn.GroupNode.ClearAllServersFromThisGroup() at Microsoft.ManagementConsole.ScopeNode.DoAction(Int32 actionId, IRequestStatus requestStatus) at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request) at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo) at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Here are some details on an error, in case it helps... Unhandled Exception in Managed Code Snap-in FX:{3FCE72B6-A31B-43ac-ADDA-120E1E56EB0F} Exception has been thrown by the target of an invocation. Exception type: System.Reflection.TargetInvocationException Exception stack trace: at Microsoft.ManagementConsole.Executive.MmcThreadMessageWindow.OnThreadException(Exception e) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.SafeNativeMethods.MessageBox(HandleRef hWnd, String text, String caption, Int32 type) at System.Windows.Forms.MessageBox.ShowCore(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options, Boolean showHelp) at System.Windows.Forms.MessageBox.Show(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options) at Microsoft.ManagementConsole.Advanced.MessageBoxParameters.ShowDialog(IWin32Window parent) at Microsoft.ManagementConsole.Internal.ConsoleDialogHost.ShowDialog(WaitCursor waitCursor, ShowDialogCallback callback) at Microsoft.TerminalServices.Monitor.SnapIn.GroupNode.ClearAllServersFromThisGroup() at Microsoft.ManagementConsole.ScopeNode.DoAction(Int32 actionId, IRequestStatus requestStatus) at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request) at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo) at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Hello Nardo, Thanks for posting in Microsoft TechNet forums. I have checked the information in another thread of you. This issue is very possibly related to a known issue for Remote Desktop Services Manager console of Windows 7 RSAT. When the target computers are large number of Windows Server 2003, the user interface performance is quite slow and unstable. Please check if there is a similar situation for Windows Server 2008 or Windows Server 2008 R2 as the target computers. According to the known issue information, this issue should not happen for Windows Server 2008 or later. Based on the description of the known issue, a workaround is to use “Refresh Manually” for Process List. Did you try this action? Please let me know the result. Thanks! Best Regards, Miya Yao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello Miya, Thanks for the reply. Most of the target computers I am trying to connect to are Server 2003. I only have one Server2008 R2 listed. I have tried the "Refresh Manually" for Processes List and Status Dialog Boxes. There is no change.

Hello Miya, Thanks for the reply. Most of the target computers I am trying to connect to are Server 2003. I only have one Server2008 R2 listed. I have tried the "Refresh Manually" for Processes List and Status Dialog Boxes. There is no change.

Hello Nardo, If I get any new information on this known issue, I will update here to let you know. Thanks for your patience and understanding. Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello Nardo, If I get any new information on this known issue, I will update here to let you know. Thanks for your patience and understanding. Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Nardo, BTW, since it’s a known issue, I will mark my former reply as answer in order to let other community members know it. Best Regards, Miya Yao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Nardo, BTW, since it’s a known issue, I will mark my former reply as answer in order to let other community members know it. Best Regards, Miya Yao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I know there is nothing I can do to change it, but I have a real problem with administrators of this forum marking things as "answers" when they clearly aren't. A known issue is not the same as a resolution. Now that this is marked as solved how do I know that it is still being looked in to? I don't. I'm sure this is how you've been told to handle questions that you can't answer, but from a customer perspective it comes across as sweeping these problems under the rug and forgetting about them.

I know there is nothing I can do to change it, but I have a real problem with administrators of this forum marking things as "answers" when they clearly aren't. A known issue is not the same as a resolution. Now that this is marked as solved how do I know that it is still being looked in to? I don't. I'm sure this is how you've been told to handle questions that you can't answer, but from a customer perspective it comes across as sweeping these problems under the rug and forgetting about them.

Hi Nardo, The reason for marking it as answer is to let other community members understand this known issue. I’m going to unmark it and sorry for making you felt uncomfortable with it. Please keep the computer update automatically in case there’s any related important update installed. Best Regards, Miya Yao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Nardo, The reason for marking it as answer is to let other community members understand this known issue. I’m going to unmark it and sorry for making you felt uncomfortable with it. Please keep the computer update automatically in case there’s any related important update installed. Best Regards, Miya Yao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I suppose this is the same issue that I am having. In my case, I enter a WS2008r2 remote desktop session as administrator. I open Remote Desktop Services Manager and remote control another users session. When I try to exit the remote control, my session hangs and I have to reconnect to it to regain control. This was never an issue under WS2003r2 or prior. Once a fix is known I would appreciate hearing back on this thread. Seems like this would have been addressed months ago???GaryPharr

I suppose this is the same issue that I am having. In my case, I enter a WS2008r2 remote desktop session as administrator. I open Remote Desktop Services Manager and remote control another users session. When I try to exit the remote control, my session hangs and I have to reconnect to it to regain control. This was never an issue under WS2003r2 or prior. Once a fix is known I would appreciate hearing back on this thread. Seems like this would have been addressed months ago???GaryPharr

I want to include myself in this since I also find it frustrating. To quote DentonT from the other thread http://social.technet.microsoft.com/Forums/en-GB/w7itpronetworking/thread/02a9843f-a977-4061-a0ab-64ebee803855 We're having similar issues at our company after upgrading to Windows 7 64-bit from Windows XP. Terminal Services Manager works perfect on WinXP, but the Remote Desktop Services Manager on Windows 7 is pretty much unusable. The screen will flicker and freeze constantly. When it 'freezes' the entire window goes white - clients are not visible. When they reappear, our operator has to try and click through quickly and do what we need to do before the next freeze. It looks like it's attempting to refresh and getting stuck (though refresh times are all set to manual). Except, I am using 32bit Windows 7 Enterprise. I have 4 Windows Server 2003/R2 servers in my console and even if I create my own console (instead of using what is automatically in the administrative tools folder) and set refresh to manual, it still happens. I tried to run the tsadmin.exe from the server (just copied it to my machine) and it opens, but then dies in a few seconds. So, the only solution is to open a remote desktop session to a server and use it from there. I have confirmed that it even happens with only 1 computer added to the console, but not as badly. It seems to compound for each server.

I want to include myself in this since I also find it frustrating. To quote DentonT from the other thread http://social.technet.microsoft.com/Forums/en-GB/w7itpronetworking/thread/02a9843f-a977-4061-a0ab-64ebee803855 We're having similar issues at our company after upgrading to Windows 7 64-bit from Windows XP. Terminal Services Manager works perfect on WinXP, but the Remote Desktop Services Manager on Windows 7 is pretty much unusable. The screen will flicker and freeze constantly. When it 'freezes' the entire window goes white - clients are not visible. When they reappear, our operator has to try and click through quickly and do what we need to do before the next freeze. It looks like it's attempting to refresh and getting stuck (though refresh times are all set to manual). Except, I am using 32bit Windows 7 Enterprise. I have 4 Windows Server 2003/R2 servers in my console and even if I create my own console (instead of using what is automatically in the administrative tools folder) and set refresh to manual, it still happens. I tried to run the tsadmin.exe from the server (just copied it to my machine) and it opens, but then dies in a few seconds. So, the only solution is to open a remote desktop session to a server and use it from there. I have confirmed that it even happens with only 1 computer added to the console, but not as badly. It seems to compound for each server.

I would like to offer that in my experience with this issue the level of "Desktop Experience" has a lot to do with being able to successfully remote view/control another desktop or Terminal Server session. If the remote desktop is using Desktop Background + Font Smoothing + Desktop Composition + Show Window Contents While Dragging + Menu and Window Animation, the remote view/control will lock up everytime. When these elements are not in use, remote view/control seems to work fine.GaryPharr

I would like to offer that in my experience with this issue the level of "Desktop Experience" has a lot to do with being able to successfully remote view/control another desktop or Terminal Server session. If the remote desktop is using Desktop Background + Font Smoothing + Desktop Composition + Show Window Contents While Dragging + Menu and Window Animation, the remote view/control will lock up everytime. When these elements are not in use, remote view/control seems to work fine. GaryPharr I am sorry, but this has nothing to do with this issue. You cannot even get to "remote control" since the screen of the management console _itself_ refreshes every second locking up everything. If you are lucky you can click on a user quickly and log him/her off. But to be honest: completely useless tool in it's current state. Use the XP version of the management console and everything is fine (on an XP machine)... But to make sure this has nothing to do with this issue: all our 15 2003R2 terminal servers are running in "performance" mode, no animations, no smoothing or desktop composition or window contents while dragging. I would like to be informed of a solution also. I cannot believe Microsoft is not making this a priority. The tool to administer a TS farm is simply not working. Do they expect us to upgrade our TS to RDS 2008R2 so our management tools will _possibly_ work? Arrogant attitude...

I would like to offer that in my experience with this issue the level of "Desktop Experience" has a lot to do with being able to successfully remote view/control another desktop or Terminal Server session. If the remote desktop is using Desktop Background + Font Smoothing + Desktop Composition + Show Window Contents While Dragging + Menu and Window Animation, the remote view/control will lock up everytime. When these elements are not in use, remote view/control seems to work fine. GaryPharr I am sorry, but this has nothing to do with this issue. You cannot even get to "remote control" since the screen of the management console _itself_ refreshes every second locking up everything. If you are lucky you can click on a user quickly and log him/her off. But to be honest: completely useless tool in it's current state. Use the XP version of the management console and everything is fine (on an XP machine)... But to make sure this has nothing to do with this issue: all our 15 2003R2 terminal servers are running in "performance" mode, no animations, no smoothing or desktop composition or window contents while dragging. I would like to be informed of a solution also. I cannot believe Microsoft is not making this a priority. The tool to administer a TS farm is simply not working. Do they expect us to upgrade our TS to RDS 2008R2 so our management tools will _possibly_ work? Arrogant attitude...

We have the same problem with RDS Manger running on 2008 R2 servers. Setting the refresh rate to manual has no effect at all. The only way we can use it effectively is to keep a 2003 server around and use it from that. A fix rather than a broken workaround would be nice!

We have the same problem with RDS Manger running on 2008 R2 servers. Setting the refresh rate to manual has no effect at all. The only way we can use it effectively is to keep a 2003 server around and use it from that. A fix rather than a broken workaround would be nice!

I have to say that since SP1 and some other Windows 7 updates, we are no longer having issues with this snapin. We are managing 12 terminalservers (2003 R2) with this console now, no problems anymore. Microsoft seems to have fixed the issue. I cannot say which specific update fixed it, sorry. It just seems to work now :)

I would agree. I've installed SP1 on my Windows 7 box and it seems to run fine now. It's either that or the fact that I'm running with 8 gigs of RAM.

I would agree. I've installed SP1 on my Windows 7 box and it seems to run fine now. It's either that or the fact that I'm running with 8 gigs of RAM.

I would like to be updated when the issue is resolved. We are a Server 2008R2 sp1 RDS environment (15 TS) and have the issue also (freezing RDS Manager tool). I remote desktop into an "admin" server that we have (server 2008 r2 with sp1) and I feel the above does help a little, but it is not a fix. I still can't reliably use the tool... totally unacceptable. I have also changed the RDS Manager options to not refresh automatically- again helps but I still see random freezing inside the tool.-Ben

I would like to be updated when the issue is resolved. We are a Server 2008R2 sp1 RDS environment (15 TS) and have the issue also (freezing RDS Manager tool). I remote desktop into an "admin" server that we have (server 2008 r2 with sp1) and I feel the above does help a little, but it is not a fix. I still can't reliably use the tool... totally unacceptable. I have also changed the RDS Manager options to not refresh automatically- again helps but I still see random freezing inside the tool.-Ben

Is there an updates to this yet, Our terminal server is a 2008 enterprise server running under a 2008 datacentre Hyper V host, if I start a remote session onto the TS as administrator and then go into Remote Desktop Service Manager, I can select a user, right click and select Remote Control I get the following error Clicking OK and I get the following error The Remote desktop Service Manger then needs to be closed, Sometimes the user who I tried to Remote control is disconnected. I have tried two different Windows 7 PC and get the same results Can somebody please advise if there is a fix for this yet Tim

Is there an updates to this yet, Our terminal server is a 2008 enterprise server running under a 2008 datacentre Hyper V host, if I start a remote session onto the TS as administrator and then go into Remote Desktop Service Manager, I can select a user, right click and select Remote Control I get the following error Clicking OK and I get the following error The Remote desktop Service Manger then needs to be closed, Sometimes the user who I tried to Remote control is disconnected. I have tried two different Windows 7 PC and get the same results Can somebody please advise if there is a fix for this yet Tim