Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, December 3, 2019 1:36 PM
We are running Windows Server 2016 Version 1607 on some of our servers and we have some monitoring tools to run, but we need it running for about 3 to 5 days. The problem initially was when the user was idle for too long he would get disconnected.
The GPO settings were changed and you can now stay active on the server as long as your RDP session remains open even if you are idle.
Now I need the session to stay open even after closing the Remote Desktop Client. What is happening is the moment I close it and I log in again (within 60 seconds) all is well. If I do not log in again within 60 seconds everything gets closed and I lose all the data I was monitoring.
The servers were hardened to CIS standards and I disabled the parts that was affecting it.
At the moment these are the changes I made.
\local computer policy\computer configuration\administrative templates\windows components\remote desktop services\remote desktop session host\session time limits
Set time limit for disconnected sessions
Not Configured
=>
enabled
never
End session when time limits are reached
Not Configured
=>
Disabled
All replies (5)
Thursday, December 5, 2019 6:10 AM âś…Answered
Hi,
>>I see the User settings are pulling through but not the Computer settings, I take it then than that the Computer configuration overrides the user configuration. Am I correct in that assumption?
If both the Computer Configuration and the User Configuration policy settings are configured, the Computer Configuration policy settings take precedence.
>>So changes for User gets applied after I log out and computer configuration gets applied after the server reboots?
I've no idea about this but normally I will run command: gpupdate /force to update group policy setting.
/en-us/windows-server/administration/windows-commands/gpupdate
The reason I suggest to check GP result was to ensure that the session time related GPO have been updated successfully.
Thanks,
Jenny
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 4, 2019 6:35 AM
Hi,
1.How did you close the remote session from remote desktop client? Press x should keep session active after closing.
2.How many users were remoting simultaneously? Please try to test with one or two remote sessions.
3.Please take a look at below article, it indicates all the GPO impact the session time.
Configure Timeout and Reconnection Settings for Remote Desktop Services Sessions
4. Please run GP result to check whether the policies have been deployed successfully and right place.
Looking forward to your update.
Thanks,
Jenny
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 4, 2019 7:48 AM
Thank you for the prompt response.
I see the User settings are pulling through but not the Computer settings, I take it then than that the Computer configuration overrides the user configuration. Am I correct in that assumption?
So changes for User gets applied after I log out and computer configuration gets applied after the server reboots?
Thursday, December 5, 2019 6:28 AM
I see running [gpupdate /force] still forces a reboot of the server, this is a production server so I cannot reboot it. It seems that is the time out sessions that are what is causing the problem.
With the next scheduled reboot it should hopefully resolve the issue.
Thank you for the assistance.
Thursday, December 5, 2019 7:52 AM
Hi,
Thanks for your update. Yes, we should always be careful when dealing with production environment.
If any update after next scheduled reboot, please feel free to post with new thread and we provide the assistance in time.
Best Regards,
Jenny
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].