With the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done. 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. 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 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. This includes all problems with a RemoteApp that does not display windows correctly or generally does not work correctly.Ī 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. RemoteApp starts and runs but does not work the way it should. RemoteApp does not start or users cannot run the RemoteApp. There are generally two main problem areas with RemoteApps, and scoping of the issue will depend on which problem you are experiencing: RDP file is distributed to users via a network share or direct sharing.Ī 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.

A RemoteApp is deployed in one of three ways:Ī. Terminal Server RemoteApps refers to applications deployed via Terminal Services and managed by the RemoteApp manager in Windows Server 2008. First published on TECHNET on May 14, 2009

Microsoft terminal services manager