FIX: You cannot start a RemoteApp application when its name contains accented characters

Applies to: Forefront Unified Access Gateway 2010

Symptoms


Consider the following scenario:
  • You publish a RemoteApp application on a Microsoft Forefront Unified Access Gateway (UAG) trunk.
  • The name of the RemoteApp application contains accented characters and appears correct on the portal page.
  • You try to start the application.

In this scenario, you receive the following error message:
RemoteApp

This RDP File is corrupted. The remote connection cannot be started.

Additionally, you may notice that the RemoteApp dialog box displays the application name as garbled characters.

Note Applications whose names use only ASCII characters start without any problems.

Cause


This problem occurs because the accented characters are not encoded correctly in the RDP data steam. This causes the client to identify the file as being corrupted.

Resolution


This problem is fixed in Rollup 1 for Forefront Unified Access Gateway 2010 Service Pack 4.

Workaround


To work around this problem, change the RemoteApp application name so that it uses only ASCII characters, and then republish the application. You must make this change in RemoteApp Manager, and a new .tspub file has to be exported that UAG can use.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.