Skip to main content

Logon Scripts in Group Policy not running

Problem 

Was having difficulty with a logon script I had created and was deploying to users via Group Policy.

The script was to customise printer settings for certain users.

But it just wasn't running when the users would logon to their PCs.

The GPO was applying properly, and I could run the script manually without issue.

Cause

It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC.

Solution

This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay.

Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply.

I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay.

So I set it to "1" (1 minute) and it worked nicely.

I must also note that during the troubleshooting process, I read many recommendations to enable the "Always wait for the network at computer startup and logon" policy.  I already had this policy enabled, along with the "Specify startup policy processing wait time" policy - these may also have helped the logon script run properly.



Comments

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

McAfee does my head in

I’ve said it before and I’ll say it again: to all intents and purposes installing McAfee Anti-virus software is pretty much as bad as getting a virus.  There, I said it.  Again. I’ve lost count of how many problems I’ve had with customer PCs over the years where the root of the problem was McAfee in one or another of its hideous incarnations.  But here’s one that’s fresh in my head because I’ve only just sorted it out… A customer had a PC that wouldn’t connect to the iTunes Store in iTunes.  He could do everything else with iTunes, just not connect to the store.  Actually, now I think of it he probably wouldn’t have been able to use the internet radio stations in iTunes either.  He could access the internet and send/receive emails just fine.  iTunes just refused to play ball.  When I ran the Diagnostics in iTunes I got an error –3221. Well what could cause this?  Probably a firewall I thought.  The customer had McAfee Security Center with VirusScan and Personal Firewall.  They also

APC PowerChute Network Shutdown - Authentication Phrase

​Was installing  APC PowerChute Network Shutdown (PCNS) on a customer’s server and couldn’t find a record of the Authentication Passphrase that I set ages back on their Smart UPSes Network Management 2 Card. So I went to reset it on the card and start anew… it took a lot of digging to find it on their particular release of firmware: Go into the UPS tab, then into “shutdown” inside the “Configuration” category: You may then need to change the passphrase being used on other servers. To do this, open up PCNS in your browser and click into the area shown below: