
close
close
Working on Windows Server 2012 R2-based computers is a nice experience. The OS is far more stable than anything we’ve known so far — it’s fast, responsive, and if you can teach yourself to ignore the semi-Windows 8 interface, it also has a really good user experience.
I’ve been building and maintaining hundreds of Windows Server 2012 R2 virtual machines in many customized labs that I use for training and testing purposes. Setting up the machines is much easier than any previous Microsoft operating system, and by using PowerShell to automate the deployment tasks, I can get them all up and running real quickly.
But there’s one small thing that I’ve been personally annoyed with.
After logging onto the OS using either the built-in Administrator’s account or any AD-based user account, I’ll use the system and leave it idle for a few moments to walk away to do something on a different machine, where I’m found with the following message:
Screen lockout message in Windows Server 2012 R2. (Image Credit: Daniel Petri)
Screensaver settings. (Image Credit: Daniel Petri)
Adjusting display settings. (Image Credit: Daniel Petri)
gpupdate /force
Refreshing the GPO. (Image Credit: Daniel Petri)
advertisment
More from Daniel Petri
advertisment
Petri Newsletters
Whether it’s Security or Cloud Computing, we have the know-how for you. Sign up for our newsletters here.
advertisment
More in Windows Server 2012
Most popular on petri
Log in to save content to your profile.
Article saved!
Access saved content from your profile page. View Saved
Join The Conversation
Create a free account today to participate in forum conversations, comment on posts and more.
Copyright ©2019 BWW Media Group