Terminal Server on 2003

[jprice]

Got terminal server setup on 2003 and everything "almost" works fine.

When the end user closes the application on the client side the connection hangs for about 60 seconds before disconnecting. If I RDP into the box it disconnects when I log off with no issue. Has me scratching my head.

I have played with the registry. I have uninstalled and reinstalled the app as well as removed and setup Terminal Server several times using different settings each time and still no luck. I have even setup terminal server on a different system running 2003 and built client setups on different dumb terms to rule out the boxes. The problem still follows.

I'm down to thinking its an issue with the application itself but before giving in wanted to know if anyone else has seen this and/or does anyone have any suggestions?

Thanks,

James

[cluberti]

You're installing the app after installing terminal services, and you're using the add/remove programs > Add new programs method to point to the setup file for the app, correct?

[jprice]

I did install the app after Term Serv was setup (by accident) but did not install the app through the add/remove > add program. I can try that if you think that would make a difference?

I'll try that and update the notes shortly.

[jprice]

I removed the program and reinstalled using the add program method with no change.

I think this has something to do with a service lingering somewhere but I can't determine where just yet?!

Thanks for the suggestion though!

[cluberti]

If you watch the TS connections to the machine from another session or the console via Terminal Services Manager mmc, you should be able to see which processes are still running in a session as it tears down. What else lingers in the session while you wait for it to log off?

[jprice]

Actually nothing out of the norm. There are the normal windows processes plus the application that is being used. And while I watched, the process for the application actually closed when the user closed it but the Term Serv connection still stayed up showing just the blue background. (term serv desktop without icons).

Edited January 7, 2008 by jprice

[cluberti]

So the app that's hanging isn't running, but the regular windows processes stick around (winlogon, lsass, csrss, etc) for a time before the session tears down?

By any chance did you make this application the default shell, rather than explorer.exe? If so, are you waiting at least 60 seconds from a full login (app is up and running) before trying to close it down?

One last thing - what happens if you add the following reg key, then log the user off and try again?

Key: HKCU\SOFTWARE\Microsoft\Cryptography\AutoEnrollment\AEExpress

(you don't need to put any values inside, just create the "AEExpress" key under the AutoEnrollment key).

[jprice]

Cluberti - Thank You.

After reading your last post I read up on your suggestions and feel pretty confident YOU have found the solution. It's amazing how much of a difference "lag" "hang" "stuck" and "DELAY" can make. I guess you really should choose your words wisely. (LOL)

http://support.microsoft.com/?kbid=901196 (You can find the suggestion here...no need to retype, correct?)

What I did to double check was....

Step 1. I opened the app and let it stay open for at least a minute and a half. After that I closed the app and everything worked as should. According to the MSKB article it has to do with the userinit.exe process.

Step 2. Just to try things out I disabled the Autoenrollment Policy and that took care of the issue without having to wait the minute and a half.

Problem is pretty much solved.

Now.....

I know that you suggested the registry key addition but I have a quick question regarding that.

The KB doc states the key as a resolution and the autoenrollment switch as a work around but since we know that the solution is connected with the auteenrollment switch should I still create this key? (Considering they say we shouldn't use the key in a "production environment".)

I will test this but you may know right off hand...will the key correct this without disabling the autoenrollment?

Thanks for your help. I appreciate your posts and you taking the time to help out!

Edited January 7, 2008 by jprice

[cluberti]

The key does the same thing, but it's on a per-user basis (HKCU) and is easier to roll back than a GPO (and easier to target as a test). The key is for testing, the GPO is for if the key works (but it sounds like you've already found the answer to that ).