Article ID: 951048 - View products that this article applies to.
Consider the following scenario. You log on to a Windows Server 2008 Terminal Services RemoteApp (TS RemoteApp) session. The TS RemoteApp session includes the startup applications and the Run registry entry or the RunOnce registry entry. Then, you try to start an application in the TS RemoteApp session. In this scenario, the application does not start.
This issue occurs because you try to start an application that relies on the Explorer.exe file. By design, the TS RemoteApp session implements limited functionality. For example, the TS RemoteApp session does not process the following items:
To work around this issue, use one of the following methods.
Method 1: Run the startup applications as a part of a user's logon settingsTo run the startup applications in the TS RemoteApp session, you can specify the startup applications as a part of a user's logon settings in Group Policy. Because Group Policy controls these settings, any startup application that you specify runs as expected when the user logs on.
To specify the startup applications as a part of a user's logon settings, follow these steps:
Method 2: Start the Runonce.exe file together with the /AlternateShellStartup switchSome applications that rely on the Explorer.exe file may run in the TS RemoteApp session if you add the Runonce.exe file to a user’s logon script. To do this, follow these steps:
Article ID: 951048 - Last Review: October 7, 2010 - Revision: 3.0