Group Policy logon scripts are delayed by 5 minutes in Windows 8.1 - by design

[JSchlackman]

This was briefly hinted at in the summer in a post about new group policy settings in Windows 8.1, but when I saw a post today spelling out what it actually meant, I was pretty surprised:

 

Warning!!!--Group Policy Logon Scripts Delays in Windows 8.1 - Group Policy Software - SDM Software | Group Policy Management & Administration Tools

 

If you are using Group Policy-based logon scripts today to map drives or printers, set up registry or environment variables, etc., when you migrate your client machines to Windows 8.1, those logon scripts won’t run until FIVE MINUTES after logon has started. For some users, this could mean broken environments as processes or environmental setup steps that are expected to kick off at logon don’t.

 

That's the default value; luckily the aforementioned GP setting allows you to override that:

 

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

 

[FN-GM]

noticed it myself. caused some confusion for a while

[Michael]

The question is, why have Microsoft done this? Where's the logic?

[PotNoodleTech]

Maybe their trying to give people the hint that logon scripts are archaic.

 

Or maybe their just silly MS.

[Quackers]

I don't see the reasoning behind this as the only place running logon scripts will be the people running the Pro/Enterprise version of 8.1 and the logon script will be there for a reason.