Win 7 PC uses RDP to login to a TS but then immediately logs out

Hello,

I have a user who is trying to connect to a new terminal server running Windows 2008 R2 via RDP but is having issues. The client side is using Win 7 Pro fully patched (minus this weeks patch Tuesday). The last terminal server that this user connected to was Win 2003 and needed to be shut down due to legacy status. We have multiple users that have had to switch to this new server and this is the one client that is experiencing this issue.

The user opens Remote Desktop and logs on to the terminal server and a compliance agreement displays. They hit OK and it starts to load the user's profile and prepare the user's desktop. The default blue remote desktop background shows but then the "logging off" message appears and logs the user off. I checked the TS server's event logs and there is no indication or error, just a successful login then an immediate successful logout on the Security log and no errors on the Application or System logs.

I am assuming there is some sort of setting I am missing on the client side since no other remote user on our network is having troubles. I have tried RDPing to the same TS server using the same user's creds with a different PC on the same network with no issue. Any chance someone can point me in the right direction of the setting causing this problem? I greatly appreciate any help. Thanks!

Tried running the RDP client as admin yet?

You can try a clean startup in case it is an app on the offending client somehow interfering - Troubleshoot Application Conflicts by Performing a Clean Startup

GokAy said:

Tried running the RDP client as admin yet?

You can try a clean startup in case it is an app on the offending client somehow interfering - Troubleshoot Application Conflicts by Performing a Clean Startup

No I have not tried that. I'll give it a shot. I may also wipe out the user's profile and create a new one but I doubt that would probably do anything.

Did you try running normally after that? It may have been a one time thing when credentials wasn't enough to change a registry setting or some such.

Yes I did and it did the same thing (I haven't given the user local admin rights yet). I am trying to use PowerBroker or some other method to see if I can bypass having to give local admin rights for this person login.

I had compared User Rights with someone who hadn't had any problems and they were the same. It's a real head scratcher.

There may be a rights issue in the registry, perhaps the user can not read a key or two relating to RDP with his/her own account. If you can find RDP related sections, you can add the user as full control in registry. Of course this would be easy if there was a way to reset registry permissions.

Also you can try adding the user as a Power User first, maybe it will suffice. I would rather re-install (hopefully you got a backup image?) and setup the user account, then giving admin rights of any kind

GokAy said:

There may be a rights issue in the registry, perhaps the user can not read a key or two relating to RDP with his/her own account. If you can find RDP related sections, you can add the user as full control in registry. Of course this would be easy if there was a way to reset registry permissions.

Also you can try adding the user as a Power User first, maybe it will suffice. I would rather re-install (hopefully you got a backup image?) and setup the user account, then giving admin rights of any kind

Well it's even worse than I thought. I tried giving her local admin right and that didn't work!?!?! I actually had to enter in my admin creds to the remote machine for her to use it which I absolutely don't want to do. So I unmarked this being solved.

I'm starting to think about going down the wipe and reinstall path. The thing that is boggling me is that every one of the remote users who is using the same TS is having no issue and they all have the same user rights from what I can tell.

From what I can tell the only real related key to RDP in the registry is only to change the port number. I don't think there is anything else.

You could try checking Remote Desktop related settings in group policy for the computer (since user can log on ok from other PCs, supposed to be this PC that has a problem?). Run rsop.msc on the PC for effective GP settings. Comp Conf - Administrative - Windows Components - Remote Desktop Services

There are RDP related entries in registry by the way, licensing for example. https://support.microsoft.com/en-us/kb/187614, the manual method should work. Make sure you create a manual System Restore point before deleting any keys there may be.

Edit; There is a section in GP under User Conf too, doesn't hurt to check it too (although I think it is Comp issue)