Terminal services will not log out user after they close their session

Hi Everyone,

This is my first time with Remote Desktop Services in Server 2008 R2 and I am having an issue. I am using this terminal server for remote access to Quickbooks Enterprise edition and I have it auto launch on log-in. On exit of the program Terminal Services starts the log-out process then the session hangs at a blue screen (not a BSOD just a blue background). The only way for me to quit the session is to manually kill the session via Remote Desktop Services Manager. I was wondering if anyone has any ideas why this is happening and where to go to find the issue, When I look in Event Viewer nothing jumps out at me.

Thanks for any help!
WindhamSDAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
WindhamSDConnect With a Mentor Author Commented:
So After digging deeper and thought to myself, "hmm why not check the running processes" seems so obvious that I overlooked it. It has a hanging process called QBW32.exe and that's where my problem lies. Thanks for the help and the brain storming! Off to a support call with QB.
0
 
Tony JConnect With a Mentor Lead Technical ArchitectCommented:
I would launch the application from a cmd file to be honest as this will allow other processes the time to run/end gracefully.

Alternatively, you might want to look at publishing the app via RemoteApp (which you'll be licensed for via your RDS CALs).

So the cmd (or bat file if you prefer) would look like this:

"C:\Program Files (x86)\Path to exe\program.exe" and launch that CMD/BAT file at login rather than the program exe.
0
 
WindhamSDAuthor Commented:
I do have it installed using Remote App.. Hmm... That's a good idea to try out the cmd file but I'd like to find the root of the issue. If all else fails I will give that a try.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
WindhamSDAuthor Commented:
So After digging deeper and thought to myself, "hmm why not check the running processes" seems so obvious that I overlooked it. It has a hanging process called QBW32.exe and that's where my problem lies. Thanks for the help and the brain storming! Off to a support call with QB.
0
 
ehrswCommented:
So what the resolution to the QBW32.exe hanging? Don't leave us hanging!
0
 
IMICoderCommented:
Lil dated but also interested in this solution...
There is a preference in QB to 'keep running for faster startup' (uncheck under Edit -> Preferences -> My Preferences) which does kill the QBW32 process, but user (whether disconnect or logoff) still leaves multiple processes running in their RDS session on the server which can only be killed at the server.
0
 
WindhamSDAuthor Commented:
Thanks IMI
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.