Skip to main content

Use Group Policy Preferences to Disable the Windows 8 Initial Logon Animation

By

So in my Windows class this week, I was asked if it is possible to disable the initial logon animation on Windows 8. You know, that one where you have to connect to the Windows App Store and then have to move the mouse around. By some strange coincidence, I actually hade the Windows 8.1 GPO Registry spreadsheet up. I did a quick internet search to find the correct registry setting, but did not find it as a GPO setting.

Next up GPO preferences. Normally I would throw PowerShell into the mix, but this is one of those cases where I feel that a GPO is the better choice. You see, with PowerShell, I would have to contact the computer when it is convenient for both of us. In other words, when I am running the script and the client is online. With a GPO Preference, I make this change and the domain tells the client what to do when the client comes online.

The registry setting is

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

The key is a DWORD of EnableFirstLogonAnimation. A value of zero (0) will disable it and a value of one (1) will enable it.

To set it up, make sure that your clients are in an OU instead of the default computer container. You can apply this GPO setting at the domain level as well. To start, create a GPO or use one that is already scoped to your needs.

Edit the GPO and navigate to Computer Configuration à Preferences à Windows Settings.

Right click Registry and then select New-Registry Item.

Match the settings below and click OK

image

The icon for this setting may appears as if it is an error or warning icon.

image

The yellow triangle actually means that this is an Update operation. An update will perform a Create operation if the key does not exists. Once this policy is applied, your users will not have to wait so long on their first log in.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more