H
Heinz09
Guest
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
More...
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
More...