Question : Windows 2008 Server immediately logging off Terminal Services sessions created from .msi / Windows Install Package

    My users are having an issue in which they log on to a terminal services session from a shortcut created by an .msi file distributed from TS RemoteApp Manager and they are immediately logged off. You can see the app starting up and the user profile being loaded and the normal process of logging onto the server, but after 'creating desktop' it says logging off and their session is over with. There doesn't seem to be any rhyme or reason to when it does this. (that's been that hardest part about trying to fix it). Sometimes when a user experiences this problem they can successfully logon from a different computer without an issue. Sometimes that doesn't make a difference. Sometimes you can try logging on as a different user on that same machine, and it works. Other times, that doesn't make a difference. I have had a lot of difficulty in even narrowing the search to determine precisely what the problem is.

A couple of interesting things are occuring. For one, this problem never happens if the user initiates a regular remote desktop connection session. It only happens when they use the shortcut created by the .msi file deployed from the Terminal Server for distribution. Also, one workaround that I have been using is logging on to the Terminal Server via a regular RDP connection, then disconnecting that session, then having the user try to connect via their shortcut. When they do that, they are able to get connected. (I assume because this allows them to bypass the logon process.)

All available Windows/Microsoft updates have been installed.

There have been a few different errors/warnings in event viewer that may or may not be related:

Application Log:
Warning
Event 1530, User Profile Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  

 DETAIL -
 1 user registry handles leaked from \Registry\User\S-1-5-21-507921405-1897051121-839522115-2534:
Process 440 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-507921405-1897051121-839522115-2534\Printers\DevModePerUser

System Log
Event 7011Service Control Manager Event Log Provider
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

I have done searches on both these messages and haven't found anything that seems to apply to this series of problems. However here are a few different things I have tried/looked in to:

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22011266.html?eeSearch=true



I slightly suspect that the issue may have something to do with drive/printer mapping during the logon process because of the message referencing the UmRdpService, but I really don't know. I tried turning off all mappings under the properties of the RDP protocol but it didn't make a difference.

Any suggestions that anyone can make would be greatly appreciated.

Tbone

Answer : Windows 2008 Server immediately logging off Terminal Services sessions created from .msi / Windows Install Package

Thanks for the suggestions that were posted. We ended up just having to go with regular workstation installs as we ran into a time crunch on this.