

To 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. Method 1: Run the startup applications as a part of a user's logon settings To work around this issue, use one of the following methods. For example, the TS RemoteApp session does not process the following items: By design, the TS RemoteApp session implements limited functionality. This issue occurs because you try to start an application that relies on the Explorer.exe file.

In this scenario, the application does not start. Then, you try to start an application in the TS RemoteApp session. The TS RemoteApp session includes the startup applications and the Run registry entry or the RunOnce registry entry. You log on to a Windows Server Terminal Services RemoteApp (TS RemoteApp) session. This article provides workarounds for an issue where you can't run an application that relies on the Explorer.exe file in a Terminal Services RemoteApp session.Īpplies to: Windows Server 2012 R2 Original KB number: 951048 SymptomsĬonsider the following scenario.
