|
rbennett806 -> RE: CM Install Start up Script interfering with “Setup Windows and ConfigMgr” Task Sequence (10/4/2008 10:56:22 AM)
|
So you've basically got a Startup script trying to install/repair/manage the client during the OSD process? While you could script the computer account object moves (you'll need to wait for things to replicate between your DCs after you move it), it might make more sense to maybe go a different route... If you're using a Startup script, why not code the script to check for a specific file or registry key that you set in your base OS .WIM image? Code it so that if the file/key exists the script doesn't do anything. Then as the last part of your OSD process, have a script remove that file/registry key so that your Startup script will run as expected. Just my two cents...
|
|
|
|