Our department uses group policy with the logon banner policy at the top of the domain. I am unable to block inheritance or circumvent the banner from breaking the OSD process. The during sysprep the system joins the domain and is added to an AD OU. It then reboots for the auto logon process to run the guirunonce but never does until someone clicks "Ok" to acknowledge the logon banner. I've tried startup scripts to remove the banner reg values etc; and nothing works. Anyone got any work arounds?
one thought would be to not add the computer to the domain until your last step. you can easily duplicate the sysprep add to domain with the netdom.exe utility from the Windows XP Support Tools.
so then the computer will not recieve the group policy and the nag window, it will auto login and run your scripts. In the last line of your script run the netdom command to join to the domain and reboot.
I was going to suggest netdom.exe too.
So...I guess that makes two votes for that idea.
We chose to not use a GPO on this and use a scheduled task or custom vuln (can't remember) to set this. The script checks for the presence of our provisioning exe and does not run until it is not in memory (provisioning is over). Very easy to do in Autoit.
the wonders of autoit. life is much easier with it around
*raises hand* - my vote goes to AutoIT too. So wonderful a tool .
- Paul Hoffmann
LANDesk EMEA Technical Lead