>

A network shared RemoteApp won’t start on the remote computer

When starting a windows 2008 (R2) RemoteApp from or depends on a network mapped drive you get the error “The program did not start on the remote computer.”

Solution: The problem is caused because the program is hosted on or depends on a network mapped drive. When starting a RemoteApp the program doesn’t wait till the logon script script is finished but just start the program directly and cannot find the right drive or program.
Workarround is to map the network drive persistant so it’s available before the RemoteApp program starts or create a batch file as RemoteApp so you can first map the network drive and then start the program.

Posted in Blog, Windows 2008, Windows 2008R2 at August 30th, 2010. 11 Comments.

Windows 2008 (R2) RemoteApp stays in disconnected state

When you close a Windows 2008 terminal server or Windows 2008 R2 remote desktop services RemoteApp the sessions stays in disconnected state.

Solution: Since Windows 2008 there is a local / group policy called ‘Set time limit for logoff of RemoteApp sessions’. You can set the policy for both computer as user configuration.

For windows 2008: Administrative Templates \ Windows Components \ Terminal Services \ Terminal Server \ Session Time Limits
For windows 2008 R2: Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop Session Host \ Session Time Limits

Posted in Blog, Windows 2008, Windows 2008R2 at August 28th, 2010. No Comments.

Sharing Buttons by Linksku