Whilst trying to contact a WDS server from an ESX client machine (though this can happen on a physical machine also). You see the following error,
The network location cannot be reached, For information about network troubleshooting, se Windows Help.
Solution
This is because the WindowsPE image you are using to Capture/Deploy does not have the network drivers for the NIC in the machine you are imaging (At time of writing the VMXnet3 driver is NOT in the standard WindowsPE 3.0 image).
1. Get the drivers for the NIC, if they are the VMware VMXnet 3 drivers, you can find them on any guest machine running the VMware tools, (look in Program filesVMwareVMware ToolsDrivers), copy both the folders as indicated below.
2. If you ARE using WDS you will need to right click your boot images and export them.
3. Once you have the drivers and the images – use THIS PROCESS to inject the drivers into the image.
4. Finally in the WDS Administrative console, delete the boot Images and “Re-import” the ones you have just updated with the new drivers.
Related Articles, References, Credits, or External Links
Before Server 2008 R2 when we needed to inject drivers into our WDS images we had to do it like this.
Now however the process is a lot more elegant! Simply import the drivers into WDS, then inject them into the boot images (Yes the boot images NOT the Windows Images you are deploying!)
Solution
Add Driver Packages to Image is “Greyed out”
If while attempting to add drivers, the option to “Add Driver Packages to Image” is grayed out.
Then you may need to update your boot images from Server 2008/Vista images to 2008 R2/Windows 7 Images. (or from version 6.0.6000 to 6.1.7600).
Related Articles, References, Credits, or External Links
Seen when using WDS on Windows Server 2008 (and 2008 R2). When attempting to PXE boot a client machine, it sucessfully gets an IP address. But it times out at the TFTP stage.
This is a common occurance if the WDS server is also a DNS server. It happens on machines that have had the MS08-037 security update installed. Basically the ports that WDS needs are being reserved for DNS.
Solution
1. On the WDS server > Start > in the search/run box type regedit {enter}.
Saw this last week, while trying to use an unattended file for the roll out of some machines with WDS.
Every time you try and enter a value you get “The network path was not found” error, no combination of file path or UNC path seems to cure the problem.
Solution
This is a “work around” not a fix, essentially it will not accept any value you put into the path without throwing and error. If you close and reopen this page the value you enter has not been accepted.
So we are going to populate the entry by editing the registry, if you go back and view the entry afterwards it will STILL ERROR but the value will say put and the unattended file will work (providing the path you specify is correct of course!)
3. Locate the “Enabled” value and change it from 0 to 1.
4. Below this key you will see there is a key for each “image processor type”. I’m adding a 32 bit (x86) Unattended file so expand that, and set the “FilePath” value to your unattended xml file (Note: the path is from the WDS root directory, keep it simple and put your unattended file in the WDSClientUnattend folder. In this example mines called WDSClientUnattend.xml).
5. Finally restart the “Windows Deployment Services Server” service.
Related Articles, References, Credits, or External Links
Over the last couple of years I’ve done a lot of imaging of School PC’s I don’t know why but they come with a myriad of different drive and partition configurations. Even big vendors like HP and Dell ship their machines with recovery partitions these days.
If you are imaging with WDS this can cause a problem so what I usually want to do is remove all the partitions, create one big one that takes up all the drive, and format it as NTFS.
Solution
Before you begin make sure you are clued up on working with WDS unattended files, run through my instructions here.
The following procedure needs to be added to the WDS Unattended file NOT the unattended file for the image, (again run through KB0000180 if you are unsure.)
1. While editing your Unattended answerfile you need to locate, “Microsoft-Windows-Setup_neutral” and add “DiskConfiguration” to the “1 windowsPE” component.
2. Right click it and add a disk > Set Disk ID = 0 > Set WillWipeDisk = true.
3. Right Click > Create Partition > Set Extend = true > Set Order = 1 > Set Type = Primary.
4. Select Modify Partitions > Set Active = true > Set Extend = false > Set Format = NTFS > Set Label = SYSTEM > Set Letter = C > Set Order = 1 > Set Partition ID = 1.
5. This procedure will add the following to your unattended file.
Related Articles, References, Credits, or External Links
During a large rollout the more things you can automate the better, before you continue though be aware of one thing…
You can only automatically join a client to a domain if it has an auto generated random machine name!*
*Note: This is not 100% true, if you pre-stage the computer objects into Active Directory with the GUID of the machine (you can see this on the screen at pXe boot time, or get it from the BIOS) Then you can auto join the machines and they will come in with the correct name. However, if you have a large number of machines to build, this is more time consuming than simply renaming them after they have been imaged.
Solution
Before you begin make sure you are clued up on working with WDS unattended files, run through my instructions here.
The following procedure needs to be added to the images unattended file NOT the WDS Unattended file, (again run through KB0000180 if you are unsure.)
1. While editing your unattended answerfile you need to locate, “Microsoft-Windows-Shell-Setup_neutral”, add it to pass 4 (Specialize) and set the ComputerName entry to * (an asterisk).
Note: In this section you can also enter to windows product code, and owner details, as well as your time zone.
2. Then locate, “Microsoft-Windows-UnattendedJoin”, add it to pass 4 (Specialize). Set the JoinDomain entry to the name of your domain. Set UnsecureJoin to “true”.
4. This procedure will add the following to your unattended file.
Related Articles, References, Credits, or External Links
Seen when deploying images with WDS, even though you have specified language, and keyboard settings in your answerfile. The system still asks you to set the language and keyboard options. For a couple of machines you might put up with this, but for a few thousand machines it can get quite annoying!
Solution
There is a reason it’s doing this, and it’s because the next thing it asks you to do is authenticate to the WDS server like so;
if there was a problem you might not be able to log in, (because you are using complex passwords like all good sysadmins) and all those ‘special characters’ can be on lots of different keys, with lots of different languages and keyboard layouts.
So to stop it asking for language settings, set the answerfile to auto authenticate to WDS. You do this by adding the ‘Windows Deployment Services‘ sub component, from the ‘Microsoft-Windows-Setup_neutral‘ component. Add it to the ‘1 windowsPE‘ pass and fill in the credentials accordingly.
Note: This is set in the WDS Unattended answerfile, NOT the one for the image you are deploying.
Adding via System Image Manager
Adding to the Answerfile (via XML)
Related Articles, References, Credits, or External Links
In part two we built our reference machine and took an image of it using WDS. Now to automate the deployments we need to create some unattended answer files, these will answer all the questions that the Windows 8 machines will ask while they are building. We will take those files and import them into the WDS server we configured in part one. Finally to make sure everything is working we will deploy Windows 8.
Solution
Download and Install the Windows Assessment and Deployment Kit for Windows 8
1. We used to have the WAIK for Windows 7, now this has been replaced with the ADK. (download link).
2. It’s a MASSIVE download, it will take a long time.
Create a WDS Distribution Share
1. On a drive that has some room (Approx 5GB should be fine,) create a folder.
2. Launch the System Image Manager.
3. In the top left section > Right click ‘Select a Distribution Share’ > Select ‘Create Distribution Share..’
4. Navigate to the folder you created earlier.
5. Now you don’t need to do this next part, but I copy the full contents of the Windows 8 DVD into this folder as well.
6. Like so.
7. Then in the bottom left section > Right click > ‘Select Windows Image..’.
8. Navigate to the Windows 8 Media > Sources Directory > Select ‘install.wim’.
Note: The install.wim MUST match the version you are going to deploy, it’s no good pointing to a Windows 8 Pro image if you are going to deploy Windows 8 Enterprise.
9. Select the version you are going to deploy > OK.
10. This is normal, select yes to create a catalog file. It will take a while, it has to mount the image, interrogate it and create all the components. Now would be a good time to put the kettle on.
Create the Unattended file for WDS (WDSUnattended.xml)
This unattended file will be just for the WDS settings, it will not be applied to the image you are going to deploy. It sets the keyboard and language settings for WDS to use, then it gives the credentials to connect to WDS, and wipes all the partitions from the target machines hard drive. It then repartitions it ready for deployment.
WARNING: As reiterated below, the disk configuration settings below will wipe the target machines drive of ALL partitions, even manufacturers rescue partitions. If you are imaging machines anyway this should not be a problem, but don’t email me to complain of you lose the recovery files for a laptop/PC while you were practicing!
1. Create a new answer file.
2. The components may not start amd64 (if you are deploying x86 images) and some of the numbers might be different on yours. But the main titles of the components will be the same. Locate Microsoft-Windows-Internationa-Core-WinPE.
3. Add it to Pass 1. If you are unfamiliar with SIM, you add a component (or a sub component) to one of the ‘Passes’ in the center, then you can select that component (or sub component) and set the values for its settings in the top right hand section. The SIM builds an XML file in the background which will become the unattended answer file.
4. You will now see this component under pass 1, select it and set the following settings. (These are for my local English Great Britain settings, you may need to change your settings according to your locale).
Wiping the Targets Hard Drive and Partitions with WDS
6. Locate the Microsoft-Windows-Setup component > Disk Configuration sub component.
7. Add to Pass 1.
8. Right click > Insert New Disk.
9. Expand > Disk > Create Partitions > Right click > ‘Insert New CreatePartition’.
10. Select the DISK.
Disk ID = 0 WillWipeDisk = true
11. Select the Partition.
Extend = true Order = 1 Type = Primary
12. Right click ModifyPartition > Insert New ModifyPartition.
13. With the new ModifyPartition selected.
Action = AddlistItem Active = true Extend = false Format = NTFS Label = SYSTEM Letter = C Order = 1 PartitionID = 1
Select Partition to install Image to
1. Locate the WindowsDeploymentService sub component, (also in Microsoft-Windows-Setup).
2. Add to Pass 1.
3. Expand Image Selection > Install To.
Disk ID = 0 PartitionID = 1
4. Expand Login > Credentials.
Domain = {Your domain name i.e. petenetlive.com would be PETENETLIVE). Password = {Of a user with administrative rights – IT WILL GET OBFUSCATED*). Username = {Of a user with administrative rights).
*I used to say ‘encrypted‘, but thats NOT the case, they are simply Base64 encoded.
Attach the Answerfile to the WDS Server
1. Save the file you have just created.
2. Place it in your Remoteinstall folder in the WdsClientUnattend sub folder.
3. Launch the Windows Deployment Services management console > Expand Servers > Right click your server > Properties.
4. Client tab > Tick to enable unattended installation > I’m deploying x64 bit images so next to that option > Browse.
5. Navigate to and select the file you have just created > Open > Apply > OK.
Create the Unattended file for Your Image (OOBEUnattend.xml)
1. Create a new answer file.
2. Locate the Microsoft-Windows-Shell-Setup component.
3. Add to Pass 4.
4. With the component selected.
ComputerName = * CopyProfile = true (Unless you don’t want to copy the profiles from your source image). ProductKey = Your 25 character Windows 8 unlock code Note: Only put in a code of you are deploying with MAK keys or Retail Keys, if you are planning on using KMS leave this option blankRegisteredOrganization = Your business name. RegisteredOwner = Your owners name. ShowWindowsLive = false {now depreciated for Windows 8} TimeZone = GMT Standard Time Note: For other time zones see here
Automatically Join the Domain
1. Locate the Microsoft-Windows-UnattendedJoin component
2. Add to Pass 4.
3. With Identification selected.
JoinDomain = {Your domain name i.e. petenetlive.com would be PETENETLIVE). UnsecureJoin = true
Set the Image Language and Keyboard Settings
4. Locate the Microsoft-Windows-International-Core component.
Set the Local Administrator Password and Add a Local Administrator
Note: The local admin account is disabled by default, so here I’m setting the local admin’s password, and then creating a new local admin user called Sysadmin.
1. Locate the Microsoft-Windows-Shell-Setup component > UserAccounts sub component
2. Add to Pass 7.
3. With AdmnistratorPassword selected set the password value.
4. Right click LocalAccounts > Insert New LoacalAccount.
5. With LocalAccount selected.
Action = AddListItem Description = Sysadmin DisplayName = Sysadmin Group = Administrators Name = Sysadmin
6. Then set the password value.
7. Save the answer file.
8. Save the file as OOBEUnattand.xml
Attach the Answer file to the Windows 8 Image
1. Launch the Windows Deployment Services Management console.
2. Locate the Windows 8 Image you are attaching the answer file to > Right click > Properties.
3. Tick the option ‘Allow image to install in unattended mode’ > Select File > Browse.
4. Select the OOBEUnattend.xml file you created earlier.
5. Note: It makes a copy of the file and stores it elsewhere calling it ImageUnattend.xml (watch out for this if you need to edit the answer file and nothing changes!)
Deploy Your Windows 8 Image.
1. Boot your target machine to the network via pXe > Press F12 to boot from the WDS.
2. Install an Image.
3. Select the image you want to deploy.
4. After the install, the machine should reboot and present you with a domain logon.
5. And your programs and settings will be pre-configured.
Related Articles, References, Credits, or External Links
In part one we built and configured the WDS Server. Now you need to prepare the reference Windows 8 machine so that you can ‘capture’ its image.
Solution
Before you start, make sure that the machine you are imaging has PLENTY of room on one of its local drive(s), because it copies the image locally, before it sends it to WDS.
Place Your Reference Windows 8 Machine in Audit Mode
To put all the software on your reference machine and configure it how you like, the machine needs to be in ‘Audit Mode’ before you start. There are TWO ways to put the machine into audit mode.
Note: While a machine is in audit mode, it will log on automatically as the Administrator, and every time the machine boots sysprep will launch (in anticipation of you needing it).
Option 1: A Newly Built Machine
1. When you have first built the Windows 8 machine, you will see the screen below, Press CTRL+SHIFT+F3, the machine will automatically reboot and enter audit mode.
Option 2: You Are Already in Windows
2. You can also put a Windows 8 machine into audit mode by running the sysprep executable with the /audit switch.
3. Once in Audit mode, install all the program and configure all the settings you want in your master image. When you are happy run the sysprep program, (Or simply reboot, as sysprep launches at every boot when you are in audit mode).
4. Tick the ‘Generalize’ option, select either shutdown or reboot, (If you choose reboot make sure the machine is ready to pXe boot from the network, and the boot order has the NICBEFORE the hard drive, or sysprep will start and rebuild the machine before it’s imaged).
5. Sysprep will run, and shutdown or reboot as requested.
6. When the machine boots press F12 to boot from the WDS server.
7. Note: Now you can see why (in part one) we called the boot image ‘Capture an Image’ and the capture ‘Capture an Image’. Select the capture option.
8. WindowsPE will run at the welcome screen > Next,
Note: If the process fails at this point, usually it’s because the network card driver for this machine IS NOT in the boot image.
9. Select the volume that you want to image, (Note: It will NOT be C: that’s reserved, usually it’s D:) > Give the image a name, this is the name you will see in the WDS console, and when you are imaging the target machines > Enter a comment/description > Next.
10. Browse.
11. Navigate to a local drive, and give the image a name with a .wim extension > Save.
12. Tick the box to upload the image > Supply IP/Name of the WDS server > Connect.
13. Supply credentials to log onto the WDS server > OK.
14. Once authenticated you can select the image group we setup in part one > Next.
15. The image will be created on the reference machine.
You want to deploy the Windows 8 Client Operating System, to a number of clients using WDS. In this part we will configure the WDS Server, then we will move onto taking an image of your reference Windows 8 machine. Finally we will cover taking that image, and deploying it out to many target systems.
Solution
Add the WDS Role
1. From Server Manager (ServerManager.exe) > Local Server.
2. Manage > Add Roles and Features.
3. Next.
4. Next.
5. Next.
6. Select ‘Windows Deployment services’ > Next > It will ask to install some other features let it do so.
7. Next.
8. Next.
9. Accept the default (both roles) > Next.
10. Install.
Configure the WDS Server
11. From the Start menu > Launch the Windows Deployment Services management console.
12. Expand servers > Right click the server name > Configure Server.
13. Read the prerequisites > Next.
14. Next.
15. Select the location where you want to store your images and keep the WDS files.
16. Note: In this case it’s warning me NOT to use the C: drive, as this is just a test server I will accept the warning and leave it as it is. In production environments make sure you are using a different drive/volume.
17. This particular server IS a DHCP server, but we will address the DHCP requirements when we are finished > Next.
18. I’m going to choose ‘Respond to all (known and unknown)’ > Next.
19. WDS should configure and the service SHOULD start.
20. Here we can see the service has not started (the server will have a small stop symbol on it).
21. So I need to manually start the service.
Adding Image Groups and Images
22. Firstly I’m going to create an group that will hold all my Windows 8 Client machine images. Right click Install Images > Add Image Group.
23. Give it a name > OK.
Adding a boot image (To send an image to a remote machine)
24. Now I need to add a boot image, so I can boot my remote clients from the WDS server and use this image to load WindowsPE on them, so they can be imaged. Right click Boot Images > Add Boot Image.
25. You can use either a Windows 8 DVD or a Windows Server 2012 DVD, you will need to navigate to the sources directory, and locate Boot.wim > Open.
26. Next.
27. Rename the image ‘Install an Image’ > Enter a description > Next.
28. Next.
29. The Image will be imported.
30. Finish.
Adding a Capture Image (To take an image from a remote machine)
31. Right click the image we have just added > Create Capture Image.
32. Call this one ‘Capture an Image’ > Give it a description > Save the image (with a .wim extension). Note: It does not matter where you save the image, but I would suggest somewhere in the ‘Remote Install’ folder > Next.
33. The image will be created.
34. Finish
35. Now even through we have created the capture image, we still need to import it. Right click > Add Boot Image.
36. Select the capture image you created earlier > Next.
37. Make sure it’s called ‘Capture and Image’ > Next.
38. Next.
39. Now the capture image will be imported into WDS.
