n00dles Posted July 21, 2005 Share Posted July 21, 2005 (edited) I started a new job recently and found there was no standard process in house for doing unattended builds, so I whipped one up ala the script in the attached .txt fileHere's what you need*Windows PE / Bart PE - with script support enabled (i use winpe personally - for just building boxes, you don't need all the other nice stuff that Bart gives you).- with a RAM disk (doesn't have to be big. 1MB would be plenty)- with ScriptPW.dll registered (I have a post somewhere about how to do that. Search!)- with any necessary mass storage and NIC drivers*A distribution share with the following structure - <root> | ----- 2000unattend.txt | | ---- $OEM$ | ------ ADV | | | ---- I386 | ----- STD | ---- I386There is only one variable you need to modify really, if you have that structure, being strDistShare on line #392*2000unattend.txt - an unattend.txt file something like the one attachedTook me about a week to write the bulk of it and then an extra 2 weeks putting the final touches on (it's always like that, ain't it!). It's geared towards 2000, but can easily be modified for 2003. Please don't email for any kind of support - if you don't know vbscript or how to do unattended builds, use google and technet and learn yourself. That's how I did it!Oh and thanks to likuidkewl I think for how to reboot PE... best.hack.ever <edits> Crap I can't get that directory structure to format correctly... I'm sure you can work out what I mean! 2000unattend.txt, $OEM$, STD and ADV all sit directly under the root, then the I386 directories sit underneath STD and ADV.BUILDSOE.txt2000unattend.txt Edited July 21, 2005 by n00dles Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now