Bud180 Posted July 23, 2010 Posted July 23, 2010 Hi Guys, 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! Help. Thanks everyone in advance. My XML file below:imageunatted.txt
teejay Posted July 23, 2010 Posted July 23, 2010 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.
Bud180 Posted July 23, 2010 Author Posted July 23, 2010 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)... Thank you though. =]
teejay Posted July 23, 2010 Posted July 23, 2010 Your unattend file has some stuff in the Windows PE pass though, everything needs to be in the oobe or specialize pass.
Bud180 Posted July 23, 2010 Author Posted July 23, 2010 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. Any help will be much apprechiated.
Gatt Posted July 23, 2010 Posted July 23, 2010 ImageUnattend.zip Hopefully I have attached a copy of my unattend file..
Bud180 Posted July 23, 2010 Author Posted July 23, 2010 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. NgA2ADUAMwByAHAAUABhAHMAcwB3AG8AcgBkAA== false WDS Setup Administrators wdssetup <DomainAccounts> Administrators Domain Admins moorside NgA2ADUAMwByAHAAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA false
Bud180 Posted July 23, 2010 Author Posted July 23, 2010 also guys what is the script with product keys? can they go into the imageunattend.xml? or will i need to run a KMS server?
Bud180 Posted July 26, 2010 Author Posted July 26, 2010 Hi everyone.. i still a little stuck on this file. Can some one help me out with the Line.. im not sure what its for?. does it look right now?
teejay Posted July 26, 2010 Posted July 26, 2010 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.Unattend.zip
Bud180 Posted July 26, 2010 Author Posted July 26, 2010 Thank you. to get the image unattend to take the AD DS naming convention. i have set %machinename% is that right?
teejay Posted July 26, 2010 Posted July 26, 2010 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.
Bud180 Posted July 26, 2010 Author Posted July 26, 2010 thank you teejay. Can i place 16 1024 60 768 in that file to alter the display under the component? or will thank fail.
teejay Posted July 26, 2010 Posted July 26, 2010 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 ;-) 1
Bud180 Posted July 26, 2010 Author Posted July 26, 2010 ok will do. just testing the one you sent me now. Also i had to change th following, does it look ok?
teejay Posted July 26, 2010 Posted July 26, 2010 Sorry, will explain why. What we've found with wds to make it most effective is to keep the image as machine agnostic as possible, so you can use that image on as many machines as possible to keep the maintenance of images down. We currently run with 1 image that covers over 700 machines and 1 extra image to cover one lab that needs some special addons.
teejay Posted July 26, 2010 Posted July 26, 2010 ok will do. just testing the one you sent me now. Also i had to change th following, does it look ok? That line is irrelevant, it's just used for when you are building the unattend file in windows AIK, it's the source of the image AIK gets the components from.
Bud180 Posted July 26, 2010 Author Posted July 26, 2010 Right i have got it to rename and join. works great thanks teejay. the only problem i got is i cannot log in with any accounts???? have placed a administrator reset in the imageunattend. but is saying the account is disabled. also cannot login with 'development\administrator' doesnt seem to take password?? any ideas. attached is my imageunattend ImageUnattend.zip
teejay Posted July 26, 2010 Posted July 26, 2010 Your script creates a local administrator password, but doesn't create or enable the local administrator account. Have you tried logging in with a domain account? Also, try pinging the machine, it may be that the network card drivers aren't installed for W7, but just for the Win PE phase.
Bud180 Posted July 27, 2010 Author Posted July 27, 2010 machine is built and logged on. was a driver issue thank teejay. Im on my way to work now. I have done a slmgr -ipk on the server. and then run the slmgr - ato... but it was with the server key. when i done it with a windows 7 on the 08R2 server is threw its dummy saying it wasnt genuine. is that the correct key to use? i have a W7 KMS key 08R2 kms key and office 2010 KMS key. Also if the kms is working will i see the machine count increase as requests are sent?
teejay Posted July 27, 2010 Posted July 27, 2010 The server KMS key will activate Windows 7, or use one of Configuring KMS Clients For Office 2010 you have to download an upgrade to allow KMS services to handle 2010 office keys. I have no link to it if you haven't got it as it's on our MS Volume Licensing portal.
Bud180 Posted July 27, 2010 Author Posted July 27, 2010 cool well im in the middle of building machines. had a few driver issues. For some reason when i was installing machine yesterday while the unattend wasnt working it installed all drivers. now it doesnt! So ive added the drivers to the console. I done it by adding them from a folder under 'Drivers then assigned them to a group. Is that correct? we shall see i guess. it seemed when i booted in safe mode i couldnt ping or ipconfig... Also does anyone have a line i can place into the xml file to enable the local administrator account. assuming it is already present. Thank you Teejay and everyone for your help! youve been great.
teejay Posted July 27, 2010 Posted July 27, 2010 Yes, that's the correct way to add drivers. Your best bet is to creat a new account and add it to the administrators group, in Windows AIK go to Windows Shell Setup, Local Accounts and you can add it through there to your unattend. Glad to help and that you've got it running.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now