RDP Session does not end when closing Program

Hello,
we have a Windows Server 2008 R2 RDP Server. Users (Win7) are running a Program X from the Server through their RDP client. When the user closes the program, the RDP session logs off the user and the session ends correctly.

Also the program X on the server can launch Microsoft Word through a button. Now when the user runs the program through RDP and then klicks the button to launch Word and then he closes word and then he closes the Program X, the RDP client is not logged off and the session keeps open (with a blank blue screen). So he has to disconnect, instead being logged off.

Does anyone know why this happens and is there a solution to this?
Many thanks
mangojerryAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
A process is still running in the users context or it cannot unload the profile from the registry.
0
mangojerryAuthor Commented:
Ok, and how can I verify this?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you would need to use the following utilties, in an admin session

Process Monitor

http://technet.microsoft.com/en-us/sysinternals/bb896645

Process Explorer

http://technet.microsoft.com/en-us/sysinternals/bb896653

These utilties will show all the process in use, registry, files etc, it would be best running with this troublesome single user and someone running these processes at the console or Admin RDP session, as they can be busy, capture the information and then stop, and view the info.

You should be able to find the process, that's causing the issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Darius GhassemCommented:
Most likely a program issue. If the program launches Word in  the backgroud there could be other process like hanccocka said that are spawned that could be hanging the logoff.
0
mangojerryAuthor Commented:
Very cool tools!!

We found out that Word starts the splwow64.exe process (printer sooler?). When we close Word, it does not close the splwow64.exe, so it stays active. When we close our program X, the driver stays active (still from Word) and RDP cannot log off the user.

Is there a way to prevent this or work around it?
0
Darius GhassemCommented:
0
mangojerryAuthor Commented:
Works like a charm!

Many thanks, great job!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.