


If,for example, an administrator accidentally walks away from a server console without first logging out, the console will be automatically locked. I will be the first to admit that in some circumstances Windows Server's auto lock feature can improve security. This means that the server will display a lock screen and will require the administrator to enter a password in order to go back to whatever they were doing. If the administrator is determined to be idle for too long, then the operating system is automatically locked. For those who might not have spent a lot of time working with Windows Server 2012 R2, the operating system is configured by default to detect keyboard and mouse input.

I wanted to use one of my posts this month to write about what is, in my humble opinion, Windows Server 2012 R2's most annoying feature: the server's auto lock.
