Windows Server 2008 SP2: What's in it for Terminal Servers?
in Microsoft on Terminal server
As you’re most likely aware, Microsoft has recently made available Windows Vista and Windows Server 2008 Service Pack 2. If you would like to know the details of every single fix and feature in the service pack, download this spreadsheet: Hotfix and Security Update List: Windows Server 2008 SP2 and Windows Vista SP2.
What’s always interesting to me is what is in the latest service packs that will directly benefit Terminal Servers. The table below lists all of the hotfixes in SP2 that directly relate to Terminal Services, and it’s quite the list. So it’s time to get testing and deploying:
| KB | Title |
|---|---|
| 951149 | Stop error on a Windows Server 2008-based terminal server when the server is running under a heavy load: 0x0000000A |
| 957081 | The query fails when you enter the terminal server farm name in the TS Web Access Administration window to query remote program information in Windows Server 2008 |
| 946068 | Stop error message on a terminal server that is running Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2: Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT) |
| 950054 | When you browse a Web page by using Internet Explorer 7 on a terminal server the colors that are displayed in the MDI child forms of the Web page may be incorrect |
| 950086 | A memory leak may occur in the non-paged pool memory on the Windows Server 2008-based terminal server when you log on to and log off from a Windows Server 2008-based terminal server through an RDP connection |
| 951749 | Stop error message on a terminal server that is running Windows Server 2003 SP1 or Windows Server 2003 SP2: Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT) |
| 951954 | Error message when you run an application on a terminal server that is running Windows Server 2008 or Windows Vista with Service Pack 1: Stop 0x0000008E |
| 957877 | Stop error on a Windows Server 2003-based terminal server that has hotfix 951749 installed: 0x0000008E |
| 966325 | Some terminal sessions stop responding and users cannot complete the logon process when a Windows Server 2008 terminal server is under heavy stress |
| 958656 | Client-side rendering in Windows Server 2008 and in Windows Vista may decrease performance on Windows Server 2008-based terminal servers |
| 952234 | When you establish a Terminal Services session that requires smart card authentication to log on to a Windows Server 2008-based terminal server the Terminal Services session stops responding |
| 954910 | Error message when you use smart card authentication to log on to a Windows Server 2008-based terminal server from a client computer that is running Windows Vista or Windows Server 2008: 0xC000040C |
| 949914 | Citrix ICA clients may crash when they are connecting to a Windows Server 2008-based terminal server that has Citrix Presentation Server installed |
| 950118 | You cannot reuse a virtual channel handle after you disconnect and then reconnect a Terminal Services session that is established on a Windows Server 2008-based terminal server |
| 951422 | The WTSQuerySessionInformation function on a Windows Server 2008-based terminal server returns ambiguous IPv6 address data |
| 951674 | Terminal Services session limit values in Windows Server 2008 are interpreted incorrectly by Windows Server 2003 terminal servers |
| 955365 | The Windows Server 2008 Terminal Services Session Broker service incorrectly balances the load among terminal servers after it runs for a while |
| 956438 | A Windows Server 2003-based or Windows Server 2008-based terminal server stops accepting new connections and existing connections stop responding |
| 957068 | Event 1004 is logged even though a user successfully logs on to a Windows Server 2008-based terminal licensing server that has Per User terminal licenses installed: The terminal server cannot issue a client license |
| 958106 | Some components of an application may not be displayed correctly in a Terminal Services session if you connect to a terminal server by using RDC 6.1 from a client computer that is running Windows XP SP3 Windows Vista SP1 or Windows Server 2008 |
| 958612 | Citrix ICA clients are not disconnected from a Windows Server 2008 terminal server as expected when the grace period has expired and a terminal license server is not configured |
| 958944 | A Windows Server 2008-based server that is running the Terminal Server role reports a Stop error when you control a session remotely from inside a session that is already being controlled remotely: 0x00000050 |
| 960470 | The pointer position behaves incorrectly when you use RDC to connect to a terminal server from a Windows Vista-based or Windows Server 2008-based client computer and you run an application that calls the SetCursorPos function |
| 960742 | Clients cannot log on to a Windows Server 2008-based terminal server through RDP connections if the terminal server is set to listen on only one of the network adapters |
| 967609 | The application compatibility scripts do not run on a terminal server that is running Windows Server 2008 when a user creates a terminal session for the first time |
