Select Page

So here is a potential gotcha that I just ran across recently with Server 2012 R2 and Group Policy Delivered Logon Scripts.

Microsoft Server 2012 R2 has made a few changes in the Group Policy area. This one could impact you, as it did me. In an attempt to spare you from pulling your hair out like me, I’ll explain the issue.

This issue comes into play if you utilize Group Policy to deploy logon scripts, or any script for that matter. Server 2012 R2 has implemented a new setting that I assume was an attempt to save logon time, they also added Group Policy Caching for this matter, which is pretty cool.

However, this NEW setting is called “Configure Logon Script Delay” and it’s default is 5 minutes, unless you change it. This means your Logon script will sit waiting for 5 minutes after the user logon, before it launches. Now maybe your scripts are ok to do this, but most things I put in a Logon script, are indeed intended to be run right at logon. Since more people nowadays are moving away from logon scripts and utilizing Group Policy Preferences, maybe this won’t bother some. But if your still using GPO delivered scripts, you need to take a look at this.

 

As I said, this only affects Logon scripts delivered via GPO. Seen Below…

logonscriptgpo

 

While troubleshooting and pulling your hair out, if you run a gpresult /v  you would see: This script has not yet run…

gpresult

 

The setting is located in the Computer Configuration at:

Computer Configuration\Policies\Administrative Templates\System\Group Policy\Configure Logon Script Delay

scriptdelaygpo

 

And as you see the default un-configured state is set to 5 minute delay…

defaultscriptdelaygpo

 

Just set this to Enabled and 0 minutes for the normal instant processing behavior…

scriptdelaysetting

 

Make sure that the GPO which applies this setting is applied to the computers in the domain, since this is a computer GPO setting.

Has anyone else ran into this new setting?

What are your thoughts?

 

-Mark