Only one GPO with startup script is ran on client

hi,

i'm not sure if i'm posting in correct forum (so many options). feel free move if required.

i have been troubleshooting issue startup scripts (in gpo) , having trouble identifying root cause.

i have couple of gpos (windows 2008r2) have startup script. on xp clients (~20) first startup script first gpo runs (according gpo precedence order). other startup scripts other gpos not run.

the scripts simple batch files; outputting echo %time% , script name file in local disk of clients (the system account has access).

to simplify things, created test ou moved test computer accounts.  i blocked inheritance @ ou, , linked single gpo 2 startup scripts. tried 2 gpos single startup script each.

the result same, startup script1 runs (i see time , script name in log).

if change order of scripts within gpo (script2, script1) or order of gpos (precedence gpo2, gpo1), script2 runs, not script1.

on client tried gpresult /v, /z, rsop.msc, userenv log, event viewer, etc... see both startup scripts show in rsop, 1 runs.

i tried many settings gpo: disable slow link, asynchronous, wait until scripts end, etc...

also tried applying setting display script name, (i video recorded display @ 20fps , saw script1 popup, not script2).

i tried configuring 2 scripts on local policy (gpedit) of 1 client, , both run.

so it's issue running more 1 script gpo.

>the weird part:

i have 2 clients (also xp, different image). these 2 both startup scripts run!

this indicates gpos not problem, rather client os.

i don't know why. computer objects in same ou (as clients run 1 script), , user account same (not  relevant, testing startup scripts).

> client os sid unique. used psgetsid.exe. images created same way (sysprep). have the group policy preference client side extensions installed.

i tried comparing rsop results, didn't find relevant.

any ideas of how can fix computers running 1 of many gpo startup scripts?

thanks

hi lawrence,

thank suggestions. had tried local startup scripts, , worked.

we found root cause novell zenworks 7 agent.

thanks.

Windows Server  >  Group Policy