WDS Deployments
You should be at least somewhat familiar
with previous-generation Windows deployment tools, such as RIS, before moving up to
the WAIK and WDS. To review how a typical enterprise might roll out XP desktops in a preVista world, see the Web-exclusive sidebar
“Deploying Windows with RIS,” InstantDoc ID 94191.
WDS is RIS's replacement and is installed
from the WAIK CD or through a download.
After installing WDS, you'll no longer have
access to RIS, although any RIS install images
you previously configured will still be available via the Legacy Images section of the WDS UI.
Like RIS, WDS requires an AD-based network
running DNS and DHCP services, and the
WDS server must have an NTFS partition on
which to store install images. If you've already
installed RIS and configured these items, the
WDS install wizard will let you use the RIS
settings. However, some users will install WDS
“fresh,” in which case they have to install (but
not configure) RIS, install WDS, and then configure WDS during the install process.
Because of the modular nature of Vista,
WDS will install several installation images
when you add the Vista install.wim file to the
WDS image store. On a typical version of Vista,
you'll likely see seven images, each representing one of the available Vista product editions.
These images will be installed into the WDS
Install Images group, which is accessible from
the WDS GUI.
Using the tools and techniques described
earlier, you can create custom install images
with custom answer files, store them in WDS,
then deploy them to clients. For the most part,
WDS works similarly to RIS. When you boot
a Preboot Execution Environment (PXE)–
enabled computer on the network, it finds the
WDS server, loads WinPE to boot from RAM,
then processes the answer file, if one exists.
Depending on how automated the install is,
you might have to answer some interactive
setup questions at the beginning of the process
and specify a computer name at the end.
Like RIS, WDS has its limitations. It doesn't
support decent monitoring functionality, making it hard to gauge how well large-scale
deployments have gone. For this reason,
large enterprises will still want to rely on
high-end deployment tools such as Microsoft
Systems Management Server (SMS), whose
useful deployment features include the ability to install Vista and the Microsoft Office
2007 System simultaneously using Zero Touch
Installation technologies. Microsoft is also
working on a set of Business Desktop Deployment solution accelerators for Vista and Office
2007 that will make rolling out these products
in large environments easier.
Migrating to Vista
Traditionally, it's been best to install new Windows versions on new hardware for a couple of
reasons. First, a new OS tends to introduce hardware and software incompatibilities, and second, the process of upgrading from one version
of Windows to another has generally proven to
be problematic. However, Vista's modular architecture partially eliminates these problems.
When you upgrade an XP PC to Vista, Windows Setup actually performs a clean install of
Vista, then reinstalls applications and user settings to the upgraded system. The result is generally a system that performs as before, but with
the benefits of Vista. (With Win2K, upgrading isn't as easy. Win2K can't be upgraded in-place
to Vista, so you'll need to back up all user documents and data files from the Win2K system
and copy them back to the PC after completing
the upgrade.) Regardless of what Windows version is on your client PCs now, make sure those
systems meet the minimum Vista requirements
before attempting a migration. For a list of those
requirements, go to http://www.winsupersite.com/reviews/winvista.asp.
There are two ways to migrate to Vista.
Small businesses and individuals can use the
Windows Easy Transfer tool and an optional
Easy Transfer Cable to move user accounts,
files and folders, program settings, Internet
settings and favorites, and email settings from
an existing Windows PC to a new PC running
Vista. Or, you can capture this information
from a client PC, put it on a recordable DVD,
network share, or removable hard disk drive,
install Vista interactively or using any of the
methods described above, and then use the
Windows Easy Transfer tool again to copy
everything back to Vista.
Enterprises and large businesses need a
more scalable approach. For them, the WAIK
provides a new version of User State Migration
Tool (USMT) to help migrate user files and settings during large Windows deployments.
Final Thoughts
Microsoft has bestowed Vista with major new
versions of its software deployment tools. To
those familiar with today's Windows deployment tools, the new WAIK, WDS, and USMT
will seem familiar, yet more powerful. Those
who have never before deployed Windows
can rejoice: Vista is simpler to deploy than any
earlier version of Windows.
End of Article
Prev. page
1
2
[3]
next page -->
