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:
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:
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:
Troubleshooting / Resolution: Troubleshooting will depend on which problem you are experiencing:
RemoteApp does not start or users cannot run the RemoteApp
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.