What are some of the best answer file settings for a WDS Deployment?

Posted by drpcken on Server Fault See other posts from Server Fault or by drpcken
Published on 2011-03-05T14:57:13Z Indexed on 2011/03/05 15:26 UTC
Read the original article Hit count: 304

I've had my head buried in answer files for days now and have gotten quite comfortable setting them up, test, etc...

I use a handful of Components to help my migrations, for my unattend.xml I like:

  • Windows-International-Core-WinPE --> this is good for setting Locales the preboot environment (en-us for us english US speakers). Keeps me from having to set these on the initial image boot.

  • Windows-Setup_neutral --> I like the WindowsDeploymentServices -> ImageSelection, especially if I'm only pushing a single image. This keeps me from having to select it each time.

My OOBE_Unattend.xml is really useful and I barely have to touch anything during this part of the installation:

  • Windows-Shell-Setup_neutral --> This lets me put a ProductKey in for my MAK volume license (very useful and time saving). I can also set the TimeZone for the installation.

  • Windows UnattendedJoin_neutral --> I couldn't live without this component. It joins the machine on my domain before logging in as a domain administrator. I would hate to not have this ability.

  • Windows-International-Core --> Again this component really speeds up the OOBE process. I configure my locals and time zone so I don't have to do it by hand when the machine enteres OOBE.

  • Windows-Shell-Setup --> Allows you to configure an autologon when the new machine is finished. I like to logon as a domain admin automatically for customizing and troubleshooting the new machine immediately after it is imaged. Also the OOBE component under here lets me skip the EULA, Hide Wireless Setup, and set my default NetworkLocation. All of this makes the entire OOBE totally automated.

What are some other good components I am missing as far as helping me get these images pushed and configured as quickly as possible?

© Server Fault or respective owner

Related posts about windows-server-2008

Related posts about deployment