Consider the following scenario:
In this scenario, you receive the following error message:
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.
- 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.
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.