Application launch failure on server 2008

[dlahaie]

Hello,

We are testing 2X out and were quite happy with it on a WIndows Server 2003 system. However, we need to get this up and running on our 2008 production unit before finalizing.

Here is our setup:
-The server is a Windows Server 2008 R2, clean install.
-2X is installed and for testing purposes we are publishing "Wordpad" as well as a "Desktop"
-There is an administrative account and also 3 user accounts for testing.
-Firewall on the server is turned off, although 20002 had been opened previously.

This is the problem:
-All users can use the 2X client and access the published "Desktop" with no problem
-When they try to access "Wordpad", the automated logon goes through but the application does not show up
-If I RDP into the server as the user with a failed "Wordpad" session, we can see the application running there ... just not on the client system.

Any help would be appreciated!

Thanks!

 

[gs]

Hi there,

1- Check that the terminal Server is configured to allow running of programs at startup. (Also Gpos)
( test using embeded application launch from Mstsc )

To test using embedded application launch from Mstsc use the following:
Start the application directly from msrdp (mstsc).
To do so set the following:
Click on options
Select Programs Tab
Make sure memshell can be run from mstsc from a client in the above fashion.

2- Make sure server is a Terminal server not a client OS. (e.g. XP and Win7).

3- Check that memshell.exe is being started when the user logs on.
To check this,
i. Open the taskmgr.exe and check if memshell.exe is running under that particular user.
ii. Check with user: administrator, to verify that it works.
iii. From the full desktop, Start > Run > c:\windows\system32\memshell.exe
and check if the desktop collapses to the published application.

4- User rights on memshell.exe.
( test for embedded application running memshell on connection from mstsc)

5- 2008 R2 TS ( definitely AD role breaks this ) Also AD should not be TS.
possibly might apply to others.

6- Solution (not ideal solution)
i. Add a shortcut to memshell.exe for all users.
ii. Add the shortcut to all users at

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

All Terminal Server options can be set from the Group Policies. Therefor, a System Administrator can set a group policy to help deployment of terminal servers.

Make sure that the below options are not set:

For Windows 2003
"Computer Configuration > Administrative Templates > Terminal Services > Always show desktop on Connection"

For Windows 2008 R2
"Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Always show desktop on connection"

NOTE: In these sections, you can also limit the redirected devices and limit Remote Desktop/Terminal Services options. Therefor, if you think that the user might have a problem with his TS environment, it might be useful to gather the Group Policy.
NOTE2: This group policy applies to the COMPUTER and not the user...therefore, it might be useful to get the group policy with both user and administrator to point out any differences.

Other notes:
______________
if starting memshell solves issue
windows\system32\memshell

Make sure the TS is actually setup as a TS not simply allowing remote access. ( no client OS)
Check user rights on memshell.
Check starting apps embedded test.

Kind regards,