Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

Augusto Alvarez
Blog
Contact

Deploying Windows 7 Using Windows Deployment Services (WDS):

Step-by-Step – Part I
April 20, 2010 at 9:51 am | Posted in Windows 7, Windows Deployment Services (WDS) | 17 Comments
Tags: Windows Deployment Services (WDS), Unattended Files, Windows 7, WDS, Unattended Deployment

See also: Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II

We had a good look about the possibilities about Windows deployment; regarding Windows 7 we’ve
completed a guide using Microsoft Deployment Toolkit 2010 (MDT 2010 beta) to capture and deploy
unattended installations of Windows 7 with Office 2007 (Post I, Post II and Post III). Also we’ve reviewed
how to implement unattended installations of Windows Vista using Windows Deployment Services (Post I,
Post II and Post III).

But we didn’t take a look about deploying Windows 7 using Windows Deployment Services (WDS). Now
we have a good chance to do that, providing a simple step by step procedure.

Why Using WDS?

Deploying operating systems using technologies like Microsoft Deployment Toolkit 2010 or even System
Center Configuration Manager are far more scalable that we can offer using WDS. But there’s always
the cost/benefit analysis we should take before deciding to use always the most scalable and dynamic
technology available.

Having a robust platform for deployment requires, as always, bigger costs for maintain it; and if there’s no
trade off which we can see it in the short term, why bother? Example: We are using one operating system
image as a baseline for our branch office with around 15 users; and we usually have to deploy one
operating system to users per month. Should we need to allocate considerate hardware and efforts to
maintain MDT or SCCM? Probably those technologies will be far more expensive than just using a simple
one or even manual deployments.

Windows Deployment Services is a simple and straight forward technology to achieve fast and
unattended deployments. Just loading a WIM file and the operating system is available over the network.

So, let’s take a look about a simple step-by-step process to achieve unattended deployments of Windows 7
using WDS.

Prerequisites for WDS

Active Directory and DNS server in place. The computer running WDS must be a member of an
Active Directory.
An active DHCP server on the network

1 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

An NTFS partition on the server with the WDS role to store your OS images.
Windows Automated Installation Kit (WAIK). This is an optional component that we can use to
create unattended files.

1. Installing the WDS role on Windows Server 2008

1.1 Installing WDS in Windows Server 2008 is quite simple, just add it as a Server Role from Server
Manager.

Besides the core components in WDS, Windows Server 2008 has the multicasting feature for the
deployment. Transport Server option gives us that functionality.

2 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

1.2 Click on next and then Install.

2. Configure WDS for first use

WDS also has a simple procedure to configure the server, just running a wizard and you’ll be good to go.

2.1 In Administrative tasks open the WDS up in mmc, expand “Servers” then right click on the root name,
and “configure server”.

2.2 We’ll need to create a path for the storing of our images. E:\RemoteInstall.

2.3 PXE answer policy, every time a machine boots from the network you can decide if they are going to
receive an automatic answer or wait for an administrator decision.

3 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

2.4 Uncheck “add images now” select next.

If we have the DHCP server on the same operating system running WDS, we’ll also need to access the
WDS server properties and select on the DHCP tab both options: “Do not listen on port 67” and
“Configure DHCP option 60 to ‘PXEClient’.

In our case the DHCP role is placed on a different server and those options are not checked.

3. Adding Boot and Default Windows 7 Images

Every environment we are trying to deploy will always need boot images; fortunately we just have to
select the boot images included on Windows 7 DVD.

3.1 Right click on “boot images” and select add boot image

4 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

3.2 Using a Windows 7 DVD, we can easily find the boot.wim file in “sources” folder.

3.3 Now we can leave the image name to its default or we can change it.

3.4 Confirm settings then continue.

For adding the Windows 7 operating system image is the same procedure to run, but using the “Install
Images” folder in WDS console.

3.5 Adding the default Install Image Right click on Install Images in the WDS console and select Add
Image.

3.6 Creating a new image group.

5 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

3.7 Browse again in “sources” folder and select install.wim.

3.8 Now we are given a choice of all the available versions of the installation media; install.wim contains
all the versions available of Windows 7.

6 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

We can select just one version to avoid allocating unnecessary space in the hard drive.

Once completed we’ll have available a boot image, plus a default and clean image of Windows 7 to be
installed over the network.

4. Capture Boot Image

There’s an important note regarding boot images; to capture a Windows 7 operating system that you’ve
already deployed, you’ll need to create a new media set of this boot.wim file.

4.1 Add a new boot image, the same procedure shown above. Open up the WDS console and right click on
“boot images” and select “add boot image”.

4.2 Change the name, and description to identify which image is for booting and for capturing; click on
“Finish”.

Once the wizard complete, we’ll see the image added to “Boot images”.

4.3 Now select the image name right click, then select “Create Capture Boot Image”.

5. Install, configure, and Sysprep the reference machine

To deploy a customized image of Windows 7 using WDS we must capture it first from an already deployed
image.

7 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

An operating system by default is not ready to be captured, before doing that we must prepare the image.
Sysprep is the tool in charge of removing all the particular components in an installation (computer name,
SID, OS product key, etc) and makes this image suitable for capturing.

5.1 We can find sysprep tool in “C:\Windows\system32\sysprep”. Running sysprep.exe will pop a simple
GUI, where we can select the options OOBE, Generalize and Reboot after completion.

We can also use the command line: “sysprep /oobe /generalize /reboot”.

Once selected, we’ll see a process running that is going to take a few seconds and the following reboot.

6. Capturing the reference machine

8 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

6.1 After sysprep has rebooted our reference machine, boot from PXE network boot, using F12.

The computer will require for an IP address to the DHCP Server which will redirect it to a Boot Server
available on the network, in this case WDS. After finding it, it will require a second F12 selection.

It is important to note that if we missed this sequence, we should reboot the machine as soon as possible. If
Windows operating system starts, the sysprep clean up performed earlier will be lost and you won’t be
available to capture the image.

6.2 Select “Capture (x64)” and press enter

6.3 After this we’ll see the WDS wizard, select next.

9 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

6.4 Now select the volume to capture, C:\, and create the image name file.

If we don’t see any volume available to capture, is because the sysprep process did not completed
normally and we must run it again.

6.5 Now we will see the screen asking you where to store the WIM file. Select “upload Image to WDS
server”, providing the IP address or FQDN. It will also require domain credentials to access the server.

6.6 Select the Image Group you’ve created to store the image. If you don’t have any group created in
WDS, you’ll receive the error of no group available.

10 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

Now the WDS will create your custom reference image of your client machine.

The process usually takes a while, depending on the operating system characteristics you are capturing.

On the next post we’ll see how to create unattended files with some examples and deploying a this
captured Windows 7 image in a full unattended process.

See also: Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II

Share this:

Possibly related posts: (automatically generated)

Windows Deployment Services now supports multicasts deployments of VHDs

Article: Windows 7 Deployment using WDS by aalvarez82

Ads by Google
WinPE 3.0 Diskless Boot
Deploy Operating Systems To PCs Hands-Free Over Windows PE
www.bootix.com
Window XP Terminal Server
Turn Windows XP into a Full Terminal Server. Instant Setup!
XP.Terminal-Server.com/FreeTrial
2X VirtualDesktopServer
Free & secure application & desktop delivery to any operating system.
www.2x.com/virtualdesktop/
Windows NT/2000/2003/2008
Tools to Administrate,Report,Alert Control, Secure, Deploy & Migrate.
www.pointdev.com/Ideal_Admin

17 Comments »
RSS feed for comments on this post. TrackBack URI

1. [...] See also: Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step –
Part I [...]

Pingback by Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II « Augusto
Alvarez — April 21, 2010 #

Reply

2.
I have a question I do not quite understand. There was a comment up above stating

“There’s an important note regarding boot images; to capture a Windows 7 operating system that
you’ve already deployed, you’ll need to create a new media set of this boot.wim file.”

11 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

What do you mean by creating a new media set of this boot.wim file. I uploaded an image to the
server and brought it back down to the pc made a few changes and reuploaded the file to the server
but it will not allow me to bring it back down. I get an error that says “Windows cannot install
required Files. Make sure all files for installation are available, and restart the installation.”

I am not sure if this has to do with creating a new media set of the boot.wim file and sure I
understand how to do that or what do. Please Help!.

Thanks,

Comment by Todd Kingsley — May 11, 2010 #

Reply

Hello Todd,
The new “media set” for boot.wim is actually the option when you select “Create Capture
Boot Image” in the WDS Console; nothing out of the ordinary.
Regarding the error you mentioned, I think it could be related to a corrupted WIM file, did
you try saving the WIM file locally in the client machine and then upload it to the WDS
manually?
Cheers!
Augusto

Comment by Augusto Alvarez — May 11, 2010 #

Reply

I have not tried to upload it manually. How would I do that? Would I just copy the wim
file on the local computer to the wds server and place it in the images folder or is there a
special process that needs to be done to upload to the server. But on a second note all
my windows xp images are working fine. I have actually reimaged the machine and am
going to try and capture the image again tomorrow. I don’t understand why would I
need to create a new capture boot image if the machine had already been imaged? Is
that causing the issue?

Comment by Todd Kingsley — May 11, 2010 #

3.
Hello Todd,
You don’t need a capture boot image if you already have captured the images.
To upload an image manually you have to move it locally to the server, and using the WDS console
you can select the option “Import Image” and add it from the WIM file.
Hope it helps,
Cheers!
Augusto

Comment by Augusto Alvarez — May 11, 2010 #

Reply

12 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

4. [...] PART-2 After reviewing Post I about installing and configuring Windows Deployment Services,
we’ve also review the process of [...]

Pingback by Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step — May 14, 2010 #

Reply

5.
Hello Augusto,

Thank you for your tips. Very useful! So, now a have a question.
Do you have same experience with migration of users documents and settings?

Comment by Fernanda Soriano — May 20, 2010 #

Reply

Hello Fernanda,
You can migrate profiles using “User State Migration Tool” from Microsoft:
http://technet.microsoft.com/en-us/library/cc722032%28WS.10%29.aspx
You can also achieve the automation of the migration by combining USMT with Microsoft
Deployment Toolkit 2010, where you can migrate profiles, deploy a new operating system and
then automatically import the profile again. Even though I haven’t made any post about
USMT, you can check the MDT 2010 posts I’ve prepared a while ago:
http://blog.augustoalvarez.com.ar/category/microsoft-deployment-toolkit-mdt/
Hope it helps,
Cheers!
Augusto

Comment by Augusto Alvarez — May 20, 2010 #

Reply

6.
So i should choose the boot.wim originally from the source cd or i should create another boot.wim
for the capturing image part.
i’ve tried to choose back the same boot.wim in the source cd, but it just wont goes into the WDS
capturing wizard.

Thank You.

Comment by Frentzen — May 21, 2010 #

Reply

Hello Frentzen,
You have to convert the boot image into a capture boot image.
Take a look to the step 4.3: Now select the image name right click, then select “Create
Capture Boot Image”.

13 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

Cheers!
Augusto

Comment by Augusto Alvarez — May 21, 2010 #

Reply

7.
Hi,
I have created a deployment share and added all the appl,drivers along with OS in MDT 2010.For
that i have created a database and task sequence for the appropriate one.Also am not capturing the
.wim .I am deploying using WDS server throug boot .wim(Network).After installing OS and all
applications but the admin users are not adding to the admin group…kindly give a solution on this..

Mani

Comment by Manivannan — May 27, 2010 #

Reply

8.
Thanks for your guide Augusto.
When I deploy one of these images, it comes down with the user profile that was used to create it.
When I ran Sysprep on XP it always deleted the user profile.
Do you know how I can do it on Windows 7 to ensure that the profile is deleted and the image
comes down “clean”?

Comment by Rob — July 29, 2010 #

Reply

Hello Rob,
You will need to delete the profile folder after you captured the image; you can do this with
IMAGEX tool. You can mount the WIM file into a directory, delete the folder, dis mount the
WIM file and add it again to WDS.
Hope it helps,
Cheers!
Augusto

Comment by Augusto Alvarez — July 29, 2010 #

Reply

9.
Hi Augusto,
Do you have instructions for doing that (mount, IMAGEX etc) or can you point me to some good
ones online?

Comment by Rob — August 4, 2010 #

Reply

14 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

10.
Hi there!

I have been following the instructions for capturing a windows 7 image, however when I get to step
6.6 when I select my image group I can’t click next – it remains greyed out. Do you know why this
could be?
Thanks

Matt

Comment by Matt — August 9, 2010 #

Reply

just solved my issue, had not given a none network location – should pay more attention to
what the window says :$

Comment by Matt — August 9, 2010 #

Reply

11.
hi augusto,

many thanksto that wonderfull and helpfull how-to! what i would recommend you to add is an
“between explanation” how to add drivers to boot.wim so that pc without ethernet card drivers will
boot. of course i found it myself but only by doin “trial and error” – because a lot of websites
explain how to do that with the “dism” command, but i can be done easly with the manager also :-)

but i do have a question too:

i am now building a system with 3 servers. 1st ads, dhcp, dns; 2nd file, print; 3rd wsus, sql and wds.
the last 2 servers are only member servers.
i had no chance to bring up the wds service to run. i did get an different error everytime i tried
something to solve that problem. io even placed the dhcp on the 3rd server but no chance.
now i decided to keep dhcp on the ads/dns/dhcp server and put wds also on it and now it runs
without a problem.
do have an idea what is going wrong in my first wished system?

regards from austria

marty

Comment by Martin Nigg — August 18, 2010 #

Reply

Leave a comment
Name (required)

15 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

E-mail (required)

Website

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <pre> <del
datetime=""> <em> <i> <q cite=""> <strike> <strong>

Notify me of follow-up comments via email.

Send me site updates

About Me
Computer geek, totally fan of the latest's IT platform solutions. Since 2006 I've been
mentioned as Microsoft Student Partner, I continue working with them, collaborating
on different academic and technological events. On this blog, you'll find most of the
experience I have evaluating, designing, implementing and managing those
technologies.

Contact Me
Suggestions? Feedback? Contact? [email protected]

16 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

Subscribe!
Email Subscription

Twitted
rt @VirtualPCGuy RT @4sysops: Why Does Microsoft exhibit at VMworld? http://is.gd
/eBo6G - this is an interesting read. 19 hours ago
impresentable rt @johnnyhalife RT @querman: che @678Oficial me parece que la pifiaste feo
con este twit http://bit.ly/dzAATQ #fibertel 23 hours ago
“ughhh…wait…why…why am I naked?” Hungover Owls http://j.mp/a6ifJT (via
@LaughItUp) 2 days ago

Visitors Map

Recent Posts
Reviewing GFI Backup 2010
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 –
Part I
Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II
Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I
Powering Up WSUS with EminentWare Extension Pack

Category Cloud

17 of 18 25-08-2010 17:46
Deploying Windows 7 Using Windows Deployment Services (WDS): S... http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-us...

Active Directory App-V Books Certifications

DNS Documentation Events Free Stuff GFI WebMonitor Hyper-V ISA
Server Lenovo W500 Microsoft Deployment Toolkit (MDT) SCVMM Team
Foundation Sever Virtualization WAIK
Twitter Uncategorized

Windows 7 Windows Deployment Services

(WDS) Windows Embedded Windows Embedded 2009
Windows Server 2003 Windows Server 2008 Windows
Server 2008 R2 Windows Vista Windows XP Embedded WSUS
Top Posts in Last 24hs
Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II
Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture
customized Windows 7 Images – Part I
Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment
(Part I)
Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture
customized Windows 7 Images – Part III
Implementing App-V - Part II: Choosing and Preparing the Environment

Recent Comments
Charbel Nemnom on Implementing App-V – Par…
Charbel Nemnom on Implementing App-V – Par…
Augusto Alvarez on Implementing App-V – Par…
Charbel Nemnom on Implementing App-V – Par…
Dom on Deploying Windows 7 Using Wind…

Technorati

Blog at WordPress.com. | Theme: Pool by Borja Fernandez.

Entries and comments feeds.

18 of 18 25-08-2010 17:46