windows server 2012 remote desktop lock out attempts

That way, an administrator who is waiting for a patch to install or waiting for a utility to finish running can monitor the operation's progress without having to unlock the console every few minutes. So how about a compromise? An optional transparent lock screen would be far less disruptive. Auto lock isn't a bad idea, but it is disruptive. For instance, you might disable the auto lock mechanism for just long enough to troubleshoot a problem, and then re-enable the mechanism.īefore I show you how to disable the auto lock mechanism, I just want to quickly give Microsoft a suggestion. Another option might be to disable the lock on a temporary basis. You can permanently disable this mechanism, or you can just adjust it to give yourself a bit more time before the console locks.

Thankfully, there is a way to disable the auto lock mechanism. The lock screen may, for example, engage while I am waiting for a PowerShell command to complete or waiting for an update to install. I have run into similar issues while troubleshooting problems on production servers. This can be especially true when you are working on multiple servers at the same time. There is nothing more annoying than to have to enter a password every time that you stop to check the documentation for the lab setup that you are building. Servers in lab environments tend to get much more hands-on use than production servers, and the automatic lock can be especially disruptive. This is especially true of lab environments. The problem with the auto lock feature is that it really tends to get in the way in certain situations. Of course in production environments, administrators often rely on management tools that are installed on the desktop rather than logging directly into the server console, but I digress. 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.

Windows server 2012 remote desktop lock out attempts