KB: “High CPU utilization in Remote Desktop session after remotely connecting to a computer that is Windows Server 2008 R2”

A new KB article was released to resolve an issue; in case you remotely connect to a computer that is running Windows 7 or Windows Server 2008 R2, the Svchost.exe process for terminal services and the Lsass.exe process consumes excessive CPU resources. This issue occurs because of an infinite failure loop that occurs in the Termsrv.dll file.

It applies to:

Windows 7

Windows 7 Service Pack 1 (SP1)

Windows Server 2008 R2

Windows Server 2008 R2 Service Pack 1 (SP1)

Source en download: http://support.microsoft.com/kb/2750090/en-us?sd=rss&spid=14134

Remote Desktop Services terminate on startup

A new KB article (2728032 ) was released by Microsoft yesterday related to a logged Application Crash event on every server reboot when Remote Desktop Services is installed. The issue seems to occurs if you have configured the Remote Desktop License Servers directly in the Registry. It applies to Windows Server 2008 R2. For more details taken from the KB article below

Symptoms
On a Windows Server 2008 R2, you have Remote Deskop Services (RDS) role installed, and on every server reboot you get the following Application Crash event logged:

Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: mstlsapi.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c829

Cause
This issue occurs if you have configured the Terminal Services License Servers directly in the Registry.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TermService\Parameters\LicenseServers

Value Type: REG_MULTI_SZ
Value SpecifiedLicenseServers
Note: The above registry value is a Mult Line entry, and if the last line is not an additonal emptyLine, but terminated early, the crash may occur.

Resolution
Add an addional empty Line to the List of SpecifiedLicenseServers, or configure the License Servers with Group Policy

Source: http://support.microsoft.com/kb/2728032/en-us?sd=rss&spid=14134

"The system cannot find the file specified" error message when you print a document on a Windows Server 2008 R2-based terminal server

A new KB Article (with hotfix) was released regarding print issue when performing a printjob to a network printer from an application that hosts Internet Explorer 9 and that is compiled with the /TSAWARE:NO option on the terminal server.

 Article ID: 2646168 - Last Review: February 16, 2012 - Revision: 1.0
"The system cannot find the file specified" error message when you print a document on a Windows Server 2008 R2-based terminal server

"...Consider the following scenario:

• You establish a Remote Desktop Services session to a Windows Server 2008 R2-based terminal server that has Windows Internet Explorer 9 installed.
• You do not redirect a printer to the Remote Desktop Services session.
• You run an application that hosts Internet Explorer 9 and that is compiled with the /TSAWARE:NO option on the terminal server.
• You try to print a document to a network printer by using this application.

In this scenario, the printer does not print the document. Additionally, you receive an error message that resembles the following: The system cannot find the file specified..."

Source: http://support.microsoft.com/kb/2646168/en-us?sd=rss&spid=14134

"Input Capture Window" shows on local desktop when you start Windows Remote Assistance as a RemoteApp

A new ("FAST PUBLISH") KB article was released by Microsoft today regarding running Windows Remote Assistance (msra.exe) as a RemoteApp hosted on a Windows Server 2008 R2. The article states that using applications like Windows Remote Assistance as RemoteApp is not a supported scenario in Windows Server 2008 R2.

Article ID: 2674002 - Last Review: February 15, 2012 - Revision: 1.0
"Input Capture Window" shows on local desktop when you start Windows Remote Assistance as a RemoteApp

"...When you start Windows Remote Assistance (msra.exe) as a RemoteApp hosted on a Windows Server 2008 R2, you may see an extra window showing up on the Taskbar with the title "Input Capture Window" on your workstation. Also the desktop is not redrawn correctly.

Using applications like Windows Remote Assistance as RemoteApp is not a supported scenario in Windows Server 2008 R2..."
Source: http://support.microsoft.com/kb/2674002/en-us?sd=rss&spid=14134

A multithreaded application might crash in Windows 7 or in Windows Server 2008 R2

A new hotfix has been released today regarding an issue with applications running on Windows Server 2008 R2 (and Windows 7) that are multithreaded and use a heap.

Article ID: 2545627 - Last Review: February 15, 2012 - Revision: 1.0
A multithreaded application might crash in Windows 7 or in Windows Server 2008 R2
On a computer that is running Windows 7 or Windows Server 2008 R2, you use a multithreaded application that uses a heap. In this situation, the application might crash unexpectedly because of a race condition.
Source: http://support.microsoft.com/kb/2545627/en-us?sd=rss&spid=14134

Aggregate of common issues seen with Remote Desktop Services updates to revision 3.0

The "aggregate of common issues list" for with Remote Desktop Services in 2008 R2 has been updated to revision 3.0 yesterday.

Source http://support.microsoft.com/kb/2601888

"...This article summarizes the available hotfixes and updatestfix for issues that can occur in Remote Desktop Services (Terminal Services) for Windows Server 2008 R2 environments. For Windows Server 2008 Terminal Services updates, please see 2312539 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;2312539) .

NOTE: This list is an aggregate of common issues seen with Remote Desktop Services (Terminal Services) in Windows Server 2008 R2. Do not proactively install the following patches unless needed. If you believe that you are experiencing an issue listed below, install just the hotfix for that specific issue. If the specific hotfix is listed for your issue we recommend that you evaluate these hotfixes and updates to determine if they apply to specific Windows version and ServicePack level.

The hotfixes and updates are arranged by component areas within Remote Desktop Services 2008 R2 environment and could apply to Windows XP, Windows Vista and Windows 7 Remote Desktop Clients..."

Remote Desktop session does not respond to keyboard input or mouse input after it loses the focus

Article ID: 2579381 - Last Review: August 10, 2011 - Revision: 1.0
A remote desktop session does not respond to keyboard input or mouse input after it loses the focus in Windows 7 or in Windows Server 2008 R2

A fix has been released for the scenario where the remote desktop session does not respond to any of the keyboard or mouse input in some scenarios.

The issue occurs because the remote desktop ActiveX object does not deactivate the focus of the remote desktop session when the focus is lost. Because the focus is still activated, the remote desktop ActiveX object cannot set the focus of the remote desktop session again when you change the focus back to the session.

Source: http://support.microsoft.com/kb/2579381/en-us?sd=rss&spid=14134

New KB: Session disconnects even when disconnection is cancelled in a VDI environment

A new KB has been published today that addresses the issue where you click the 'X' on the Connection Bar of a VDI environment and then click 'Cancel', the session disconnects regardless.

Article ID: 2572647 - Last Review: June 27, 2011 - Revision: 1.0
Session disconnects even when disconnection is cancelled in a VDI environment
http://support.microsoft.com/kb/2572647/en-us?sd=rss&spid=14134

Shadowing error: The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

In addition to an earlier blogpost about troubleshooting shadowing (remote controlling) sessions; http://microsoftplatform.blogspot.com/2011/04/troubleshooting-remote-control-session.html

Microsoft released KB2533983 yesterday. This is about shadowing remote session in which Aero is enabled. This is not supported and could raise the following error:

The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

How do you know Aero is enabled for a user? The existence of the Dwm.exe process in the user session indicates that Aero is enabled for that session.

In addition the following events are raised:

Log Name: System
Source: TermDD
Date: 4/5/2011 1:14:24 PM
Event ID: 50
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computername.domain.com
Description:
The RDP protocol component WD detected an error in the protocol stream and has disconnected the client.
Log Name: System
Source: TermDD
Date: 4/5/2011 1:14:24 PM
Event ID: 56
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computername.domain.com
Description:
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: fe80:0000:0000:0000:e499:f014:83ea:8221.

Source: http://support.microsoft.com/kb/2533983/en-us?sd=rss&spid=14134