Hello,
I'm having an issue with our Terminal Server Cluster.
Recently, we have been getting a ton of corrupt profiles on users on our network (350+ active sessions daily across 8 Terminal Servers) so to combat the issue I have tried by adding the policy that disconnects idle session to 2 hours and then terminates disconnected sessions after 1 hour. It has been working great, except for one small problem.....
When a idle user is disconnected they are unable to reconnect to their session, I have to manually disconnect there session in RDSM for the user to reconnect.
My thinking is that if a idle session is disconnected the user has 1 hour to login back in to maintain there session, but it appears that logical thinking isn't working correctly because users are unable to reconnect to their disconnected sessions.
Does anyone have any suggestions? - I'm thinking I have to change the disconnected session TTL to less than a 5 minutes so that the disconnected session don't become corrupt. There just doesn't seem like a viable option, IMHO, to allow a disconnected session to still live in memory for a user to re-use.
My end game goal is to save resources on a server or at-least auto-save documents or files before a user is disconnected.... but I'm sure that's a dream of most IT professionals....just a dream....