Is there a way to force the order of at reboot scripts? I have two scripts that run at first boot, one that resets the policy history, and one that runs a firstRun trigger, which runs a few policies that will create an account, install parallels, and a few other things.
However, it appears that the firstRun trigger runs before the clear policy history, so some policies aren't running that need to, and on brand new machines, I don't see any policies getting applied, but the results are there.
Can I force the order, or run the flushPolicyHistory Before casper imaging runs?
On a related note, is there anyway to restart the loginwindow after you create a user, I kill and reopen loginwindow as part of the policy that creates the user, but it doesn't seem to work unless I do it manually after the machines is fully booted.
-Robert