![]() The solution is the registry entry needs to be applied locally so the fDenyTSConnections=0 is the default that is used when reprocessing group policy. Every time I changed anything in the local group policy, the RDP session would forcefully disconnect. ![]() ![]() ![]() What's weird is that the solution proposed isn't working for me - mainly because the registry setting they suggest is already set! So it looks like I have to do a bit more digging.I came across the same issue with Win 7. If the local settings are such that you would be denied remote desktop, you'll be disconnected, but can reconnect right away as soon as the GPO processes. To sum up, if you have previously not configured Remote Desktop, or have set RDP to "Deny", and then you set it to "Enabled" with a GPO, then during the Group Policy updates the settings will briefly revert back to the local settings on the machine before being updated to the current Group Policy. I discovered today that I could trigger the disconnect by doing a gpupdate - and doing some digging uncovered this MS page: Well, it looks like I found the culprit of the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |