This lets the multiuser computers get the same Group Policy as all of the other computers without forcing the “idle logoff” on every single computer.Ĭreate new GPO in the Group Policy Management Console For multiuser computers, I usually like to create a new sub-Organizational Unit (OU) inside the original OU that contains all the other non-multiuser computers. To set up our solution, we’ll need to create a new Group Policy Object (GPO) in the Group Policy Management Console (GPMC). This session doesn’t work for physical computers that people are using at the console.

You can use it for logging off idle users on Remote Desktop Services (RDS, formerly Terminal Services).

I’ve seen this setting recommended-a LOT-as a solution for logging off idle users. “Set time limit for disconnected sessions” policy (for RDS sessions only) The setting is located in Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits > Set time limit for disconnected sessions. Do you really want to run something this old on your network if you don’t have to? Another is a Group Policy setting that a lot of people point to as a solution to this problem. And, last but not least, getting this old utility to work correctly on newer OSs is just a pain. It also requires you to lengthen your screensaver activation time so you don’t accidentally log off a user who has gone on a break or lunch period. This solution doesn’t take into account newer operating systems that include Fast User Switching. A systems administrator can set the workstation’s screensaver to winexit.scr, and the user would be logged off when the screensaver activated. One solution that used to be popular is the winexit.scr screensaver included in the Windows NT Server 4.0 Resource Kit. Before we get started, I’d like to address two of the ways I’ve seen suggested as a way to handle logging off idle user sessions.

Windows 10 automatic logout