At this point we’ve already installed and properly configured Windows Deployment Server on Windows 2003/Windows 2008 (Part I); and we created a full image (programs and features installed) on our Windows Vista and uploaded it to the server (Part II); the only thing missing is creating the answer files that will be used on the images to achieve the full unattended installation of our operating system. Show
For those using Windows Server 2003 SP1, we reviewed that among the requirements for WDS installation there was installing Windows Automated Installation Kit. This kit also gives us an important tool for the unattended files creation, the Windows System Image Manager. So, it’s recommended for any other platform used on WDS to download this kit and install the System Image Manager. This tool it’s not a requirement for creating the unattended files. Installing
WAIK System Image Manager provides us the way to, using the .wim (or .clg) file for an installation, select the components that are necessary within the answer files. This way we can be sure that the answer options selected are used on the right place at the right time:
Adding a .wim or .clg files is not a requirement, but you won’t be able to validate or check the errors on unattended files that is not using an OS image as a reference. For more information, visit the site Windows System Image Manager Technical Reference. We’ll create two files that are necessary for a complete unattended image installation: WDSClientUnattend.xml and AutoUnattend.xml. Note: All of the components that we’ll add here are associated to 32bit images because the installation file selected has that architecture. If we uploaded a 64bit image, you’ll see an answer file with x64 components. WDSClientUnattendDownload WDSClientUnattend.xml example here. This is the first file used by WDS to respond to all the first configurations on the Windows PE: Disk partitions (creating, modifying) and selecting the image from WDS that we are going to install. As you can imagine, all the components that we will add will go on Windows PE cycle:
Here’s an example of all the components and values that can be inserted on the answer file. On the values I have set in here I’m doing the following: – Setup and keyboard language: English To confirm that the answer file has no errors, click on Tools and Validate Answer File. All the errors will be displayed and explained on the lower panel. Once the file is validated click on Save and use the name WDSClientUnattend. This file must be stored inside the folder of installation files created by default: /RemoteInstall/WDSClientUnattend.xml Download AutoUnattend.xml example here. This is the file that we are using to answer all the Vista configurations: Product key, computer name, domain joining, local users and passwords, etc. The components that need to be added are the following: Cycle 4: Specialize
Cycle 7: OobeSystem
Here’s an example of the values selected: – ComputerName: If you set the value “*” on the computer name will be selected randomly (using RegisteredOwner value). To confirm that the answer file has no errors, click on Tools and Validate Answer File. All the errors will be displayed and explained on the lower panel. Once the file is validated click on Save and use the name AutoUnattend. You can locate this answer file on any folder. Note: A good thing about System Image Manager is that for each component that you have here, you can access to the description of it. If you have any doubt on the values that you are placing, take a look to the help file. Associating Unattended FilesNow that we have the both files necessary, all we need is to associate each file to the images we are going to install: 1. Associating WDSClientUnattend.
2. Associating AutoUnattend
And there you go; you have the complete environment to install full and unattended images of Windows Vista. You have to remember that at the moment of booting a client machine, once you’ve selected the WindowsPE image to boot, the complete installation process will not require any user intervention. If you have to select on clients different disk options or partitions, you can deselect the option where you choose the WDSClientUnattend file; with this you’ll get to manually introduce any changes on image selection and disk management. Common Issue on x64 images and WDSI’ve encountered that there are some scenarios that the 64bits images are not available for selection on a deployment, even though you have correctly uploaded to the WDS Server and the client supports x64 architecture. The problem is that when the client connects to the WDS Server (soon after you pressed F12 to boot from the network) it doesn’t notify that it is x64 compatible client. And for the server, the client is just x86 compatible and the rest of the images do not apply for it. To solve it: 1. Open a cmd on the WDS Server 2. Insert WDSUTIL /set-server /architecturediscovery:yes And the next time any client contacts the WDS Server, will first notify about if is x64 compatible. Hope you find this guide useful. Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment (Part
I). Cheers What command would you use to prepare a Windows installation for imaging that will remove the SID and computer name?The Sysprep /generalize command removes unique information from your Windows installation so that you can safely reuse that image on a different computer.
What is the primary program to configure the Windows environment?The Microsoft System Configuration (msconfig) tool is a Microsoft software application used to change configuration settings, such as which software opens with Windows.
What is the name of the server 2016 boot image file?Boot Image.
A special image that enables the computer to boot and begin installing the operating system using the install image. A default boot image, named Boot. wim, is located in the sources folder of the Windows Server installation media.
What does the name of the answer file on a USB drive have to be to perform an automatic installation?Unattended installations do not require administrator intervention. The entire process can be automated using an answer file called Autounattend.
|