asked on

How are startup scripts handled in SBS 2008

Hello,

I have a SBS 2008 network that was migrated from SBS 2003. When the domain computers boot, it takes a long time because it stalls for several minutes on "Running startup scripts." This takes place prior to logging in. This isn't a login script. None of my GPO's are enforced but all of them are enabled. In my mind, if they aren't enforced, then any startup scripts within them shouldn't run. So where is this startup script coming from. Where are they stored? I don't want any to run, so I'm just going to delete it if only I could find it.

Philip Elder

Group Policy settings are cascaded much in the way CSS operates.

Domain Level
OU1
OU2
OU3
OU10
OU11

If we have a domain level GPO that runs a script at the machine level, then all computers in any of the OUs indicated will run the script.

If we have a GPO tied to OU1 with a script enabled for any computers in OU1 or any nested OUs, then that script will run.

If, however, OU3 has a GPO where the script is not present linked to it, and that GPO is ENFORCED, then the script should not run.

Enforcing a GPO gives policy processing precedent to any settings in that specific GPO and any objects it applies to.

What you are experiencing is to be expected.

Philip

Philip Elder

BTW,
Get the Blue and Green books by Jeremy Moskowitz:
http://gpanswers.com/

His books are an excellent place to learn how to manage Group Policy.

Philip

jennx

ASKER

Thanks. What's the distinction between enabled and enforced? I was surprised that an enabled and unenforced policy ran.

ASKER CERTIFIED SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial