i have been playing with WDS for the last month or so but only where we have time. We are currently using FOG to build machines. Anyway.....at the moment i am more than happy to use an install.wim from a W7 disc to image with as all SW is packaged and pushed.
i have created a WDSunattend.xml file (applied to server) which works fine and the initial stage of a build is great. picks image, credentials language and disc etc. No problems.
I have also worked out the drivers pool and assigning them to images. (Tested last night at silly o clock). WORKS GREAT.
However, i cannot get the image to automate anything once its finished the initial copying files expanding files and installing driver bit.
ive set the naming convention on the WDS console. have a basic imageunattend.xml (at the image) but it will not do anything. i need it to rename and join to the domain. Ive also set up the container to place machines to in AD.
the frustrating thing is i have done this once before about 4 months ago and now completely forgot!
You need to seperate your unattend into 2 files, one unattend with just the Windows PE phase stuff and one which deals with the rest. In wds, you right click on the server and under client you attache the unattend which deals with the Windows PE stuff and then on the install image you right click, properties and add the unattend which deals with the rest of it.
yeah thats done. i have a wdsunattend at the server. which deals with image selection and everything fine. But the image unattend which is applied to the image will not take. i know its reading it as it is adding an additional local account and setting the res.See the attached.. But no domain join. or rename ( the naming is applied on the console)...
Can you post up like a bit of a generic xml. Im real stuck on this one coz it seems like the one i have (a copy of one chopped up from tinternet) isnt very good. i need to be rolling images out monday! eek.
The below part of the xml file. is there a reason the accounts are needed. Do they relate to the domain join. Or does it create accounts? Also with plain text on the password set to false. does the value need to be changed? Sorry im more of a Cisco and apple person. so am a little green to WDS.
Hi everyone.. i still a little stuck on this file. Can some one help me out with the <cpifflineImage cpi:source="catalog://apps01/reminst/images/operating systems/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
Our unattend files are attatched. This does the domain join in unsecure mode, which is actually the securest method for joining the domain, good old Microsoft!
Activation is best done through KMS rather than MAK key, remember though that until the KMS count gets to 25 your machines won't activate.
Using the unattend files I posted, if the machine already exists in AD with it's network GUID set, then it will join as that machine. For machines without the GUID set, we have 'Require Administrator Approval' set in PXE Response Policy on the wds server and we can then set the machine name through the WDS console before the boot proceeds. You need to set an OU for wds to dump the machines into, then you just move them to the correct OU afterwards.
thank you teejay. Can i place <Display>
in that file to alter the display under the component? or will thank fail.
Really is no need to set it, Windows 7 will automatically use the best resolution and colour depth for the monitor and graphics card. I've found it's best to leave as much out as possible in the unattend and just let WIndows 7 get on with it ;-)
ok will do. just testing the one you sent me now. Also i had to change th following, does it look ok? <cpifflineImage cpi:source=wim://cpi-srv1/reminst/images/Windows7/install.wim" xmlns:cpi="urn:schemas-microsoft-com:cpi" />