Logon scripts do not run for five minutes after a user logs on to a Windows 8.1-based computer

If you are planning to roll out  or you already have Windows 8.1 in your environment and like many others your client end also depend on the various logon scripts applied on the users or computers and please be aware of an interesting fact that with Windows 8.1 MS has implemented a new group policy which delays the execution of the logon script for five minutes after the user logon is completed.  So  after a user logs on to a Windows 8.1-based computer, the logon scripts do not run for five minutes.

The known issues because of this change is that, The resources required by user immediately after logon like map drives or Printer, may not be available up until 5 mins when the script execution is completed.

But why did MS do this ?

That’s a fair question, the reason is that MS correctly ( 🙂 ) believes that in due course of time there is a lot of mal programmed logon script get accumulated or applied on a user account. The resources which the logon script were designed to call , do not even exist in the environment any more. But admins do forget to remove such logon scripts and they result in user logon delay.

So to resolve the user logon delay MS pushed this policy which delays the script execution and the users login just fine.

The Group Policy 

The Group Policy setting is called as “Configure Logon Script Delay” and its found at the following location

 Computer Configuration\Administrative Templates\System\Group Policy

The default value setting for the “Configure Logon Script Delay” policy is Not Configured. However, the default behavior of a Group Policy client is to wait five minutes before it runs logon scripts.

 

If you want the logon scripts to run at user logon without any delay, you should configure the setting to Disabled:

Computer Configuration\Administrative Templates\System\Group Policy: Configure Logon Script Delay ==> Disabled

If you want to change the time that the Group Policy client waits until it runs the logon scripts, you can set the time in minutes:

Computer Configuration\Administrative Templates\System\Group Policy: Configure Logon Script Delay ==> Enabled

Then, in the options section, set minute to the desired value. The maximum value that you can enter is 1,000 minutes.

After you set the policy to Enabled and set the time in minutes, the Group Policy client waits for the specified time before it runs logon scripts at user logon. If you enter the time in minutes as zero (0), the setting is disabled, and the Group Policy client runs the logon scripts at user logon without any delay.

Please feel free to start a new thread at our forum to report any new issue you need help with

The following two tabs change content below.
An automobile enthusiast at heart and computer geek by profession, started my Career with MS in 2005.Left Jobs and started Pledge Technologies (the parent company to Grishbi) back in 2009.We have been providing IT consulting to various Small and Medium businesses across US and UK since then.Our company specialises in Microsoft Server technologies like AD, Exchange, the rest and with numerous Office 365 migrations under our belt, we quite an expert with that too. Whatever we learn in our day to day life, we share it back on Grishbi as a Thank for all the love and support our customers have given us.
%d bloggers like this: