Windows Verbose Status

Windows Verbose Status

By default, Windows servers display lots of details when you logon to them and rarely leave you wondering what it’s doing. A while back I ran into an issue that was causing 15 minute login times when a user would log in to the computer for the first time. This was particularly a problem with shared systems like meeting room computers as many users may have never logged into that computer before. The problem scales with the more meeting rooms you have and the more users you have, and typically people are rushing for meetings and don’t have time to wait for a long Windows login process.

From the user’s perspective, it looks like the computer would just sit at Welcome for 15 minutes. Yes, you can go dig into the event logs and see what’s causing that or you could make it so the computer can output what it’s doing, making it so the users can provide you with more useful information.

To do this you need to enable verbose statuses. This is enabled by default on Windows servers but not regular Windows devices. When a regular Windows device logins in and sits at the Welcome message it is doing stuff but not telling you what it’s doing.

In this post, I will detail step-by-step how to enable the Windows verbose login status with a GPO or Intune.

The Process

GPO

Intune

I like to use some of my dynamic device groups for this. You can read more about the dynamic device groups I like to use in my post called Intune Dynamic Device Groups

Now the computer will tell you what it’s doing when it’s booting or shutting down or a user logs on or off.

By enabling this you allow your users to provide you with better information to help you troubleshoot issues faster. Having verbose login enabled for all devices has saved me countless hours of troubleshooting as the information from the users is way more informative and gives me a head start in solving the problem.

My 15 minute login problem was due to printer GPO not applying correctly.

Exit mobile version