TERMINAL SERVER: REMOTEAPPS


Description: Terminal Server RemoteApps refers to applications deployed via Terminal Services and managed by the RemoteApp manager in Windows Server 2008.  A RemoteApp is deployed in one of three ways:

  1. A .RDP file is distributed to users via a network share or direct sharing.
  2. A Windows Installer package that installs a shortcut to the RemoteApp on the client Start menu and may also associate local file extensions with the RemoteApp.
  3. Terminal Server Web Access

 

Scoping the Issue:  There are generally two main problem areas with RemoteApps, and scoping of the issue will depend on which problem you are experiencing:

  1. RemoteApp does not start or users cannot run the RemoteApp.
  2. RemoteApp starts and runs but does not work the way it should.  This includes all problems with a RemoteApp that does not display windows correctly or generally does not work correctly.

A RemoteApp that does not start usually means that the user cannot make a connection to the Terminal Server that is specified in the RemoteApp properties.  If a Terminal Server Gateway is also in use, you may need to troubleshoot the Gateway and resolve a connectivity issue there before a user would be allowed to start the RemoteApp.

If the RemoteApp starts fine but users report problems using the application, then a simple test of the application in a full desktop RDP session will determine if the issue is really with the application itself.  If the application does not have the same problem in a full RDP session then it is likely a problem specific to the deployment of the application via RemoteApps.

 

Data Gathering:  In all instances, collecting either MPS Reports with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done.  Additional data required may include the following:

  • A copy of the RDP file generated by RemoteApp manager.
  • A copy of the MSI package if the RemoteApp is deployed via MSI.
  • All relevant information about the application that is deployed as a RemoteApp.  Especially if the application does not work correctly we need to know as much information as possible, starting with specific version information.
  • If the RemoteApp does not work correctly, the steps taken to reproduce the problem will be required.
  • If possible, provide a copy of the application with instructions on how to configure it and reproduce the problem.

 

Troubleshooting / Resolution:  Troubleshooting will depend on which problem you are experiencing:

RemoteApp does not start or users cannot run the RemoteApp

  • First step is to make sure a standard connection to the same Terminal Server can be made. If the user can use the RDP client to logon to the same Terminal Server then they can probably run a RemoteApp.
  • If users are connecting via a Terminal Server Gateway, try bypassing the Gateway by connecting directly to the same Terminal Server from inside the LAN.
  • Try connecting by IP Address instead of DNS name. If the connection succeeds then there could be a general networking configuration or DNS problem.

RemoteApp starts and runs but does not work the way it should, including all problems with a RemoteApp that does not display windows correctly or generally does not work correctly.

  • Test the same application in a full desktop RDP session. If it works fine then it could be a RemoteApp specific problem.
  • Make sure the application is supported in a Terminal Server environment. Ask the vendor specifically if they support RemoteApps. If the vendor is not sure or does not know what RemoteApps are then they likely may not support it.
  • If the application was written with VB6, install the following hotfix: <placeholder for public KB967885>
  • If you are using Microsoft Dynamics as a RemoteApp or your application uses ComboBoxes, install the following hotfix: <placeholder for KB968358>

 

Additional Resources: