Performance issues due to Inactive Terminal Server Ports

re: Performance issues due to Inactive Terminal Server Ports

Blake Morrison - MSFT — Mon, 01 Apr 2013 15:17:14 GMT

@Steve Boer: Yes, it is safe to run while users are logged on as it only removes the inactive ports, not those currently in use.

re: Performance issues due to Inactive Terminal Server Ports

Steve Boer — Thu, 28 Mar 2013 19:55:48 GMT

Is it safe to run this fix while users are logged in?

re: Performance issues due to Inactive Terminal Server Ports

George — Tue, 16 Oct 2012 10:02:21 GMT

On my Windows 2008 R2 SP1 TS ports registry appear under:

HKLM\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\##?#Root#SYSTEM#0001#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}

so FixIt tool doesn't remove anything for me.

re: Performance issues due to Inactive Terminal Server Ports

ForbesCorporation — Fri, 17 Aug 2012 03:37:26 GMT

Scott if you are running Citrix it uses the Microsoft Backbone of Terminal Server. Citrix no longer can use the CODE for controls of the OS as per agreement back in the Early 90’s. This was after Terminal Server 4.0. Again if Client Printing is set on “now Called Printer Redirection” these will accumulate. If you use Graphon’s GO-GLOBAL www.graphon.com they have there own Server source Code which does not interface with any of the Windows Terminal Server Code like Citrix. This is one of the only Cloud Based software’s I know of that has written all of their own source code and so printing is done differently on that platform. As Jdickson289 has suggested open the registry and review the number of key entries accumulated for a definitive answer. Citrix does create there own HOT Fixes separate from Microsoft to address some of these issues.

re: Performance issues due to Inactive Terminal Server Ports

ForbesCorporation — Fri, 17 Aug 2012 03:22:37 GMT

Patrick the keys don't get purged and will accumulate into the thousands depending on how many users you have running on the Terminal Server. This is a very old issue that goes back to Server 2000 and maybe earlier. As Blake said above every time a TS session starts and Client Printing is Turned on (Now called Windows Printer Redirection) these will be created. If you use Network Printing only in the Terminal Server Environment they do appear (Now shown as Windows Printer with a check box DISABLE under RDP-TCP Properties for the Terminal Services Configuration. In Server 2000 when we first saw this issue 12 years ago we would manual clean them out and delete all the keys. If you shut off Client printing (Disable in Server 2008) I think they will never return. These days many people work from home and so turning on Client Printing “Windows Printer Redirection” in Terminal Server these days is generally set on. When it is turned on as an example a 2008 server with 80 users can create about 600 entries in a day or two even if most of the users run Network Printers and don’t have a client printer the entries are still made. One day we estimated a server to have had 24,000 entries. Its important to use the fix listed on this page.

re: Performance issues due to Inactive Terminal Server Ports

Patrick Hoban — Sat, 02 Jun 2012 13:55:11 GMT

Hotfix aside, what is the expected behavior of registry key in question? When no one is logged in should there be no subkeys, etc? Is the issue that the subkeys are not properly being purged at logoff?

re: Performance issues due to Inactive Terminal Server Ports

Adam Richards — Mon, 16 Apr 2012 14:29:08 GMT

Marc,

200 is not a hard limit - it's an indicator of a potential problem that should be addressed with the FixIT and hotfix to prevent a problem in the future.

re: Performance issues due to Inactive Terminal Server Ports

Marc — Mon, 16 Apr 2012 00:49:57 GMT

jdickson289's comment about 200 entries under the reg key suggests that this is a limitation of the OS. Is this correct?

re: Performance issues due to Inactive Terminal Server Ports

MR — Wed, 11 Apr 2012 02:17:28 GMT

Is the post by jdickson289 suggesting that issues occur if the count of ports in general gets above 200?

re: Performance issues due to Inactive Terminal Server Ports

jdickson289 — Wed, 14 Mar 2012 14:04:34 GMT

Please check the number of entries under [HKLM\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\##?#Root#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}].

If there are more than 200 then suggest to install the hotfix and run the FixIT to remove any entries and prevent further accumulation of TS Inactive Ports.