1

Windows Automated Installation Kit (WAIK) User's Guide for Windows Code named Longhorn

Pre-Release Documentation Beta 1 July 21, 2005

Abstract: The Windows Automated Installation Kit (WAIK) is designed to help Original Equipment Manufacturers (OEMs), s stem !uilders, and corporate IT professionals deplo Windows onto new hardware" The WAIK is a new set of deplo ment tools supporting the latest release of Windows" This guide descri!es the current methods, tools, and requirements for deplo ing Windows"

2 This is a preliminar document and ma !e changed su!stantiall prior to final commercial release of the software descri!ed herein" The information contained in this document represents the current #iew of Microsoft $orporation on the issues discussed as of the date of pu!lication" %ecause Microsoft must respond to changing mar&et conditions, it should not !e interpreted to !e a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an information presented after the date of pu!lication" This White 'aper is for informational purposes onl " MI$(O)O*T MAKE) +O WA((A+TIE), E,'(E)), IM'-IE. O( )TAT/TO(0, A) TO T1E I+*O(MATIO+ I+ T1I) .O$/ME+T" $ompl ing with all applica!le cop right laws is the responsi!ilit of the user" Without limiting the rights under cop right, no part of this document ma !e reproduced, stored in or introduced into a retrie#al s stem, or transmitted in an form or ! an means (electronic, mechanical, photocop ing, recording, or otherwise), or for an purpose, without the e2press written permission of Microsoft $orporation" Microsoft ma ha#e patents, patent applications, trademar&s, cop rights, or other intellectual propert rights co#ering su!3ect matter in this document" E2cept as e2pressl pro#ided in an written license agreement from Microsoft, the furnishing of this document does not gi#e ou an license to these patents, trademar&s, cop rights, or other intellectual propert " /nless otherwise noted, the e2ample companies, organi4ations, products, domain names, e5mail addresses, logos, people, places and e#ents depicted herein are fictitious, and no association with an real compan , organi4ation, product, domain name, e5mail address, logo, person, place or e#ent is intended or should !e inferred" 6 7889 Microsoft $orporation" All rights reser#ed" Microsoft, Win:7, Windows, and Windows +T are either registered trademar&s or trademar&s of Microsoft $orporation in the /nited )tates or other countries or regions" The names of actual companies and products mentioned herein ma !e the trademar&s of their respecti#e owners"

Contents
Windows Automated Installation Kit (WAIK) User's Guide.............................................. Microsoft Windows Code-Named "Lon !orn"............................................................. Introduction.............................................................................................................................. An "#er#iew of t!e Windows Automated Installation Kit (WAIK)...................................! New $eatures in t!e Windows Automated Installation Kit (WAIK).................................! Ima in .............................................................................................................................. "# %etu&.................................................................................................................................. "# %etu& Mana er................................................................................................................. "# %'s&re&.............................................................................................................................. "# (Ima e..............................................................................................................................."# )oadma& to Windows Automated Installation.................................................................."" Gettin %tarted................................................................................................................."" Accessi*ilit' $eatures and "&tions......................................................................................"$ Ke'*oard %!ortcuts in +el&..........................................................................................."$ Ke'*oard %!ortcuts in %etu& Mana er........................................................................"% %i,e and $ormat "&tions................................................................................................"& -rintin t!e .ocumentation.................................................................................................."' Windows -reinstallation........................................................................................................."' -!ase /0 -reinstallation -lannin ........................................................................................." -reinstallation Conce&ts........................................................................................................" .e&lo'ment 1erminolo '..............................................................................................." Core 1ec!nolo ies...........................................................................................................$# Ima e-2ased Installation................................................................................................$$ -reinstallation -rocess...........................................................................................................$$ 34am&le .e&lo'ment 3n#ironment..............................................................................$( Automation........................................................................................................................$% -reinstallation Met!ods..........................................................................................................$% A Com&arison of .e&lo'ment Met!ods.......................................................................$% .e&lo'ment Met!ods......................................................................................................$) Ima e-2ased Installation $) Networ5 Installation $' C.-2oot Installation$' +ardware and %oftware )e6uirements...............................................................................$ +ardware )e6uirements.................................................................................................$ %oftware )e6uirements..................................................................................................$ Wal5t!rou !0 2uild an Installation from a Networ5 %!are..............................................$! Wal5t!rou !0 2uild an Installation from t!e -roduct .7...............................................$! -!ase 80 -reinstallation -re&aration...................................................................................(" La* -re&aration.......................................................................................................................($ -re&arin t!e 1ec!nician Com&uter....................................................................................(( Usin Windows -3 for .e&lo'ment......................................................................................(( Usa e 34am&le0 %tandalone .e&lo'ment...................................................................(% Usa e 34am&le0 Networ5 .e&lo'ment........................................................................(% -!ase 90 -reinstallation Customi,ation...............................................................................() Confi ure User %ettin s.........................................................................................................() Confi ure )un"nce Commands...........................................................................................(& -!ase :0 -reinstallation 1estin ...........................................................................................(' -!ase ;0 Ima e Ca&ture and Modification.........................................................................('

Confi uration $ile Creation....................................................................................................( Usin t!e Confi uration $ile...........................................................................................%# Wal5t!rou !0 Ca&ture an Ima e..........................................................................................%# Ca&ture %cenarios............................................................................................................%" Ca&turin an 3ntire Installation %" Ca&turin from a Customi,ed Windows -3 %" Ca&turin an Ima e.........................................................................................................%" %&littin an Ima e............................................................................................................%$ Wal5t!rou !0 Com&ress an Ima e......................................................................................%( Com&ression %cenarios...................................................................................................%% Com&ressin and Ca&turin an 3ntire Installation %% Com&ressin and Ca&turin from a Customi,ed Windows -3 %% Com&ressin an Ima e...................................................................................................%% Ma4imum Com&ression %) $ast Com&ression %) None %& %&littin an Ima e............................................................................................................%& Wal5t!rou !0 Mount and Modif' an Ima e........................................................................%' Installin t!e Windows Ima in $ile %'stem $ilter (WIM $% $ilter) .ri#er ............% Mountin an Ima e..........................................................................................................% Modif'in an Ima e.........................................................................................................%! Unmountin an Ima e....................................................................................................)# -!ase <0 Ima e .e&lo'ment.................................................................................................)" Confi ure .is5 Confi uration................................................................................................)$ Windows Installation usin t!e -roduct .7......................................................................)% Installin Windows from t!e -roduct .7..........................................................................)% Install Windows from t!e -roduct .7. (Networ5)............................................................)) Ima e .e&lo'ment from a Networ5....................................................................................)) Wal5t!rou !0 A&&l' a .e&lo'ment Ima e.........................................................................)& A&&l'in an Ima e usin a Networ5 )etrie#al %cenario..........................................)& A&&l'in an Ima e usin .istri*uted .e&lo'ment to %tandalone Com&uters ....)' A&&l'in an Ima e usin %&lit WIM $iles.....................................................................)' -!ase =0 Ima e Maintenance................................................................................................) Installation 1ec!nolo ies 1ec!nical )eference.................................................................) Windows -roduct Acti#ation.................................................................................................) +ow Acti#ation Wor5s.....................................................................................................)! Acti#ation and -reinstallation........................................................................................&# %etu& 1ec!nical )eference....................................................................................................&# W!at is %etu&>.........................................................................................................................&# 2enefits of %etu&..............................................................................................................&" Common %etu& %cenarios..............................................................................................&$ Clean Installations &$ U& rade Installations &$ .e&endencies of %etu&...................................................................................................&$ 1ec!nolo ies )elated to %etu&......................................................................................&( %etu& Mana er &( %'stem -re&aration 1ool (%'s&re&) &( Unattend?4ml &( Windows .e&lo'ment %er#ices (W.%) &( Windows -reinstallation 3n#ironment (Windows -3) &% (Ima e &%

+ow %etu& Wor5s....................................................................................................................&% %etu& 1erms and .efinitions.........................................................................................&% %etu& Arc!itecture...........................................................................................................&' %etu& Installation Met!ods@ 1'&es@ and -!ases.........................................................&! %etu& Met!ods &! %etu& Installation 1'&es &! -!ases of %etu& '( %etu& Command-Line "&tions..............................................................................................'& (Ima e Command-Line "&tions...................................................................................'& Unattend?4ml %ettin s...........................................................................................................'! %!owUI Attri*ute.............................................................................................................. " 3ntit' )eferences in C!aracter .ata............................................................................ " AUser.ataB...................................................................................................................... " A.is5Confi B................................................................................................................... ( AIma eInstallB................................................................................................................ !# A%ecurit'B........................................................................................................................!$ AAutoLo onB...................................................................................................................!% A)un"nceB......................................................................................................................!' A+ardwareB..................................................................................................................... !! AU& rade.ataB..............................................................................................................."## %etu& Mana er 1ec!nical )eference..................................................................................."#$ W!at is %etu& Mana er>........................................................................................................"#$ 2enefits of %etu& Mana er............................................................................................."#( Common %etu& Mana er %cenarios............................................................................."#( Creatin and Usin t!e Unattend?4ml $ile "#( .e&endencies of %etu& Mana er.................................................................................."#( 1ec!nolo ies )elated to %etu& Mana er....................................................................."#( Unattend?4ml "#( Windows %etu& (%etu&?e4e) "#% +ow %etu& Mana er Wor5s..................................................................................................."#% %etu& Mana er 1erms and .efinitions........................................................................"#% %etu& Mana er Arc!itecture.........................................................................................."#& %etu& Mana er %cenarios..............................................................................................."#' Creatin an Unattend?4ml $ile "#' %'s&re& 1ec!nical )eference..............................................................................................."#' W!at is %'s&re&>....................................................................................................................."#' 2enefits of %'s&re&.........................................................................................................."# Common %'s&re& %cenarios.........................................................................................."# %imilar !ardware confi urations "# )a&id .e&lo'ment "# A&&lication de&lo'ment "# C.-*ase Installations "#! Limitations of %'s&re&...................................................................................................."#! .e&endencies of %'s&re&..............................................................................................."#! 1ec!nolo ies )elated to %'s&re&.................................................................................""# (Ima e ""# Windows -roduct Acti#ation ""# Windows %etu& ""# %etu& Mana er """ Unattend?4ml """

+ow %'s&re& Wor5s................................................................................................................""" %'s&re& Arc!itecture.......................................................................................................""" %'s&re& -rocesses...........................................................................................................""( %'s&re& 1ools and %ettin s...................................................................................................""% %'s&re& 1ools...................................................................................................................""% %etu& Mana er Utilit' (setu&m r?e4e) "") Windows %etu& (setu&?e4e) "") %'s&re& Command-Line "&tions..................................................................................."") (Ima e 1ec!nical )eference................................................................................................""& W!at is (Ima e>...................................................................................................................... ""& 2enefits of (ima e..........................................................................................................""' Common (Ima e %cenarios..........................................................................................."" Creatin an Ima e for )a&id .e&lo'ment "" Modif'in an Ima e $ile "" Limitations of (Ima e....................................................................................................."" .e&endencies of (Ima e................................................................................................""! 1ec!nolo ies )elated to (Ima e..................................................................................""! Windows .e&lo'ment %er#ices (W.%) ""! %'stems Mana ement %er#er (%M%) "&eratin %'stem .e&lo'ment $eature -ac5 "$# +ow (Ima e Wor5s................................................................................................................."$# (Ima e 1erms and .efinitions......................................................................................"$# (Ima e Arc!itecture........................................................................................................"$" (Ima e Command-Line "&tions..........................................................................................."$% 1rou*les!ootin Installation -ro*lems................................................................................"%# -ro*lems wit! Ima e Maintenance......................................................................................"%# +ow do I modif' an e4istin ima e once I !a#e resealed it wit!out acti#atin it> "%# W!' does %'s&re& not wor5 w!en I insert t!e flo&&' dis5 wit! %'s&re&?inf>......"%# W!' does %'s&re& not remo#e a user account t!at was created to &reinstall t!e o&eratin s'stem from t!e C.-)"M>..................................................................."%#

Windows Automated Installation Kit (WAIK) User's Guide

*i+rosoft Windows Code,-amed .Longhorn.
The Windows Automated Installation Kit (WAIK) helps ou to install, customi4e, and deplo the Microsoft Windows code5named ;-onghorn; famil " *or additional support, #isit the .es5to& .e&lo'ment Center at M).+"

Introdu+tion
This section pro#ides an introduction to the Windows Automated Installation Kit (WAIK) Guide, including an o#er#iew, a discussion a!out new features, a roadmap to deplo ing Windows, and general information a!out using this guide"

In this /e+tion
An "#er#iew of t!e Windows Automated Installation Kit (WAIK) New $eatures in t!e Windows Automated Installation Kit (WAIK) )oadma& to Windows Automated Installation New $eatures in t!e Windows Automated Installation Kit (WAIK) Accessi*ilit' $eatures and "&tions 1ec!nical %u&&ort -rintin t!e .ocumentation

An 01er1iew of the Windows Automated Installation Kit (WAIK)

The Windows Automated Installation Kit (WAIK) is designed to help Original Equipment Manufacturers (OEMs), s stem !uilders, and corporate IT professionals deplo Windows onto new hardware" The WAIK is a new set of deplo ment tools supporting the latest release of Windows" This guide descri!es the current methods, tools, and requirements for deplo ing Windows" The goals of this guide are to< Ensure a consistent user e2perience of the core functionalit of the Windows operating s stem" Ena!le ou to !rand and customi4e an Windows product" Ena!le ou to install applications and de#ice dri#ers that are not part of the Windows operating s stem" (educe illegal software pirac " 'ro#ide fle2i!le methodolog and tools to help optimi4e our manufacturing process, whether ou !uild =8 or =8,888 computers per month" This guide includes the following sections< Introduction 5 >eneral information a!out how to use the guide" Windo s Installation 5 .etailed information a!out how to deplo Windows onto new hardware" This section is organi4ed into se#en phases" Installation !ec"nolo#ies !ec"nical Re$erence 5 A comprehensi#e technical discussion of the technologies used in the WAIK"

/ee Also
)oadma& to Windows Automated Installation New $eatures in t!e Windows Automated Installation Kit (WAIK) -rintin t!e .ocumentation

-ew 2eatures in the Windows Automated Installation Kit (WAIK)

Microsoft has completel redesigned the installation technologies for Windows code5named ;-onghorn; to meet OEM and corporate deplo ment requirements" This topic highlights the new features for Windows code5named ;-onghorn; and pro#ides lin&s to the feature sections"

Imaging
Windows code5named ;-onghorn; is deli#ered on the product media in the Windows Imaging ("wim) file5!ased format that is highl compressed to minimi4e the networ& traffic generated when replicating or deplo ing an image" 0ou can install the Windows code5named ;-onghorn; "wim file from the Windows product .?. or create customi4ed images for automated deplo ment" %ecause "wim images are file5!ased, ou can edit our deplo ment images in a non5 destructi#e manner, ma&ing image maintenance easier" 0ou can also store multiple #olume images in a single "wim file"

/etu3
)etup for Windows code5named ;-onghorn; installs the "wim file and uses the new /nattend"2ml answer file, which replaces the set of answer files used in earlier #ersions of Windows" %ecause the image5!ased )etup is faster, ou can use it in high5#olume deplo ments and for automating image maintenance"

/etu3 *anager
)etup Manager is the recommended tool for creating our distri!ution shares, configuration sets, and the /nattend"2ml answer file" It e2poses all configura!le settings in Windows code5named ;-onghorn; and ena!les ou to ma&e and sa#e our customi4ations in /nattend"2ml, including dis& configurations and customi4ations"

/4s3re3
) sprep has a new set of command5line options"

5Image
,Image is the new file5!ased imaging tool for Windows code5named ;-onghorn"; 0ou can use it to capture, modif , and appl file5!ased dis& images for rapid deplo ment" ,Image wor&s with other technologies that use the "wim images, such as )etup for Windows code5named ;-onghorn,; and Windows .eplo ment )er#ices (W.))"

/ee Also
%etu& 1ec!nical )eference Unattend?4ml %ettin s %'s&re& 1ec!nical )eference (Ima e 1ec!nical )eference

10

6oadma3 to Windows Automated Installation

The Windows Automated Installation Kit (WAIK) is designed to help Original Equipment Manufacturers (OEMs), s stem !uilders, and corporate IT professionals deplo Windows onto new computers" The WAIK is a new set of deplo ment tools supporting the latest release of Windows" This guide descri!es the current methods, tools, and requirements for deplo ing Windows" This guide leads ou through se#en installation phases to help ou !uild, deplo , and maintain our Windows installations" P"ase 1< Installation 'lanning P"ase 2< Installation 'reparation P"ase %< Installation $reation and $ustomi4ation P"ase &< Installation Testing P"ase 5< $apturing and Modif ing the Image P"ase '< Image .eployment P"ase (< Image Maintenance Each phase pro#ides specific information a!out what ou need to &now and do !efore proceeding to the ne2t phase" In addition, this guide includes Wal&through, Technical (eference, and Trou!leshooting topics" Wal&through topics pro#ide step5! 5step instructions on how to !uild a specific solution !ased on a series of tas&s" Technical (eference topics pro#ide detailed information a!out the technologies used in the WAIK, including how the technologies wor& and what settings ou can configure"

Getting /tarted
If ou are new to Windows deplo ment, start at the !eginning with 'hase = to learn the !asic concepts and technologies of deplo ment" Once ou understand the concepts and requirements proceed to the ne2t phases in order to the final phase" Throughout this process, use the Wal&through topics to help ou !uild specific solutions" If ou are familiar with pre#ious #ersions of the Windows corporate deplo ment tools, man of the concepts and methods in this guide will !e recogni4a!le" 1owe#er, Windows code5named ;-onghorn@ uses a new Image5!ased )etup and a single answer file (/nattend"2ml)" The new architecture pro#ides more fle2i!ilit in creating and managing multiple images" 'hase = descri!es the new architecture in more detail" 'hase : will descri!e how to !uild the new /nattend"2ml answer file" *or differences !etween this deplo ment guide and pre#ious Windows deplo ment &its, see New $eatures in t!e Windows Automated Installation Kit (WAIK)"

11

0ther 7e3lo4ment 6esour+es

In addition to the WAIK, Microsoft offers a num!er of other complimentar deplo ment solutions" This guide will focus onl on the methods and tools a#aila!le in the WAIK" Other deplo ment resources include< Windo De)loyment *er+ices ,WD*- 5 A suite of components that ena!le the deplo ment of Windows operating s stems, particularl Windows code5named ;-onghorn"; W.) is a redesigned Windows code5named ;-onghorn; #ersion of (emote Installation )er#ices ((I))" W.) consists of two main parts< ser#er5side components and the W.) $lient" *or more information, see Windows .eplo ment )er#ices" .icroso$t *olution Accelerator $or Business Des/to) De)loyment 5 A solution that contains documentation, templates, and technolog files that deli#er an end5to5end solution for efficient planning, !uilding, testing, and deplo ing of Windows and Office 788:"

/ee Also
An "#er#iew of t!e Windows Automated Installation Kit (WAIK) New $eatures in t!e Windows Automated Installation Kit (WAIK) -rintin t!e .ocumentation

A++essi8ilit4 2eatures and 03tions

The Windows Automated Installation Kit (WAIK) User's Guide includes features that ma&e the software accessi!le to a wider range of users, including those who ha#e limited de2terit , low #ision, or other disa!ilities" )ome of the content in this topic ma not !e applica!le to some languages" To e2pand a section, select it, and then press E+TE("

Ke48oard /hort+uts in 9el3

$T(- A TA% E+TE( or (I>1T A((OW E+TE( or -E*T A((OW /' A((OW or .OW+ A((OW 1OME E+. *B To mo#e among the Contents, Index, Search, and Favorites ta!s To e2pand a group of topics To collapse a group of topics To select the pre#ious or ne2t group of topics To select the first group of topics To select the last group of topics To switch !etween the Ta!le of $ontents and the 1elp topic panes

12

TA% or )1I*TATA% E+TE( A-TAO A-TAO, and then press T A-TAO, and then press % A-TAO, and then press * A-TAO, and then press 1 A-TAO, and then press ) A-TAO, and then press ( A-TAO, and then press I A-TAO, and then press ' A-TAO, and then press O A-TA*C $T(-ATA% A-TA$ A-TA+ A-TA) A-TAI E+TE( .OW+ A((OW /' A((OW )1I*TA*=8 /' A((OW or .OW+ A((OW 'A>E /' or 'A>E .OW+ 1OME or E+. $T(-A' $T(-AA $T(-A$

To mo#e forward or !ac&ward from one h perlin& to the ne2t within a topic To perform the action for the selected h perlin& To displa the Options menu To hide or show the pane with the Contents, Index, Search, and Favorites ta!s To displa the pre#iousl #iewed topic To displa the ne2t topic in a pre#iousl displa ed sequence of topics To return to the specified home page To stop the 1elp window from opening a 1elp topic (useful if ou want to stop a We! page from downloading) To refresh the topic (useful if ou ha#e lin&ed to a We! page) To open the Internet Options dialog !o2 for Microsoft Internet E2plorer, where ou can change accessi!ilit settings To print all topics in a !oo& or a selected topic onl To turn search highlighting on or off To close the 1elp window To switch to the ne2t ta! To switch to the Contents ta! To switch to the Index ta! To switch to the Search ta! To switch to the Favorites ta! To open a selected !oo& or 1elp topic To select the ne2t !oo& or 1elp topic To select the pre#ious !oo& or 1elp topic To displa a shortcut menu To scroll toward the !eginning or end of a 1elp topic To scroll toward the !eginning or end of a 1elp topic in large increments To go to the !eginning or end of a 1elp topic To print the current 1elp topic To select the entire 1elp topic To cop the selected items to the $lip!oard

13

Ke48oard /hort+uts in /etu3 *anager

A-T E)$ A-TA*C /' A((OW or .OW+ A((OW To ma&e access &e s #isi!le To cancel )etup Manager To close the )etup Manager window To mo#e among option !uttons in )etup ManagerD or, when a menu or su!menu is open, to select the ne2t or pre#ious command TA% or )1I*TATA% To mo#e forward or !ac&ward to the ne2t option or option group )'A$E%A( To perform the action for the selected !utton or commandD to chec& or clear the selected chec& !o2 $T(-ATA% or To go forward or !ac&ward through the )etup $T(-A)1I*TATA% Manager pages E+TE( To perform the action for the selected !utton or command A-TA)'A$E%A( To displa the window shortcut menu (Control menu) $T(-AE)$ To displa the Start menu Arrow &e s To mo#e !etween options in an open drop5down list, or !etween options in a group of options A-TA the letter underlined in an To select an option, or to select or clear a chec& option !o2 A-TA.OW+ A((OW To open a selected drop5down list E)$ To close a selected drop5down list, or to cancel a command and close a dialog !o2 1OME To mo#e to the !eginning of an entr in a te2t !o2 E+. To mo#e to the end of an entr in a te2t !o2 -E*T A((OW or (I>1T To mo#e one character to the left or right A((OW $T(-A-E*T A((OW To mo#e one word to the left $T(-A(I>1T A((OW To mo#e one word to the right )1I*TA-E*T A((OW To select or cancel one character to the left )1I*TA(I>1T A((OW To select or cancel one character to the right $T(-A)1I*TA-E*T A((OW To select or cancel one word to the left $T(-A)1I*TA(I>1T To select or cancel one word to the right A((OW

14

)1I*TA1OME )1I*TAE+. '(I+T )$(EE+ A-TA'(I+T )$(EE+ $T(-AE or A-TA%A$K)'A$E $T(-A)1I*TA0 $T(-A)1I*TA?

To select from the insertion point to the !eginning of the entr To select from the insertion point to the end of the entr To cop a picture of the screen to the $lip!oard To cop a picture of the selected window to the $lip!oard To undo To cop item To paste item

15

$T(-A, or )1I*TA.E-ETE $T(-A$ or $T(-AI+)E(T $T(-A? or )1I*TAI+)E(T

To cut To cop To paste

/i:e and 2ormat 03tions

0ou can use our own st le sheet to format 1TM- pages in a customi4ed wa " This change will appl to Internet E2plorer and to the Windows OPK User's Guide or an other 1TM- document" !o use your o n style s"eet =" $reate a st le sheet ("css) file that specifies our customi4ed st les, fonts, and formats" 7" In the Windows Automated Installation Kit (WAIK) User's Guide, clic& Options, and then clic& Internet Options" :" On the General ta!, clic& Accessibility" C" )elect the Format documents using my style sheet chec& !o2" 9" $lic& Browse and !rowse to the location of our st le sheet" B" .ou!le5clic& the name of the st le sheet, and then clic& OK"

/ee Also
-rintin t!e .ocumentation

;rinting the 7o+umentation

/sing the rint command of the 1TM- 1elp #iewer, ou can print a single topic or all su!topics of a heading"

;rinting <o3i+s from this 7o+umentation

!o )rint to)ics $rom t"is documentation =" In the Contents ta!, select a topic or heading" 7" On the tool!ar, clic& the rint !utton, and follow the instructions"

/ee Also
Accessi*ilit' $eatures and "&tions

16

Windows ;reinstallation
This section descri!es how to create, deplo , and maintain a Windows installation" The process of Windows installation is di#ided into se#en phases" (e#iew the phases in order !ecause each phase is dependent on the pre#ious phase"

In this /e+tion
-!ase -!ase -!ase -!ase -!ase -!ase -!ase /0 80 90 :0 ;0 <0 =0 -reinstallation -lannin -reinstallation -re&aration -reinstallation Customi,ation -reinstallation 1estin Ima e Ca&ture and Modification Ima e .e&lo'ment Ima e Maintenance

;hase "= ;reinstallation ;lanning

This section pro#ides !ac&ground information a!out Windows deplo ment" /se the topics in this section to help decide which methods !est align with our manufacturing and !usiness goals" The section introduces a series of concepts including terminolog , core technologies, processes, Image5!ased )etup, and deplo ment methods" The concepts pro#ide a foundation for understanding the later sections of this guide" In addition, this section pro#ides Wal&through topics to help ou get started" Wal&through topics are step5! 5step instructions on !uilding a specific solution"

17

In this /e+tion
-reinstallation Conce&ts -reinstallation -rocess -reinstallation Met!ods Wal5t!rou !0 2uild an Installation from t!e -roduct .7. Wal5t!rou !0 2uild an Installation from a Networ5 %!are

;reinstallation Con+e3ts
This section descri!es !asic concepts that ou must understand !efore !uilding an installation, including deplo ment terminolog , core technologies, and image5!ased installation"

7e3lo4ment <erminolog4
These terms are used throughout the Windows Automated Installation Kit (WAIK) User's Guide" Term !ase image .efinition A collection of files and folders (sometimes compressed into one file) captured from a master installation" This image contains additional OEM or corporation configurations and files, in addition to the !ase operating s stem" To manufacture and customi4e a computer according to customer specifications" To manufacture a specified num!er of computers according to a gi#en specification, and then distri!ute the manufactured computers to customers" A file and folder structure that contains the necessar configuration settings that control the installation process and define the manufacturerFs customi4ation information" To manufacture a computer according to customer specifications ! customi4ing a pre5e2isting image of a master installation"

!uild5to5order !uild5to5plan

configuration set

configure5to5order

18

Term destination computer

distri!ution share end user image

master computer master installation original equipment manufacturer (OEM)

technician computer

Microsoft Imaging file ("wim)

.efinition The computer on which ou install Windows that is distri!uted to customers" 0ou can either run Windows )etup on the destination computer or cop a master installation onto a destination computer" A networ& share that stores !ase images for deplo ment" The person who ultimatel recei#es the computer" A collection of files and folders (sometimes compressed into one file) that duplicates the original file and folder structure of an operating s stem" In addition to the !ase operating s stem, an image often contains other files added ! the OEM or corporation, &nown as a !ase image" A full 5assem!led computer containing a master installation" A customi4ed installation of Windows that an OEM or corporation plans to duplicate onto one or more destination computers" A compan that t picall purchases computer components from other manufacturers, uses the components to !uild a personal computer, installs Windows onto that computer, and then sells the computer" /nless e2plicitl stated otherwise, the general term ;OEM; in this guide includes !oth named account OEMs and s stem !uilders" The computer on which ou install )etup Manager" +ormall , the configuration sets and the distri!ution share are also located on the technician computer" The file format for an image captured using ,Image, and is a compressed collection of files and folders"

Core <e+hnologies
The following are core technologies used to deplo Windows operation s stems onto new computers"

19

Technolog Windows )etup

)etup Manager /tilit

Windows 'reinstallation En#ironment (Windows 'E)

) stem 'reparation Tool () sprep) ,Image

/nattend"2ml

.escription Windows )etup is the new program that ena!les ou to install or upgrade to the WindowsG code5 named ;-onghorn; operating s stem" )etup is also the !asis for the following non5interacti#e installation and upgrade methods< unattended installation, Windows .eplo ment )er#ices (W.)), and image5!ased installation with the ) stem 'reparation tool () sprep)" The tool that ena!les ou to create answer files (/nattend"2ml) and distri!ution shares, or to modif the files contained in a configuration set" 0ou use the )etup Manager on the technician computer, and then transfer our /nattend"2ml file to the master computer !efore creating our installation image" Windows 'E is a minimal Windows operating s stem with limited ser#ices, !uilt on the Windows &ernel" It contains the minimal functionalit that ou need to run Windows )etup, install Windows from a networ& share, automate !asic processes, and perform hardware #alidation" A Windows tool that facilitates image creation and prepares an image for deplo ment to multiple destination computers" A Microsoft command5line tool that ena!les Original Equipment Manufacturers (OEMs) and corporations to capture, modif , and appl file5 !ased dis& images for rapid deplo ment" ,Image copies Windows Imaging ("wim) images to a networ&, and can also wor& with other technologies that use "wim images, such as )etup for Windows code5named ;-onghorn,; Windows .eplo ment )er#ices (W.)), and the )M) Operating ) stem *eature .eplo ment 'ac&" An answer file used ! Windows )etup" /nattend"2ml replaces /nattend"t2t and other answer files from pre#ious deplo ment &its"

20

Image,>ased Installation
The term image is used throughout this guide and its definition ma change !ased on its conte2t" It is important to understand the concept of creating and managing preinstallation images" Image5!ased installation is the most efficient deplo ment method in toda Fs high5 #olume manufacturing en#ironment" $reating a !ase image that ou deplo onto new hardware is significantl faster than installing each operating s stem one at a time" Manual installation is time5consuming and can introduce errors and inconsistencies" Image5!ased installation ena!les a consistent, sta!le, and repeata!le manufacturing process, which can help ou sa#e time and mone " Windows code5named ;-onghorn; is now a single, file5!ased image, ma&ing Windows easier and faster to install" /sing a new component5!ased architecture, ou can automate the configuration and installation of Windows through a single answer file (/nattend"2ml)" *or more information a!out how Windows )etup wor&s, see %etu& 1ec!nical )eference"

;reinstallation ;ro+ess
There are man wa s to deplo a Windows operating s stem" 1owe#er, there are se#eral common phases ou will go through in order to deplo Windows" The following process outlines an image5!ased deplo ment scenario" Plannin# 5 .etermine which deplo ment method !est meets our !usiness needs" >ather all the required resources including hardware and software" 0n+ironment *etu) 5 %uild our deplo ment en#ironment" Install the WAIK tools onto a single computer designated as the technician computer" /sing the )etup Manager tool, define our networ& shares and other en#ironment settings" 1reate Ima#e 5 $reate an answer file (/nattend"2ml) ! using )etup Manager" /nattend"2ml is a single file that replaces pre#ious /nattend"t2t and "ini files" Appl the answer file and the Windows product $.H.?. to a master installation" !est 5 Test our new installation" $apture and store the image onto our distri!ution share" De)loy 5 .eplo the image onto a new computer" If necessar , test the image further on the new computer" Deli+er 5 .eli#er the new computer to the customer" .aintenance 5 Modif the !ase image using )etup Manager to include new dri#ers, ser#ice pac&s, and third5part applications"

21

?@am3le 7e3lo4ment ?n1ironment

The following illustrates the creation and deplo ment of an image<

=" Install the O'K tools onto a designated technician computer" /sing )etup Manager, create a configuration set, which specifies manufacturer customi4ations" )tore the configuration set on a networ& share" 7" Assem!le and connect the master computer to the networ& share and !uild the new installation" Test the installation and then run the ) sprep tool to prepare the installation for image capture" :" $apture an image of the new installation and store it on a networ& share" C" Appl the image to new computers on our factor floor" 9" $ustomi4e and test the new computers as necessar " B" (un the ) sprep tool to remo#e user5specific data and then deli#er the new computers to the customers"

22

Automation
This topic will descri!e what parts of the deplo ment process ou can automate"

/ee Also
-reinstallation Conce&ts -reinstallation Met!ods

;reinstallation *ethods
There are man wa s to install Windows" This section descri!es the three supported deplo ment methods< image5!ased, networ& installation, and $.5!oot" E#er manufacturing process has ad#antages and disad#antages" The right choice for ou and our compan depends on factors such as< The num!er and t pe of computers that ou plan to manufacture" Whether our manufacturing model is !uild5to5plan, !uild5to5order, or a com!ination of these models" 1ow much ou customi4e the operating s stem" 1ow much ou automate our processes" The qualit chec&s that ou perform on !oth hardware components and manufactured computers" The e2isting infrastructure of our compan " 0our compan Fs growth rate and !usiness goals"

A Com3arison of 7e3lo4ment *ethods

The following ta!le summari4es and compares the !asic methods, according to three features< *)eed< The time to manufacture and deli#er 2olume< The num!er of manufactured computers 1ustomi3ation< The amount of automated modifications made to the installed software

23

!ethod

Speed

"olume

Customi#ation

Ima#e-Based Installation: .eplo an *ast image of the master installation from a distri!ution share" 0ou can customi4e the image on the *actor floor if necessar " 4et or/ Installation: )tart destination )lowest computers from a !oota!le de#ice (flopp dis&, /ni#ersal *lash .e#ice (/*.)), and run )etup from a distri!ution share" 1D Boot: (un )etup from the destination )low computer using the Windows product .?.D manuall customi4e, audit, and reseal the installation"

1igh

1igh

Medium

1igh

-ow

-ow

7e3lo4ment *ethods
The following section descri!es the general process of each method" 0ou can modif the methods to fit our !usiness needs" Image,>ased Installation This method gi#es ou the most fle2i!ilit in our manufacturing en#ironment, and ena!les ou to duplicate multiple computers quic&l " % creating a !ase image, ou can appl the image onto multiple computers with identical configuration" 0ou can also customi4e the !ase image to meet the requirements of a specific order or a specific customer" This method is also &nown as !uild5to5 plan or !uild5to5order" The !uild5to5plan method is to deplo an image of the master installation without customi4ing the destination computers" The !uild5to5 order method is to deplo an image of the master installation to the destination computers, which are started in *actor mode and customi4ed to order" When ad3usted for our specific manufacturing en#ironment, this method significantl decreases the time required to manufacture each computer" *or e2ample, if ou gi#e our customers a choice from a standardi4ed range of applications, ou can stage man or all of these applications in the master installation" In *actor mode (sysprep -factory), complete the installation of the desired applications, and delete the remaining applications" This method is faster than installing each required application in the factor " Each time ou !uild a computer using this method, ou start from a &nown, tested master installation" When the components change within our manufacturing

24

en#ironment, ou need to test onl those modifications on top of the &nown master installation, significantl reducing the testing time required for !uilding and testing a completel new master installation" This method pro#ides the most comprehensi#e automated solution" /sing #arious implementations of /nattend"2ml, ou can automate all or parts of the entire installation process" 1owe#er, full implementing an automated #ersion of this method does require more preparation time" The !asic process of this method is< =" %uild a master installation with as man customi4ations as necessar , where these customi4ations appl across an entire product line or all the computers that ou manufacture" Thoroughl test this installation" 7" )hut down the operating s stem using the ) stem 'reparation Tool () sprep)" /se sysprep -reseal if the installation is read for deplo ment and deli#er " /se sysprep -factory if ou plan on customi4ing the installation !efore deli#er " :" /se ,Image to capture an image of the master installation, and then store the image on a distri!ution share specified ! the )etup Manager tool" C" Assem!le the hardware for the destination computer" 9" )tart the destination computer with the Windows 'reinstallation En#ironment (Windows 'E) tool" B" $onfigure the hard dis& of the destination computer and duplicate the image of the master installation onto the hard dis&" I" (Optional) If ou ran the sysprep -factory command, customi4e the installation manuall or through automation ! using /nattend"2ml" In this mode, ou can add additional applications and configurations" (un the sysprep -reseal command when ou are done" This method requires that each destination computer ha#e an installed networ& adapter" OEMs or corporations who manufacture or deplo a large num!er of computers ma automate some or all of this process, or !uild a customi4ed #ersion of Windows 'E ! using the tools pro#ided in the WAIK" 0ou can modif this process to duplicate the master installation onto separate hard dis&s, and then later place those hard dis&s into full assem!led computers" -etworA Installation If ou !uild onl a small num!er of computers and it is not cost effecti#e for ou to !uild and manage images of the operating s stem, use the networ& installation

25

method to install and ena!le customi4ations to the destination computers" In this case, the master computer is the destination computer" This method is fle2i!le and eas to maintain" It requires less time to set up an required infrastructure, !ut more time to !uild each computer"

26

The !asic process of this method is< =" /se )etup Manager to create a configuration set on a distri!ution share" 7" Assem!le the hardware for the destination computer" :" )tart the destination computer using Windows 'E" C" $onnect to the networ& and install the Windows operating s stem from the configuration set" 9" To test or customi4e Windows, run the sysprep -factory command" Ma&e our customi4ations in *actor mode" B" (un the sysprep -reseal command (or clic& the Reseal !utton) to shut down the computer" C7,>oot Installation If ou do not want to use a networ& or images in our manufacturing process, use the $. !oot method" %ecause it is completel manual, this is a slow and inefficient method" 1owe#er, for low5#olume !usinesses this method ena!les a high degree of manual customi4ation" 0ou can place an /nattend"2ml file on a flopp dis& to automate !randing in unattended )etup" The !asic process of this method is< =" )tart the computer ! using the Windows product .?." 7" (un )etup to install Windows" :" Ma&e customi4ations and run tests" C" (un the sysprep -reseal command"

/ee Also
-!ase <0 Ima e .e&lo'ment

9ardware and /oftware 6eBuirements

The Windows Automated Installation Kit (WAIK) tools are supported on Windows ,' 'rofessional with )er#ice 'ac& 7 ()'7) and Windows )er#er 788:, )tandard Edition, or Windows )er#er 788:, Enterprise Edition"

9ardware 6eBuirements
Minimum requirements for a technician computer are as follows< A computer with a :885M14 or higher processorD Intel 'entiumH$eleron famil , AM. KBHAthlonH.uron famil , or a compati!le processor (recommended)

27

=7J mega! tes (M%) of (AM or higher (recommended) C8 giga! tes (>%) of hard dis& space" If ou plan to create our own $. images, ou must upgrade to a B85>% hard dri#e" )uper ?>A (J88 2 B88 pi2els) or higher5resolution #ideo adapter and monitor A $.5(OM or .?. dri#e Ke !oard Microsoft Mouse or compati!le pointing de#ice =88 mega!its per second (M!ps) networ& adapter" *or high5#olume deplo ments, use a giga!it Ethernet networ& infrastructure"

/oftware 6eBuirements
To perform a Windows installation and deplo ment, ou will need the following software< Windows ,' 'rofessional with )er#ice 'ac& 7 ()'7) or Windows )er#er 788: with )er#ice 'ac& = ()'=) Windows Automated Installation Kit (WAIK) $.5(OM Microsoft "+ET *ramewor& 7"8

/ee Also
La* -re&aration -re&arin t!e 1ec!nician Com&uter -reinstallation Met!ods -reinstallation -rocess Usin Windows -3 for .e&lo'ment

WalAthrough= >uild an Installation from a -etworA /hare

This wal&through illustrates how to !uild an installation from a networ& share" The process !egins ! creating a master installation using )etup Manager, capturing and storing the image to a distri!ution share, and finall deplo ing the image onto new hardware" This wal&through relies on a simple networ& infrastructure to mo#e files !etween computers"

;rereBuisites
In order to complete this wal&through, ou will need< Windows code5named ;-onghorn; product .?. and manual $ertificate of Authentication ($OA) stic&er

28

Windows Automation Installation Kit, which includes )etup Manager /tilit , ,Image and ) sprep A technician computer, an computer running Windows ,' 'rofessional +etwor& support from technician computer to distri!ution share and master computer 0our )upport Information (required) %randing information (optional) Additional dri#ers for all peripheral de#ices

;ro+edures
This section will descri!e the following procedures< To !uild a la! en#ironment To create an /nattend"2ml answer file To create a master installation To test our application To capture and store an image To deplo the image o#er the networ&

/ee Also
Wal5t!rou !0 2uild an Installation from t!e -roduct .7.

WalAthrough= >uild an Installation from the ;rodu+t 7C7

This wal&through illustrates how to !uild a manual installation ! using the product .?. of Windows code5named ;-onghorn,; this is also &nown as the $.5%oot method" This wal&through does not require a networ&, !ut does require ou to create a flopp dis& to mo#e files from one computer to another" The process !egins with the creation of an answer file (/nattend"2ml) ! using )etup Manager, cop ing the file along with the ) sprep tool to a flopp dis&, and then running )etup for Windows code5named ;-onghorn; with the flopp dis& on the new hardware" The end result is a new installation of Windows"

;rereBuisites
In order to complete this wal&through, ou will need the following items< Windows code5named ;-onghorn; product .?. and /serFs >uide $ertificate of Authentication ($OA) stic&er

29

Windows Automated Installation Kit (WAIK), which includes the )etup Manager /tilit and the ) sprep tool A technician computer, that is, an computer running Windows ,' 'rofessional A flopp dis& to transfer the /nattend"2ml answer file and tools to a new computer 0our support information (required) %randing information (optional) Additional dri#ers for all peripheral de#ices

;ro+edures
!o create an ans er $ile =" Install )etup Manager on our designated technician computer" 7" $reate an /nattend"2ml answer file using )etup Manager ! pro#iding the following information when as&ed<

Customer name@ or ani,ation@ and com&uter name (o&tional) -roduct Ke' (re6uired) .is5 confi uration (o&tional) )un "nce o&tion (o&tional)

30

:" )a#e the /nattend"2ml answer file to a flopp dis&" C" $op *ys)re)5e6e to the flopp dis&, and remo#e the flopp dis& from the computer" !o manually install Windo s on ne "ard are =" Insert the Windows code5named ;-onghorn; product .?. and flopp dis& (from the pre#ious procedure) into a new computer" 7" Turn on the new computer" )etup for Windows code5named ;-onghorn; will start" %ased on the settings that ou selected in our /nattend"2ml file, )etup will prompt ou for more information" :" Once )etup is complete, create a ) sprep director on dri#e $ of the new computer" *or e2ample, $<K) sprep" C" $op ) sprep"e2e to $<K) sprep" 9" (emo#e the product .?. for Windows code5named ;-onghorn; as well as the flopp dis&" B" At a command prompt, t pe *ys)re)5e6e 7reseal" ) sprep will delete installation log files and other user5specific and computer5specific settings and data" The computer will automaticall shut down and will !e read for customer deli#er "

-e@t /te3s
This method is the simplest method for installing Windows onto new hardware" This method is useful when networ& access is not a#aila!le or when ou !uild onl a few computers" 1owe#er, this method pro#ides limited automated customi4ation" *or more information a!out other deplo ment methods, see -reinstallation Met!ods"

/ee Also
-!ase 80 -reinstallation -re&aration -!ase 90 -reinstallation Customi,ation

;hase $= ;reinstallation ;re3aration

This section descri!es what ou must do to create and deplo installations of Windows code5named ;-onghorn"; our customi4ed

In this /e+tion
La* -re&aration -re&arin t!e 1ec!nician Com&uter

31

Usin Windows -3 for .e&lo'ment

6eferen+e
Installation 1ec!nolo ies 1ec!nical )eference

/ee Also
-!ase /0 -reinstallation -lannin -!ase 90 -reinstallation Customi,ation -!ase :0 -reinstallation 1estin

La8 ;re3aration
If ou do not alread ha#e a la!, we recommend that ou esta!lish a dedicated and isolated la! en#ironment to de#elop and test the deplo ment" The la! must mirror the production en#ironment as closel as possi!le to ensure that all aspects of the production en#ironment can !e accounted for in the de#elopment process" *or low5#olume deplo ments, the la! must include< A tec"nician com)uter to "ost t"e 8P9 or WAI9 tools5 It can !e a wor&station, ser#er, or e#en a laptop, and can !e used as a networ& distri!ution share" It can run Windows ,', Windows )er#er 788:, or Windows code5named ;-onghorn"; 1lient or/stations5 An unique t pe of wor&station configuration found in production must !e duplicated in the la!" This ena!les ou to test each hardware configuration" 4et or/ "ubs and cablin#5 Internet access5 The la! (or a portion of the la!) must ha#e access to the Internet for downloading software updates" 1D or D2D burner5 A computer must !e a#aila!le in the la! for creating $.5(OMs or .?.5(OMs" *or high5#olume deplo ments, the la! must include the pre#ious minimum requirements, in addition to the following< A Windo s domain $or t"e com)uters to :oin and to "ost user accounts5 This can !e a MicrosoftG Windows 7888G or MicrosoftG Windows )er#erL 788: domain" 4et or/ s itc"es and cablin#5 *or high5#olume deplo ments, =88 mega!itsHsec (M!Hs) or faster is recommended to accommodate high #olumes of data" D;1P ser+ices5 .1$' ser#ices pro#ide T$'HI' addresses to client computers"

32

D4* ser+ices5 .+) ser#ices pro#ide T$'HI' host name resolution to client and ser#er computers" WI4* ser+ices5 WI+) ser#ices pro#ide +et%IO) name resolution to client and ser#er computers" A build ser+er in t"e domain to "ost t"e build $iles and ima#es5 This can !e a wor&station or ser#er class computer installed with Windows 7888 or a later #ersion of Windows" Although the s stem has no specific dependencies on the !uild computer itself, the computer must ha#e at least 98 giga! tes (>%) of dis& space and some form of !ac&up equipment, such as a tape dri#e or a storage area networ& ()A+)" 9eyboard7+ideo7mouse ,92.- s itc"es5 It can !e helpful to connect the client wor&stations to a K?M switch to minimi4e the floor space required to host the wor&stations"

/ee Also
-!ase :0 -reinstallation 1estin -!ase =0 Ima e Maintenance

;re3aring the <e+hni+ian Com3uter

The technician computer is the computer in our la! on which ou install the OEM 'reinstallation Kit (O'K) or Windows Automated Installation Kit (WAIK)" The technician computer can also !e used as our distri!ution share, or ou can use )etup Manager to create distri!ution shares on other computers on our networ&" The technician computer can !e a wor&station, ser#er, or e#en a laptop" It can !e in a domain !ut that is not required" It can run Windows ,', Windows )er#er 788:, or Windows code5named ;-onghorn"; If running a #ersion of Windows )er#er, it can !e a standalone ser#er, mem!er ser#er, or a domain controller" To prepare the technician computer, install the tools from the Windows O'K or WAIK $." If ou plan to use the technician computer as a distri!ution share, connect it to the la! networ&"

33

/ee Also
La* -re&aration Usin Windows -3 for .e&lo'ment

Using Windows ;? for 7e3lo4ment

Windows 'E is a minimal Windows operating s stem with limited ser#ices, !uilt on the Windows &ernel" It contains the minimal functionalit that ou need to run Windows )etup, install Windows from a networ& share, automate !asic processes, and perform hardware #alidation" Windows 'E was de#eloped specificall to address des&top and ser#er deplo ment scenarios" In the past, M)5.O) !oot dis&s were used for s stem configuration and operating s stem installation" With support for M)5.O) !ecoming more difficult to find, Windows 'E offers a minimal operating s stem that le#erages the dri#ers and !asic features of the Windows operating s stem"

Usage ?@am3le= /tandalone 7e3lo4ment

In a standalone deplo ment scenario, ou create a $. or .?. that contains !oth Windows 'E and the operating s stem to install" 0ou can distri!ute this remo#a!le media to users or to technicians who install or upgrade machines at the remote site" The following is a t pical standalone deplo ment scenario< =" %oot the computer with the Windows 'E $. or .?." )tartnet"cmd loads the appropriate networ& ser#ices, and then passes control to a custom !atch file" The custom !atch file inspects the computer to ensure that it is the correct manufacturer or model to deplo to" If the computer is a #alid destination, a process !ac&s up user data from the computer" %ecause Windows 'E has full +T*) access to the hard dis& dri#e, ou can mo#e the user data to a remote location or to another location in the computer" 7" After creating the partitions, use ,Image or )etup to restore an image to the destination dri#e"

Usage ?@am3le= -etworA 7e3lo4ment

+etwor& deplo ment scenarios are similar to standalone deplo ment scenarios, !ut can include more options" =" %oot the computer into Windows 'E from the Windows 'E $. or .?. or using (emote Installation )er#ices ((I))")tartnet"cmd loads the appropriate networ& ser#ices" 7" Map a dri#e to the local ser#er from which ou will deplo Windows"

34

:" *rom the ser#er, start a custom !atch file to !egin )etup" The custom !atch file inspects the computer to ensure that it is the correct manufacturer or model to deplo to" If the computer is a #alid destination, a process !ac&s up user data from the computer" %ecause Windows 'E has full +T*) access to the hard dis& dri#e, mo#e the user data to a remote location or to another location in the computer" C" After creating the partitions, use ,Image or )etup to restore an image to the destination dri#e"

/ee Also
-re&arin t!e 1ec!nician Com&uter La* -re&aration

;hase (= ;reinstallation Customi:ation

This section will descri!e how to customi4e the end user e2perience ! !uilding the new /nattend"2ml answer file"

Configure User /ettings

This screen ena!les ou to define, in the /nattend"2ml file, what the end user must see and e2perience after starting the computer for the first time, including whether< The end user must accept the -icense Terms for Microsoft )oftware, pre#iousl &nown as the End5/ser -icense Agreement (E/-A)" The end userFs full name must !e pre5entered and whether the related user interface (/I) must appear to the end user for modification" The end userFs organi4ation must !e pre5entered and whether the related /I must appear to the end user for modification" The computerFs name must !e pre5entered and whether the related /I must appear to the end user for modification" The 'roduct Ke must !e pre5entered and whether the related /I must appear to the end user for modification" 4ote The entries and selections that ou ma&e on the $ser Settings screen will appear in the <UserData> element of the /nattend"2ml file"

35

!o con$i#ure user settin#s =" In Setup !anager, clic& Create a new unattend %ile, and then clic& $ser Settings in the left pane"The $ser Settings screen will appear" 4ote 0ou can also open an e2isting /nattend"2ml file for modification, ! clic&ing Open an unattend %ile in the left pane" 7" *rom the &icense 'erms %or !icroso%t So%tware area, select the Accept the &icense 'erms %or !icroso%t So%tware %or the user chec& !o2" If ou do not select the chec& !o2, the user will recei#e and must accept the <icense !erms $or .icroso$t *o$t are message during )etup" :" /nder $ser and Computer In%ormation, ou can modif the following information<
Full (ame) 1'&e t!e full name of t!e end user? 1!e default #alue is Windows User@ and@ if modified@ must not e4ceed <: c!aracters in len t!?

rompt $ser) %elect t!e c!ec5 *o4 to s!ow t!e full name-related UI to t!e end user for modification? If t!is c!ec5 *o4 is cleared@ t!e UI will not a&&ear and t!e end user will not *e a*le to modif' t!e information?

Organi#ation) 1'&e t!e name of t!e or ani,ation? 1!is #alue cannot e4ceed <: c!aracters in len t!?

rompt $ser) %elect t!e c!ec5 *o4 to s!ow t!e or ani,ation-related UI to t!e end user for modification? If t!is c!ec5 *o4 is cleared@ t!e UI will not a&&ear and t!e end user will not *e a*le to modif' t!e information?

Computer (ame) 1'&e t!e name of t!e com&uter? 1!e default #alue is *@ w!ic! ena*les %etu& to enerate a random com&uter name? If c!an ed@ t!e #alue cannot e4ceed /; c!aracters in len t!?

rompt $ser) %elect t!e c!ec5 *o4 to s!ow t!e com&uter namerelated UI to t!e end user for modification? If t!is c!ec5 *o4 is cleared@ t!e UI will not a&&ear and t!e end user will not *e a*le to modif' t!e information?

C" *rom the roduct Key area, ou can enter the 'roduct Ke (also &nown as the serial num!er) for the Windows code5named ;-onghorn; installation .?." The 'roduct Ke consists of fi#e groups of alphanumeric #alues, each separated ! a h phen" *or e2ample, XX123-123XX-YY123-123YY-XYXYX"

/ee Also
Confi ure .is5 Confi uration Confi ure )un"nce Commands W!at is %etu& Mana er>

36

+ow %etu& Mana er Wor5s

Configure 6un0n+e Commands

This screen ena!les ou to define and configure, in the /nattend"2ml file, the commands that automaticall run after Windows Welcome" The *unOnce commands ena!le actions, such as application installation, the running of scripts, and Auto -ogon" 4ote The entries and selections that ou ma&e on the *unOnce Commands screen will appear in the <RunOnce> and <AutoLogon> elements of the /nattend"2ml file" !o con$i#ure Run8nce commands =" *rom Setup !anager, clic& *unOnce Commands in the left pane" The *unOnce Commands screen will appear" 7" $lic& Add" A !lan& field will appear" :" *rom the *unOnce Commands area, enter the following information<
+escription) 1'&e a la*el for 'our command? $or e4am&le@ Net Connect?

Command &ine Argument) 1'&e t!e command s'nta4 to run after Windows Welcome? $or e4am&le@ t'&e NETUSE R:\\Server\Share\Apps@ w!ere R:\\Server\Share\Apps &oints to t!e location of t!e a&&lication on 'our networ5 s!are?

4ote These commands run in the order listed on the screen, from top to !ottom and appear in the Run8nce area of the /nattend"2ml file" /se the $p or +own !utton to modif the order on the screen, if necessar " C" )elect the Auto logon with the %ollowing credential chec& !o2 if a user account can log on to the computer ! using the supplied credentials<
$ser (ame) 1'&e t!e name of t!e user account t!at can automaticall' lo on to t!e com&uter? $or e4am&le@ t'&e Administrator?

assword) 1'&e a &assword for t!e user account? assword

Con%irm assword) )e-t'&e t!e &assword entered in t!e field?

Count ,(ot %or Beta -.) 1'&e a numeric #alue for !ow man' times t!e com&uter attem&ts to lo on *' usin t!e su&&lied credentials *efore it enerates an error?

37

Im)ortant *or %eta =, networ& credentials are stored on the hard dis& in clear te2t" Onl Administrator credentials will wor& at this time, !ecause of the ina!ilit to add user accounts from )etup Manager"

/ee Also
Confi ure User %ettin s Confi ure .is5 Confi uration W!at is %etu& Mana er> +ow %etu& Mana er Wor5s

38

;hase %= ;reinstallation <esting

This section will descri!e how to test our new installation prior to customer deli#er "

;hase )= Image Ca3ture and *odifi+ation

This phase descri!es the process to capture and modif our Windows Imaging ("wim) files using ,Image" ,Image is a command5line tool that uses a set of A'Is, &nown as Windows Imaging A'I (WIM>A'I), to perform man tas&s with the Microsoft Windows Imaging (WIM) files" WIM files contain one or more #olume images for a Windows operating s stem, while a #olume image represents the captured #olume or partition of a Windows operating s stem" The primar purpose of ,Image is to capture, modif , and appl images for deplo ment in a manufacturing or corporate IT en#ironment"

In this /e+tion
Confi uration $ile Creation Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e Wal5t!rou !0 Mount and Modif' an Ima e

6elated /e+tions
Wal5t!rou !0 A&&l' a .e&lo'ment Ima e W!at is (Ima e> +ow (Ima e Wor5s (Ima e Command-Line "&tions

Configuration 2ile Creation

,Image is a command5line tool that ena!les the creation of image files for deplo ment in a manufacturing or corporate IT en#ironment" 0ou can create a con i!"ration#$ist%ini file to determine< Which files and folders must !e e2cluded from the capture process, when ou use the 7ca)ture option" Which folders, files, and file t pes must !e e2cluded from the compression process, when ou use the 7com)ress option

39

Whether the "wim file aligns on a BCK !oundar or the default :7K !oundar " Im)ortant If ou name our configuration_list"ini file wimscript"ini, and store it in our ,Image director (where the ,Image"e2e file is located)D it will automaticall run when ou run the 7ca)ture option with or without the 7com)ress parameter, without requiring ou to use the 7con$i# option"

?@am3le
7es+ri3tion The 7con$i# option ena!les ou to customi4e specific compression, capture, and !oundar alignment actions, for each indi#idual file and folder, within ,Image" $reate the con i!"ration#$ist"ini file using a te2t editor, such as +otepad" The following sections appear in the ,Image configuration list< )ection [ExclusionList] .escription Ena!les ou to define the files and folders to e2clude from the 7ca)ture option" [CompressionExclusionList] Ena!les ou to define the specific files and folders, in addition to specific file t pes, to e2clude from the 7com)ress option" 4ote 0ou can use file or folder matching to e2clude a file from compression" 0ou can pro#ide a full path match, or ou can use wildcards (M)" *or e2ample, ou can enter C:\WINDOWS\inf\ !pnf to match a specific t pe of file, or C:\WINDOWS\inf\ to match an entire folder"

40

)ection ["li#nmentList]

.escription Ena!les ou to define specific files to align on a BCK !oundar " $ompression will not occur for an files aligned on a BCK !oundar " If ou do not list files within this section, our files will all align on a :7K !oundar " 4ote )ecurit ma occasionall use this section for pattern matching purposes"

41

Code
[ExclusionList] $i%erfil!sys &a#efile!sys 'oot!ini (system )olume Information( C:\*EC+CLE* [CompressionExclusionList] !mp, !-ip !ca% C:\WINDOWS\inf\ta%letpc!inf C:\WINDOWS\inf\ !pnf C:\WINDOWS\inf\ ["li#nmentList] &arallel!sys

Using the Configuration 2ile

If ou create a custom5named con i!"ration#$ist"ini file and store it outside of the ,Image director , ou can use ,Image to run the file" At a command prompt, open the ,Image director , and then t pe< xima#e .confi# c:\ima#in#\confi#uration/list!ini .capture 0: 0:\ima#in#\0ata!1im (Dri2e D( Otherwise, at the command prompt, ou can also t pe< xima#e .confi# c:\ima#in#\confi#uration/list!ini .appen0 0: 0:\ima#in#\0ata!1im (Dri2e D( Where c:\i&a!in!\con i!"ration#$ist%ini pro#ides the complete director location for the configuration file" 0ou must use either the 7ca)ture option to create a new "wim file, or the 7a))end option to append an e2isting "wim file"

/ee Also
Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e (Ima e Command-Line "&tions

WalAthrough= Ca3ture an Image

,Image is a command5line tool that uses a set of A'Is, &nown as Windows Imaging A'I (WIM>A'I), to perform man tas&s with the Microsoft Windows Imaging (WIM) files" WIM files contain one or more #olume images for a Windows operating s stem, while a #olume image represents the captured #olume or partition of a Windows operating s stem" The primar purpose of ,Image is to

42

capture, modif , and appl images for deplo ment in a manufacturing or corporate IT en#ironment"

;rereBuisites
%efore ou can capture an image using ,Image, ou must perform the following tas&s< =" Install the WAIK tools, including ,Image on our master computer" 7" $onfigure and customi4e the files for our installation" :" (un the ) sprep tool to remo#e all user5specific and computer5specific settings and data, to reset the product acti#ation cloc& to :8 da s, and to ena!le the end user to accept the -icense Terms for Microsoft )oftware after the first time ou start the computer" C" $reate a configuration file to control the capture, compression, and !oundar alignment capa!ilities of ,Image" To create a configuration file, see the topic Confi uration $ile Creation" 9" .etermine whether to compress our image, using an option other than fast compression" To compress our image using another compression t pe, see the topic Wal5t!rou !0 Com&ress an Ima e"

Ca3ture /+enarios
0ou can capture our image file from Windows 'E, MicrosoftG Windows code5 named ;-onghorn,; MicrosoftG Windows ,'G with )er#ice 'ac& 7 ()'7), MicrosoftG Windows )er#er 788:G with )er#ice 'ac& = ()'=), or a customi4ed Windows 'E pro#ided ! MicrosoftG ) stems Management )er#er ()M)) Operating ) stem .eplo ment *eature 'ac& or WindowsG .eplo ment )er#ices (W.))" Ca3turing an ?ntire Installation If ou capture an entire installation, the !est practice is to !oot from Windows 'E" %ecause Windows 'E runs in memor , or from a $.H.?., it ensures that no loc&ed files or folders will !e included in our installation image" -oc&ed files and folders will cause the image capture to fail" Ca3turing from a Customi:ed Windows ;? If ou capture an entire installation, the !est practice is to !oot from Windows 'E" 1owe#er, depending on our licensing agreement, ou ma onl ha#e access to a customi4ed #ersion of Windows 'E, pro#ided ! MicrosoftG ) stems Management )er#er ()M)) Operating ) stem .eplo ment *eature 'ac& or

43

WindowsG .eplo ment )er#ices (W.))" Although this is a customi4ed #ersion of Windows 'E, it still ena!les the capture of an image from memor , and does not create loc&ed files or folders"

Ca3turing an Image
/sing ,Image, ou can capture our image with fast compression" Once ou capture our image, ou can modif and appl the image either to a networ& or destination computers" Im)ortant To control the amount of compression used on our image, use the 7com)ress option" !o ca)ture an ima#e it" ma6imum com)ression =" %oot our master computer with the Windows 'reinstallation En#ironment (Windows 'E)" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To capture the image, t pe<

xima#e .capture 0:\ima#e/0irectory c:\ima#in#\0ata!1im (Ne1/Ima#e/4ile(

Where d:\i&a!e#director' is the location of the files to image, c:\i&a!in!\data%wi& is the name and location of the new image file, and ;New#(&a!e#)i$e; is a description a!out the image file" 4ote If ou do not pro#ide a location for our new "wim file, the capture process automaticall creates it in our ,Image director " *or e2ample, if ou enter Data.wim instead of d:\imaging\data.wim, then the new "wim file appears in our ,Image director "

/3litting an Image
If the "wim file is too large for our selected media, ou can split the file into smaller files, for spanning across multiple writa!le mediums" *or e2ample, if our "wim file is too large to fit on $. media, ou can split the "wim file so that it spans se#eral $.5(OMs" % default, the 7s)lit option names the split "wim files the same as the specified imageNfile, with an additional num!er and a "swm file name e2tensionD howe#er, ou can specif a custom name or destination location, if required"

44

!o s)lit an ima#e =" .etermine the si4e of media required for the image" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To split the image, t pe<

xima#e .split 0:\ima#in#\0ata!1im 566

Where d:\i&a!in!\data%wi& is the name and location of the image file to split and *++ is the si4e in mega! tes (M%) for each of the created files" In this e2ample, the 7s)lit option creates a .ata"swm file, a .ata7"swm file, a .ata:"swm file, and so on, defining each portion of the split "wim file" !o s)lit an ima#e )ro+idin# a custom name and destination location =" .etermine the si4e of media required for the image" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To split the image to a specific director , t pe<

xima#e .split c:\ima#in#\0ata!1im 0:\ima#in#\0ataparts!s1m 78

Where c:\i&a!in!\data%wi& is the name and location of the image file to split, d:\i&a!in!\dataparts%sw& is the destination name and location for the split "wim files, and 2, is the si4e in mega! tes (M%) for each of the created files" In this e2ample, the 7s)lit option creates a .ataparts"swm file, a .ataparts7"swm file, a .ataparts:"swm file, and so on, defining each portion of the split "wim file, in the d<Kimaging director "

-e@t /te3s
After capturing and compressing our image, ou can use the 7mount or 7mountr option to mount the image to our technician computer for modification, including adding, editing, and deleting files" 0ou can also use the 7a))ly option to appl the image to a networ& location or directl to our destination computers if modifications are not required" 4ote 0ou cannot modif split "wim filesD ou can onl appl the files to our destination computers, using the 7a))ly option"

/ee Also
Wal5t!rou !0 A&&l' a .e&lo'ment Ima e

45

Wal5t!rou !0 Com&ress an Ima e Confi uration $ile Creation Wal5t!rou !0 Mount and Modif' an Ima e (Ima e Command-Line "&tions

WalAthrough= Com3ress an Image

,Image is a command5line tool that uses a set of A'Is, &nown as Windows Imaging A'I (WIM>A'I), to perform man tas&s with the Microsoft Windows Imaging (WIM) files" WIM files contain one or more #olume images for a Windows operating s stem, while a #olume image represents the captured #olume or partition for a Windows operating s stem" The primar purpose of ,Image is to capture, modif , and appl images for deplo ment in a manufacturing or corporate IT en#ironment"

;rereBuisites
%efore ou can compress an image using ,Image, ou must perform the following tas&s< =" Install the WAIK tools, including ,Image on our master computer" 7" $onfigure and customi4e the files for our installation" :" (un the ) sprep tool to remo#e all user5specific and computer5specific settings and data, to reset the product acti#ation cloc& to :8 da s, and to ena!le the end user to accept the -icense Terms for Microsoft )oftware after the first time ou start the computer" C" $reate a configuration file to control the capture, compression, and !oundar alignment capa!ilities of ,Image" To create a configuration file, see the topic Confi uration $ile Creation"

Com3ression /+enarios
0ou can compress and capture our image file from Windows 'E, MicrosoftG Windows code5named ;-onghorn,; MicrosoftG Windows ,'G )er#ice 'ac& 7, MicrosoftG Windows )er#er 788:G )er#ice 'ac& =, or a customi4ed Windows 'E pro#ided ! MicrosoftG ) stems Management )er#er ()M)) Operating ) stem .eplo ment *eature 'ac& or WindowsG .eplo ment )er#ices (W.))" Com3ressing and Ca3turing an ?ntire Installation If ou compress and capture an entire installation, the !est practice is to !oot from Windows 'E" %ecause Windows 'E runs in memor , or from a $.H.?., it ensures that no loc&ed files or folders will !e included in our installation image" -oc&ed files and folders will cause the image compression and capture to fail"

46

Com3ressing and Ca3turing from a Customi:ed Windows ;? If ou compress and capture an entire installation, the !est practice is to !oot from Windows 'E" 1owe#er, depending on our licensing agreement, ou ma onl ha#e access to a customi4ed #ersion of Windows 'E, pro#ided ! MicrosoftG ) stems Management )er#er ()M)) Operating ) stem .eplo ment *eature 'ac& or WindowsG .eplo ment )er#ices (W.))" Although this is a customi4ed #ersion of Windows 'E, it still ena!les the compression and capture of an image from memor , and does not create loc&ed files or folders"

Com3ressing an Image
.uring the compression process, ou can select one of the following compression t pes for our image< ma6imum< 'ro#ides the !est compressionD howe#er, it also ta&es the longest time to capture the image" $ast< 'ro#ides faster image captureD howe#er, it pro#ides less compression than that pro#ided ! ma6imum" This is the default compression t pe, used if ou lea#e this parameter !lan& or if ou use the 7ca)ture option without the 7com)ress option" none< $aptures our image without compression" %ecause the 7com)ress option specifies the t pe of compression for our entire "wim file, this option is #alid onl on the initial capture and cannot !e changed" Additionall , if ou use the 7e6)ort option, the source and destination "wim files must ha#e the same compression t pe" Im)ortant If ou do not pro#ide a location for our new "wim file, it will appear in our ,Image director " *or e2ample, if ou enter Data.wim instead of d:\imaging\data.wim, then the new "wim file will appear in our ,Image director " *a@imum Com3ression !o com)ress and ca)ture an ima#e it" ma6imum com)ression =" %oot our master computer with the Windows 'reinstallation En#ironment (Windows 'E)" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To compress and capture the image, t pe<

xima#e .compress maximum .capture c:\ima#e/0irectory 0:\ima#in#\0ata!1im (ne1/ima#e/file(

47

Where ma6imum is the compression t pe, c:\i&a!e#director' is the location of the files to image, d:\i&a!in!\data%wi& is the name and location of the new image file, and ;new#i&a!e# i$e; is a description a!out the image file" 2ast Com3ression !o com)ress and ca)ture an ima#e it" $ast com)ression =" %oot our master computer with Windows 'E" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To compress and capture the image, t pe<

xima#e .compress fast .capture c:\ima#e/0irectory 0:\ima#in#\0ata!1im (ne1/ima#e/file(

Where $ast is the compression t pe, c:\i&a!e#director' is the location of the files to image, d:\i&a!in!\data%wi& is the name and location of the new image file, and ;new#i&a!e# i$e; is a description a!out the image file" This is also the default compression t pe, used if ou capture our image without using the 7com)ress option, or if ou lea#e this parameter !lan&" -one !o ca)ture an ima#e it"out com)ression =" %oot our master computer with Windows 'E" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To compress and capture the image, t pe<

xima#e .compress none .capture c:\ima#e/0irectory 0:\ima#in#\0ata!1im (ne1/ima#e/file(

Where none is the compression t pe, c:\i&a!e#director' is the location of the files to image, d:\i&a!in!\data%wi& is the name and location of the new image file, and ;new#i&a!e# i$e; is a description a!out the image file"

/3litting an Image
If the "wim file is too large for our selected media, ou can split the file into smaller files, for spanning across multiple writa!le mediums" *or e2ample, if our

48

"wim file is too large to fit on $. media, ou can split the "wim file so that it spans se#eral $.5(OMs" % default, the 7s)lit option names the split "wim files the same as the specified imageNfile, with an additional num!er and a "swm file name e2tensionD howe#er, ou can specif a custom name or destination location, if required" !o s)lit an ima#e =" .etermine the si4e of media required for the image" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To split the image, t pe<

xima#e .split 0:\ima#in#\0ata!1im 566

Where d:\i&a!in!\data%wi& is the name and location of the image file to split and *++ is the si4e in mega! tes (M%) for each of the created files" In this e2ample, the 7s)lit option creates a .ata"swm file, a .ata7"swm file, a .ata:"swm file, and so on, defining each portion of the split "wim file" !o s)lit an ima#e )ro+idin# a custom name and destination location =" .etermine the si4e of media required for the image" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To split the image to a specific director , t pe<

xima#e .split c:\ima#in#\0ata!1im 0:\ima#in#\0ataparts!s1m 78

Where c:\i&a!in!\data%wi& is the name and location of the image file to split, d:\i&a!in!\dataparts%sw& is the destination name and location for the split "wim files, and 2, is the si4e in mega! tes (M%) for each of the created files" In this e2ample, the 7s)lit option creates a .ataparts"swm file, a .ataparts7"swm file, a .ataparts:"swm file, and so on, defining each portion of the split "wim file, in the d<Kimaging director "

-e@t /te3s
After capturing and compressing our image, ou can use the 7mount or 7mountr option to mount the image to our technician computer for modification, including adding, editing, and deleting files" 0ou can also use the 7a))ly option to appl the image to a networ& location or directl to our destination computers if modifications are not required"

49

4ote 0ou cannot modif split "wim filesD ou can onl appl the files to our destination computers, using the 7a))ly option"

/ee Also
Confi uration $ile Creation Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Mount and Modif' an Ima e Wal5t!rou !0 A&&l' a .e&lo'ment Ima e (Ima e Command-Line "&tions

WalAthrough= *ount and *odif4 an Image

With the ,Image tool, the Windows Imaging *ile ) stem *ilter (WIM *) *ilter), and a Windows Imaging ("wim) file, ou can map the contents of the image to a director and perform common file operations, such as cop ing, pasting, and editing from a file management tool, such as Windows E2plorer, without e2tracting or recreating the image" To manipulate an image, ou must install the WIM *) *ilter dri#er on our technician computer" Once installed, the dri#er ena!les ou to mount our image with read5onl or readHwrite permissions, and #iew the included files and folders from a file management tool, such as Windows E2plorer"

;rereBuisites
%efore ou can mount and manipulate an image using ,Image, ou must perform the following tas&s<

50

=" Install Windows code5named ;-onghorn; and the WAIK tools, including ,Image on our master computer" 7" $onfigure and customi4e the files for our installation file" :" (un the ) sprep tool to remo#e all user5specific and computer5specific settings and data, to reset the product acti#ation cloc& to :8 da s, and to ena!le the end user to accept the -icense Terms for Microsoft )oftware after the first time ou start the computer" C" $apture, and, optionall , compress, our installation into an image file with ,Image" 9" Install the Windows Imaging *ile ) stem *ilter (WIM *) *ilter)"

Installing the Windows Imaging 2ile /4stem 2ilter (WI* 2/ 2ilter) 7ri1er
%efore ou can mount or modif our image, ou must install the WIM *) *ilter dri#er on our technician computer" Im)ortant The WIM *) *ilter dri#er requires that the technician computer run one of the following operating s stems<

51

!o install t"e WI. =* =ilter dri+er =" In Windows E2plorer, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

7" (ight5clic& the Wimfltr"inf file, and then clic& Install"

*ounting an Image
After installing the WIM *) *ilter dri#er, ou ma mount our image with read5 onl or readHwrite permissions to a director on our technician computer" If ou mount an image with read5onl permission, ou will !e una!le to modif the image and sa#e an changes" Im)ortant After ou mount our image, the e2isting files or folders in our mount director will disappear" The files and folders will reappear after ou unmount our director " !o mount an ima#e it" read-only )ermission =" %oot our technician computer with a supported Windows operating s stem" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To mount the image, t pe<

xima#e .mount c:\mounte0/ima#es 0:\ima#in#\0ata!1im 7

Where c:\&o"nted#i&a!es is the location of the mount director , d:\i&a!in!\data%wi& is the name and location of the "wim file to mount, and 2 is the reference num!er of the specific #olume in the "wim file" !o mount an ima#e it" read7 rite )ermission =" %oot our technician computer with a supported Windows operating s stem" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To mount the image, t pe<

xima#e .mountr1 c:\mounte0/ima#es 0:\ima#in#\0ata!1im 7

52

Where c:\&o"nted#i&a!es is the location of the mount director , d:\i&a!in!\data%wi& is the name and location of the "wim file to mount, and 2 is the reference num!er of the specific #olume in the "wim file"

*odif4ing an Image
Once ou mount an image, the director structure !ecomes a#aila!le from a file management tool, such as Windows E2plorer" *rom the file management tool, ou can re#iew our file and folder structure, add files and folders, edit the e2isting files and folders, and delete an files and folders that ou do not need" !o +ie $iles and $olders =" *rom our technician computer, start Windows E2plorer, and open the mounted director " *or e2ample, t pe<
c:\mounte0/ima#es

7" (e#iew the file and folder structure, including content" !o add $iles or $olders =" *rom our technician computer, start Windows E2plorer, and open the mounted director " *or e2ample, t pe<
c:\mounte0/ima#es

7" Add additional files and folders to the location where the must appear once applied to the destination computer" *or e2ample<
c:\pro#ram/files\application/name

Im)ortant If ou must add an application or de#ice, #erif that ou included all required files" Although ou can add application files and folders, ou cannot install applications" !o edit $iles or $olders =" *rom our technician computer, start Windows E2plorer, and open the mounted director " *or e2ample, t pe<
c:\mounte0/ima#es

7" Edit the files and folders" 0ou ma mo#e the files and folders within our image, or open the files and #iew their contents"

53

!o delete $iles or $olders =" *rom our technician computer, start Windows E2plorer, and open the mounted director " *or e2ample, t pe<
c:\mounte0/ima#es

7" .elete the files and folders" 4ote 0ou cannot delete an entire "wim fileD howe#er, ou can delete all of the files contained within the image"

Unmounting an Image
After ou modif an image, ou must unmount the image" At this time, if ou mounted our image with readHwrite permissions, ou can commit our changes and ma&e our modifications a permanent part of the image" Im)ortant .o not perform the 7unmount 7commit option from Windows 'reinstallation En#ironment (Windows 'E)" %ecause Windows 'E forces a re!oot e#er 7C hours, and !ecause mounted images cannot persist across re!oots, if ou ha#e changes to commit as the re!oot occurs, ou will lose the changes" !o unmount an ima#e =" %oot our technician computer with a supported Windows operating s stem" 7" At the command prompt, open the ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

:" To unmount the image, t pe<

xima#e .unmount .commit c:\mounte0/ima#es

Where c:\&o"nted#i&a!es is the location of the mount director " If ou do not specif the parameters to unmount, this option lists all mounted images, !ut does not perform the unmount action" Im)ortant If ou use the 7unmount option without the 7commit option, our changes will !e discarded" To sa#e our changes, the following conditions must !e true< 5 0ou mounted the image using the Hmountrw option" 5 0ou used the Hcommit option with the Hunmount option"

54

-e@t /te3s
After modif ing an image, ou can appl the image from a networ& share or from our local media, such as a .?. or dis&"

/ee Also
Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e Wal5t!rou !0 A&&l' a .e&lo'ment Ima e (Ima e Command-Line "&tions

;hase &= Image 7e3lo4ment

This section pro#ides instructions on how to deplo an image of Windows onto new computers" %ased on our deplo ment method, select the appropriate topic"

In this /e+tion
Confi ure .is5 Confi uration Windows Installation usin t!e -roduct .7. Ima e .e&lo'ment from a Networ5

/ee Also
-!ase ;0 Ima e Ca&ture and Modification

Configure 7isA Configuration

This screen ena!les ou to define and configure each hard dis& and its associated partition in the /nattend"2ml file" )etup applies these settings during the dis& configuration phase" 4ote The entries and selections that ou ma&e on the *unOnce Commands screen will appear in the ODiskConfigP and OImageInstallP elements of the /nattend"2ml" Im)ortant If ou do not define or configure a hard dis& I., )etup will automaticall partition hard dis& 8 with a single partition and install the operating s stem"

55

!o con$i#ure dis/ con$i#uration =" *rom Setup !anager, clic& +is/ Con%iguration in the left pane" The +is/ Con%iguration page will appear" 7" *rom the +is/s area, list all hard dis&s installed on the destination computer, defining the following information<
I+) %elect a numeric #alue to re&resent t!e !ard dis5 I.? 1!e default #alue is CD !owe#er@ t!e #alue can *e an' num*er *etween 0 and -1? 1!is is a re6uired field if 'ou &erform an' dis5 or &artition confi uration and must *e uni6ue for eac! !ard dis5?

*epartition) %elect t!e *epartition c!ec5 *o4 to o#erwrite an e4istin &artition on t!e !ard dis5 defined *' t!e !ard dis5 I.? 2' default@ t!is c!ec5 *o4 is selected?

:" *rom the artitions %or dis/ area, define the partition settings for each hard dis&, including defining the following information<
Action) %elect t!e action to &erform on t!e !ard dis5? 1!is can *e Create@ w!ic! creates a new &artition@ or !odi%y@ to modif' an e4istin &artition?

'ype) %elect t!e t'&e of !ard dis5 to &artition@ eit!er (34tensi*le $irmware Interface)?

rimary or 2FI

Im)ortant 0ou cannot create more than four primar partitions on a single hard dis&"
Si#e) 1'&e t!e si,e in me a*'tes (M2) for t!e &artition? 1!e #alue must *e &ositi#e and reater t!an or e6ual to -?

I+) %elect a numeric #alue from - to -3 to re&resent t!e &artition? 7erif' t!at no two &artitions !a#e t!e same &artition I.?

2xtend) %elect w!et!er to associate t!e e4tended !ard dis5 attri*utes wit! t!e &artition? 1!is c!ec5 *o4 is onl' a#aila*le if 'ou modif' a &artition and@ *' default@ is cleared?

Format) %elect t!e c!ec5 *o4 to define w!et!er %etu& must format t!e &artition durin t!e !ard dis5 confi uration &!ase?

&etter) 1'&e an al&!a*etical #alue@ ran in from C to 4@ to re&resent t!e &artition? 2' default@ t!e letter C a&&ears? 7erif' t!at no two &artitions !a#e t!e same &artition letter?

&abel) 1'&e a la*el for 'our &artition? 1!is field is not re6uired and does not !a#e a ma4imum c!aracter len t!?

56

Im)ortant %efore ou can define the partition settings, ou must create or select a single hard dis& from the +is/s area" 0ou cannot select multiple hard dis&s !ecause each hard dis& ma ha#e unique partition requirements" C" *rom the Operating System Installation &ocation area, ou ha#e the option to define the following information<
Install the Operating System to hard dis/) %elect t!e !ard dis5 to w!ic! 'ou will install t!e o&eratin s'stem?

artition I+) %elect t!e !ard dis5 &artition to w!ic! 'ou will a&&l' t!e o&eratin s'stem?

rompt $ser) %elect t!e c!ec5 *o4 to dis&la' t!e !ard dis5 I. and &artition-related UI to t!e end user for modification? If t!is c!ec5 *o4 is cleared@ t!e UI will not a&&ear and t!e end user will not *e a*le to modif' t!e information?

/ee Also
Confi ure User %ettin s Confi ure )un"nce Commands W!at is %etu& Mana er> +ow %etu& Mana er Wor5s

Windows Installation using the ;rodu+t 7C7

The simplest method to install Windows on new hardware is to start directl from the Windows product .?." This method is commonl &nown as the $. %oot method, and pro#ides fle2i!ilit when networ& access is not a#aila!le or ou !uild onl a few computers" In addition, ou can use )etup Manager to create a single answer file (/nattend"2ml) to ma&e the installation process more efficient" /nattend"2ml pro#ides the answers for )etup" OEMs are required to reseal the new installation ! using the ) stem 'reparation () sprep) tool" ) sprep clears #arious user settings and resets the computer so that the ne2t time the computer restarts, our customers can accept the -icense Terms for Microsoft )oftware, enter the 'roduct Ke , and add user and compan information"

In this /e+tion
Installin Windows from t!e -roduct .7. Install Windows from t!e -roduct .7. (Networ5)

6elated /e+tions
%etu& 1ec!nical )eference %'s&re& 1ec!nical )eference

57

/ee Also
Ima e .e&lo'ment from a Networ5

Installing Windows from the ;rodu+t 7C7

This method is the simplest method for installing Windows onto new hardware" Instead of starting the computer with Windows 'E and installing a configuration set, ou can use the $. %oot method to start Windows )etup on computers that support starting from a $.H.?." This method pro#ides limited automated customi4ation" This method is useful when networ& access is not a#aila!le or when ou must !uild onl a few computers" 4ote Windows code5named ;-onghorn; is primaril distri!uted in .?. format !ecause of its file si4e" !o install Windo s $rom t"e Windo s )roduct D2D =" $reate an /nattend"2ml answer file using the )etup Manager tool and sa#e it to a flopp dis&" The answer file will ena!le ou to automate all or parts of )etup" 7" )tart the computer from the Windows product .?." Windows )etup ()etup"e2e) will !egin automaticall " :" When )etup displa s the message that it is e2amining the hardware configuration, insert the flopp dis& that contains the /nattend"2ml file" C" When the light of the flopp dis& dri#e turns off, remo#e the flopp dis&" )etup will cop files to the hard dis&" 9" After )etup finishes, install applications and run ) sprep to con#ert the computer to a customer5read state"

/ee Also
-reinstallation Met!ods Install Windows from t!e -roduct .7. (Networ5)

Install Windows from the ;rodu+t 7C7 (-etworA)

This section will descri!e how to install Windows from the product .?. from a networ& share"

/ee Also
Installin Windows from t!e -roduct .7.

58

Image 7e3lo4ment from a -etworA

This section descri!es how to deplo a !ase image of Windows from a networ& share" This section assumes that ou ha#e alread created and stored the image on a distri!ution share" An image can !e either a cop of the complete set of files in the installation (a file5!ased image) or a single image file ("wim) created ! the ,Image tool" There are man wa s to cop files from the networ& share to the new computer" This section will focus on using Windows 'E to !oot the new computer onto the networ& and on using ,Image to appl the !ase image onto the new computer" Once the !ase image is copied to the new computer, ou can customi4e the installation !efore deli#ering the computer to our customer"

In this /e+tion
Wal5t!rou !0 A&&l' a .e&lo'ment Ima e

/ee Also
Windows Installation usin t!e -roduct .7.

WalAthrough= A33l4 a 7e3lo4ment Image

,Image is a command5line tool in Windows code5named Q-onghorn,@ that uses a set of A'Is, &nown as Windows Imaging A'I (WIM>A'I), to perform man tas&s with the Microsoft Windows Imaging ("wim) files" A "wim image file contains one or more #olume images, dis& #olumes that contain images of an installed Windows operating s stem" The primar purpose of ,Image is to capture, modif , and appl images for deplo ment and redeplo ment in a manufacturing or corporate IT en#ironment"

;rereBuisites
%efore ou can appl an image ! using ,Image, ou must perform the following tas&s<

59

=" Install the WAIK tools, including ,Image on our master computer" 7" $onfigure and customi4e the files for our image file" :" (un the ) sprep tool to remo#e all user5specific and computer5specific settings and data, to reset the product acti#ation cloc& to :8 da s, and to ena!le the end user to accept the -icense Terms for Microsoft )oftware after the first time ou start the computer" C" $apture, and optionall compress, an image using ,Image" 9" Mount, modif , and unmount our image, if needed"

A33l4ing an Image using a -etworA 6etrie1al /+enario

0ou can use the networ& retrie#al scenario to appl a single image file to multiple destination computers, using )er#er Message %loc& ()M%)" This scenario ena!les ou to wor& o#er our e2isting protocol stac&" !o a))ly your ima#e $rom t"e net or/ =" Mo#e our image file to a networ& location, accessi!le from our master computer" 7" %oot our master computer with the Windows 'reinstallation En#ironment (Windows 'E)" :" At the command prompt, open our ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

C" $onnect to our image )M% share" *or e2ample, t pe<

net use y: \\my/ima#e/s9are\ima#es

9" To appl

our image from the networ&, t pe<

xima#e .apply y:\0ata!1im c:\ :

Where c:\ is the root of the destination #olume to which ou will appl the image, ':\data%wi& is the )M% location from which the image is applied, c:\ is the root of the destination #olume to which ou will appl the files, and 1 specifies the specific #olume to appl from the files"

A33l4ing an Image using 7istri8uted 7e3lo4ment to /tandalone Com3uters

0ou can use distri!uted deplo ment to appl an image to our disconnected, standalone destination computers" This deplo ment method requires that ou

60

create a default image, and send the "wim file to our emplo ees for installation or to a location where our emplo ees can install the "wim file" 4ote %ecause this method requires either $. or .?. media distri!ution, ou might need to split our "wim file into smaller files, and appl them across multiple writa!le mediums" *or more information a!out how to split our "wim file see Wal5t!rou !0 Ca&ture an Ima eand Wal5t!rou !0 Com&ress an Ima e

A33l4ing an Image using /3lit WI* 2iles

If ou split our "wim file due to si4e constraints, ou can appl the files from our networ&" !o a))ly t"e s)lit 5 im $iles $rom t"e net or/ =" Mo#e our split "wim files to a networ& location, accessi!le from our master computer" 7" %oot our master computer with Windows 'E" :" At the command prompt, open our ,Image director " *or e2ample, t pe<
c:\op3tools\xima#e

C" $onnect to our image )M% share" *or e2ample, t pe<

net use y: \\my/ima#e/s9are\ima#es

9" To appl 5O(5

our image from the networ&, t pe<

xima#e .ref y:\ !s1m .apply y:\0ata!1im c:\ :

xima#e .ref y:\0ata7!s1m .ref y:\0ata!1im c:\ :

Where data2%sw& or *%sw& are the sp$it %wi& i$es to app$'- ':\data%wi& is the )M% location from which the image is applied, c:\ is the root of the destination #olume to which ou will appl the files, and 1 specifies the specific #olume to appl from the files"

/ee Also
Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e Wal5t!rou !0 Mount and Modif' an Ima e (Ima e Command-Line "&tions

61

;hase '= Image *aintenan+e

This section will descri!e how to ser#ice an e2isting image"

Installation <e+hnologies <e+hni+al 6eferen+e

This section includes reference material on the following technologies<
Windows -roduct Acti#ation %etu& Mana er 1ec!nical )eference %'s&re& 1ec!nical )eference (Ima e 1ec!nical )eference

Windows ;rodu+t A+ti1ation

Windows 'roduct Acti#ation (W'A) reduces Windows pirac ! ensuring compliance with the -icense Terms for Microsoft )oftware)" )oftware pirac damages consumers, manufacturers, and software pu!lishers ali&e when consumers are pro#ided incomplete software and documentation pac&ages, and no customer support" 'roduct acti#ation ensures compliance with the -icense Terms for Microsoft )oftware, which for the Windows operating s stem states that a licensed cop of Windows can !e installed onl on one computer" It significantl reduces pirac of Windows, while requiring a minimum of additional steps ! the legal end user or computer manufacturer" 'roduct acti#ation wor&s ! matching the 'roduct Ke with the indi#idual computer on which the software is installed" It does this ! #alidating the 'roduct Ke , and chec&s that it has not !een used with more than the licensed num!er of computers" An end user has :8 da s from the initial startup to acti#ate their installation" The end user can acti#ate their installation ! using the Internet or the telephone" The computer manufacturer can also prepopulate the unique 'roduct Ke from the certificate of authenticit ($OA) stic&er on the specific computer, and acti#ate the computer on !ehalf of the end user" After Windows acti#ates, acti#ation is not initiated unless the end user ma&es significant hardware changes to the computer" If significant hardware changes are detected, the end user must reacti#ate the computer so that the license can !e reconfirmed" *or details on hardware changes that require an end user to reacti#ate the computer, see the <e+hni+al *arAet >ulletins on the *i+rosoft ;rodu+t A+ti1ation we8 site"

62

9ow A+ti1ation WorAs

'roduct acti#ation !egins with the s stem com!ining the 'roduct Ke and a non5 unique hardware identifier to create an installation I." The end user then sends the installation I. to a Microsoft -icensing clearinghouse, either automaticall using an Internet connection on the computer or ! telephoning a Microsoft customer ser#ice center" The Microsoft -icensing clearinghouse chec&s that this 'roduct Ke has not !een used on more than the num!er of computers specified ! the -icense Terms for Microsoft )oftware" If this chec& passes, the Microsoft -icensing clearinghouse sends the computer a confirmation I., which acti#ates this installation of Windows on that particular computer" If the chec& fails, howe#er, the installation of Windows is not acti#ated" When acti#ation fails, the end user is gi#en the opportunit to contact a customer ser#ice representati#e and request to transfer the license associated with the 'roduct Ke to another computer" 4ote (egistration is not the same as Windows 'roduct Acti#ation" (egistration is optional, contains identif ing information, and is primaril a mar&eting tool" Acti#ation is a required anti5pirac measure" +o identif ing information is transmitted or sa#ed during acti#ation"

A+ti1ation and ;reinstallation

0ou can use ) sprep for a ma2imum of three times to reset the cloc& for Windows 'roduct Acti#ation" After the third time, the cloc& can no longer !e reset" *or more information a!out the role that acti#ation pla s in the preinstallation process, see< 'repopulating the 'roduct Ke and 'reacti#ating Windows ) sprep and Windows 'roduct Acti#ation *requentl As&ed Ruestions (*AR)

/etu3 <e+hni+al 6eferen+e

)etup is the program that ena!les the installation, upgrade, and configuration of Windows code5named ;-onghorn"; )etup is also the !asis for the following installation and upgrade methods< unattended )etup, Windows .eplo ment )er#ices (W.)), and image5!ased installation with the ) stem 'reparation tool () sprep)" 4ote This program replaces the pre#ious #ersions of Winnt"e2e, Winnt:7"e2e, te2t5mode )etup, and >/I5mode )etup"

63

In this /e+tion
W!at is %etu& Mana er> +ow %etu& Mana er Wor5s Unattend?4ml %ettin s

/ee Also
%'s&re& 1ec!nical )eference (Ima e 1ec!nical )eference

What is /etu3D
Windows )etup is the program that ena!les ou to install or upgrade to the Windows code5named ;-onghorn"; )etup is also the !asis for the following installation and upgrade methods< unattended )etup, Windows .eplo ment )er#ices (W.)), and Image5!ased )etup with the ) stem 'reparation tool () sprep)" This topic includes< %enefits of )etup $ommon )etup )cenarios .ependencies of )etup Technologies (elated to )etup

>enefits of /etu3
Man OEMs and corporations must install and configure Windows as rapidl as possi!le" (educed deplo ment and installation time lowers manufacturing costs for OEMs, and can decrease cost and scheduling ris& for corporate deplo ments" The new )etup technolog for Windows code5named ;-onghorn; pro#ides the following !enefits< Better *tability" In the past, )etup was somewhat unsta!le, which affected the consistenc and qualit of the installation of the operating s stem" The new Windows )etup uses Image5!ased )etup (I%)), a technolog that ma&es )etup faster and more consistent !ecause it uses a single file5!ased, non5destructi#e image for the installation" Reduction in 4umber o$ Ima#es" 're#iousl , an OEM or corporation maintained man installation images due to differences in s stem components and configuration" The new Windows )etup ena!les ou to configure multiple components within a single, unified /nattend"2ml file"

64

1om)liance it" t"e WI. =ile =ormat" )etup emplo s the Windows Imaging ("wim) file format for the installation image" The use of "wim images pro#ides a file5!ased format that ena!les ou to install Windows code5named ;-onghorn; to a hard dis& without o#erwriting the contents of the dri#e" =aster Installations and >)#rades" %ecause Windows )etup is now image5!ased, ou can install and upgrade Windows code5named ;-onghorn; faster and easier" 0ou can perform a clean installation of Windows ! deplo ing a cop of the installation image stored on our networ& location to destination computers, or ! manuall installing the Windows product .?. onto destination computers" 0ou can perform quic& and eas upgrades ! appl ing the installation image of Windows code5named ;-onghorn; to an supported #ersion of Windows and migrating the pre#ious #ersionFs settings" *treamlined Installations" )etup ena!les the optimi4ed manufacturing and deplo ment scenarios used ! OEMs and corporations" As a result, the user e2perience ta&es less time, with fewer tas&s to finish !efore using Windows code5named ;-onghorn";

Common /etu3 /+enarios

)etup is the program that ena!les ou to install or upgrade to Windows code5 named ;-onghorn"; The most common scenarios for using )etup include performing clean and upgrade installations" Clean Installations The most common scenario for )etup is performing a clean installation" This scenario comprises the following stages< =" 0ou run )etup"e2e from our Windows code5named ;-onghorn; $. or .?., networ& share, or locall from our hard dis&" 7" 0ou select the Clean installation t pe" :" )etup creates a local !oot director and copies all of the required )etup files" C" )etup re!oots into Windows code5named ;-onghorn; and launches Windows Welcome" %ecause this is a clean installation, Windows code5named ;-onghorn; does not sa#e our pre#ious settings and preferences"

65

U3grade Installations Another common scenario for )etup is to perform an upgrade installation" To perform an upgrade installation, ou must !egin from one of the following operating s stems< MicrosoftG Windows code5named ;-onghorn; MicrosoftG Windows ,'G MicrosoftG Windows )er#er 788:G

66

This scenario comprises the following stages< =" 0ou run )etup"e2e from a downle#el operating s stem, located on a $. or .?., networ& share, or locall from our hard dis&" 7" 0ou select the $pgrade installation t pe" :" )etup protects our files and settings for migration" This is to pre#ent o#erwriting during the rest of the process" C" )etup re!oots into Windows code5named ;-onghorn,; restores our protected settings and files, and launches Windows Welcome"

7e3enden+ies of /etu3
)etup has the following dependencies< /sing )etup Manager, ou can create an answer file (/nattend"2ml) to automate the )etup process" /sing Windows 'reinstallation En#ironment (Windows 'E), ou can configure our custom Windows installation image, either interacti#el or non5interacti#el " Additionall , ou can migrate data if ou perform an upgrade instead of a clean installation" /sing the ) sprep tool, ou can speciali4e and then generali4e our data for capture ! ,Image" (unning ) sprep on our master computer remo#es all user5specific and computer5specific settings and data, resets the product acti#ation cloc& to :8 da s, and ena!les the creation of a new securit identifier ()I.) when the computer restarts"

<e+hnologies 6elated to /etu3

/etu3 *anager )etup Manger pro#ides a more complete solution for managing images of the operating s stem in !oth our test and deplo ment en#ironments" The solution ena!les complete iterati#e offline image editing, the customi4ation of image settings, the creation of an answer file (/nattend"2ml), and the simplification of the entire creation, pu!lishing, and deplo ment process to destination computers, reducing the time to mar&et for customers" /4stem ;re3aration <ool (/4s3re3) ) sprep prepares a computer for dis& imaging or deli#er to a customer ! configuring the computer to create a new computer securit identifier ()I.) once it is restarted" In addition, ) sprep cleans up user5specific and computer5specific settings and data that ou do not cop to a destination computer"

67

Unattend.@ml /nattend"2ml is the answer file for )etup, created ! using the )etup Manager utilit " This file ena!les the addition and remo#al of components, the configuration of the offline installation, and the completion of )etup tas&s, such as dis& configuration" Additionall , /nattend"2ml ena!les ou to configure multiple components in a single file" 4ote /nattend"2ml replaces the /nattend"t2t file from pre#ious #ersions of Windows" Windows 7e3lo4ment /er1i+es (W7/) W.) ena!les companies to remotel administer and deplo the latest operating s stem, using Windows 'E and W.) )er#er" This deplo ment scenario can !e full unattended, and is customi4a!le and scala!le" 4ote Windows .eplo ment )er#ices replaces the e2isting (emote Installation )er#ices ((I)) deplo ment technolog " Windows ;reinstallation ?n1ironment (Windows ;?) Windows 'E is a minimal Windows operating s stem with limited ser#ices, !uilt on the Windows &ernel" It contains the minimal functionalit that ou need to run Windows )etup, install Windows from a networ& share, automate !asic processes, and perform hardware #alidation" 5Image ,Image is a command5line tool that ena!les the capture, modification, and application of file5!ased dis& images for rapid deplo ment" ,Image wor&s with Windows Imaging ("wim) files for cop ing directl to destination computers, or it can wor& with other technologies that use the WIM images, such as )etup for Windows code5named ;-onghorn";

/ee Also
+ow %etu& Mana er Wor5s Unattend?4ml %ettin s

9ow /etu3 WorAs

Windows )etup is the program that ena!les ou to install or upgrade to the WindowsG operating s stem code5named ;-onghorn"; )etup is also the !asis for the following non5interacti#e installation and upgrade methods< unattended )etup,

68

Windows .eplo ment )er#ices (W.)), and image5!ased installation with the ) stem 'reparation tool () sprep)" 4ote )etup in Windows code5named ;-onghorn; replaces the pre#ious #ersions of Winnt"e2e and Winnt:7"e2e, in addition to te2t5mode )etup and >/I5mode )etup" This topic pro#ides a comprehensi#e re#iew of how )etup wor&s, including< )etup Terms and .efinitions )etup Architecture )etup Methods, Installation T pes, and 'hases

/etu3 <erms and 7efinitions

The following terms are associated with )etup"
Component +escription

$MI .estination computer

.istri!ution ser#er *irst !oot

Image5!ased )etup (I%))

Imaging Master computer

$omponent Management Interface" The programming model interface used to access the functionalit e2posed in the components" The computer on which ou install the operating s stem" *or Windows code5named ;-onghorn,; this is the computer to which ou cop our customi4ed installation image" The computer that contains our installation images for application to destination computers" A phase of )etup, launched when the user !oots into a computer with the offline installation of Windows code5named ;-onghorn"; The mechanism used to install, deplo , and test the installation image" I%) is file5!ased and non5destructi#e, which means that ou can update and modif our images without o#erwriting all of the e2isting data" The process of capturing and cloning an operating s stem for deplo ment to one or man destination computers" The computer that contains our master installation image"

69

Component

+escription

Master installation image

$onsists of our installed and configured operating s stem, in addition to an additional software applications and updated dri#ers, for application to destination computers" Offline installation An installation created ! !uilding components from a repositor to a specified, temporar location" The component files are copied to locations, the registr entries are written to hi#e files, and an offline configura!le settings are set" The installation is read for application to a destination computer and the first !oot phase" Online installation An offline installation, applied and !ooted from a destination computer" $onfiguration of the components occurs online, which ma&es the installation unique to the destination computer" )etup"e2e The tool that prepares our hard dis&, applies the installation image, and ena!les the addition and remo#al of components" )etupcl"e2e >enerates new )ecurit I.s ()I.s) and resets the Access $ontrol -ists (A$-s) for files and folders upon first !oot" )etup E#enting Engine ('anther) Initiali4es the )etup phase and implements all of the actions performed ! )etup, e2cept for those required ! the user interface (/I)" )etup Manager The tool that ena!les ou to edit offline images, customi4e image settings, create an answer file (/nattend"2ml), and simplif the entire creation, pu!lishing, and deplo ment process to destination computers" ) stem 'reparation Tool The tool used to prepare a computer for () sprep) deli#er to a customer ! creating a new computer securit identifier ()I.)" In addition, ) sprep cleans up user5specific and computer5 specific settings and data that must not !e copied to a destination computer" Technician computer The computer used to create and modif our answer files"

70

Component

+escription

/nattend"2ml

/nattended installation ?olume image Windows .eplo ment )er#ices (W.))

Windows Imaging ("wim) file Windows 'reinstallation En#ironment (Windows 'E)

,Image

The answer file that automates )etup"e2e" This file ena!les the configuration of offline installations, the addition and remo#al of components, and man )etup tas&s, such as dis& configuration" The non5interacti#e method of performing )etup using an answer file and installation images" A captured installation image file" One or more #olume image(s) comprise a Windows Imaging ("wim) file" (eplaces the (emote Installation )er#ices ((I)) deplo ment technolog " W.) ena!les companies to remotel administer and deplo the latest operating s stem, using Windows 'E and W.) )er#er" A file5!ased imaging format that contains one or more #olume images" Windows 'E is a minimal Windows operating s stem with limited ser#ices, !uilt on the Windows &ernel" It contains the minimal functionalit that ou need to run Windows )etup, install Windows from a networ& share, automate !asic processes, and perform hardware #alidation" A command5line tool used to capture, modif , and appl installation images for deplo ment in a manufacturing or corporate IT en#ironment"

/etu3 Ar+hite+ture
The )etup program contains components that start and restart the computer, gather information, cop files, and create or ad3ust configuration settings" The following ta!le shows the components and their relationship !ased on the OEM and corporate IT en#ironments"

71

72

/etu3 Installation *ethodsE <43esE and ;hases

/etu3 *ethods )etup can perform installations for Windows code5named ;-onghorn,; using interacti#e or non5interacti#e (unattended )etup) methods" Interacti+e *etu)< The )etup e2ecuta!le file ()etup"e2e) wor&s without an answer file to perform interacti#e installations, upgrades, and configurations" This method is useful for small5scale rollouts or indi#idual computer installations, !ecause it does not require an preparator wor&, such as creating answer files or images" 0ou can interacti#el install or upgrade Windows, using the Windows product .?. from either our .?. dri#e, or from a networ& location (after ou store and share the installation files from the Windows product .?.)" This method in#ol#es a simple repeating process in which )etup alternates !etween prompting for information and performing the appropriate tas&s, such as cop ing files, sa#ing settings, and so on" 4on-interacti+e *etu)< The )etup e2ecuta!le file ()etup"e2e) wor&s with an answer file (/nattend"2ml) to perform non5interacti#e installations, upgrades, and configurations" This method is useful for large5scale rollouts and for achie#ing consistenc and precision in the configuration of each computer" The non5interacti#e method requires that the input come not from a person responding to prompts, !ut instead, from another source, such as an answer file (for unattended )etup or W.)) or from an installation image file (for ) sprep or W.))" )etup and the answer file run on !oth the master computer and the destination computer" 0ou create the /nattend"2ml file on our technician computer using )etup Manager, and then ou run the file on !oth our master computer and our destination computer (required for ) sprep)" The imaging tool, ,Image, runs on our master computer, ena!ling ou to create and appl our custom installation image to our destination computer" /etu3 Installation <43es )etup can perform clean and upgrade installations for Windows code5named ;-onghorn"; )etup cannot perform computer5to5computer migrationsD instead, ou must use the Migration Wi4ard" Im)ortant The Migration Wi4ard functionalit is not implemented for %eta ="

73

Clean Installations

)etup can perform a clean, downle#el installation, o#erwriting our pre#ious settings and preferences"

74

75

$pgrade Installations

)etup can perform an upgrade installation, retaining our settings and preferences, while upgrading our operating s stem to Windows code5named ;-onghorn";

76

;hases of /etu3 Throughout the )etup process, )etup"e2e mo#es through se#eral phases and interacts with man components and technologies" The path that )etup follows for the installation, upgrade, or migration depends on the t pe of installation performed" The )etup phases include< =" Do nle+el< The starting point for clean or upgrade installations" 7" Windo s Preinstallation 0n+ironment ,Windo s P0-< Applies the "wim image of Windows code5named ;-onghorn; and, if the installation is an upgrade, migrates data" :" 8nline< Ena!les the configuration of online components, our !randing, and the installation of an 'lug and 'la de#ices" C" =irst Boot< Ena!les the configuration of components and ma&es the operating s stem unique, ! using ) sprep" 9" 1a)ture< *inishes the image and captures the customi4ed "wim file" 4ote +ot all phases of )etup appl to all scenarios" )ome phases are not required, depending on our installation and requirements"
+ownlevel hase

The downle#el phase starts the clean or upgrade installation from a downle#el operating s stem" This supports !ooting from .?., dis&, MicrosoftG Windows 7888G, MicrosoftG Windows )er#er 788:G, MicrosoftG Windows ,'G, and MicrosoftG Windows code5named ;-onghorn"; In this phase, ou will insert the .?. and !egin the Autorun program" 4ote This replaces Winnt:7"e2e and Winnt"e2e" 0ou can no longer install Windows ! using an M)5.O) command"

5indows 2 hase

The Windows 'E phase applies Windows 'E to the hard dis&, and then restarts into the Windows 'E operating s stem" *rom Windows 'E, ou will choose our

77

language and start )etup" Once )etup starts, a compliance chec& will occur, and )etup will gather information, including< 'roduct I. -icense Terms for Microsoft )oftware )etup T pe (upgrade or clean installation) An additional mass5storage de#ices After )etup acquires this information, confirmation and product !ill!oards will appear" *inall , the s stem configuration will occur, including the following< .is&prep Application of the "wim file for Windows code5named ;-onghorn; Application of the files specific to the #ersion of Windows Application of third5part dri#ers (offline) $onfiguration of the !oot information, including writing the !oot sector, and updating the %oot"ini and %oot"config files" $onfiguration of the offline components, including information a!out components and settings specific to the #ersion of Windows" 4ote This phase replaces !oth te2t5mode )etup and >/I5mode )etup"
Online hase

The Online phase !oots into a primiti#e #ersion of the operating s stem, applies the !ootstrap (the utilities required to start the operating s stem), and ena!les online component configuration, including information a!out securit and components specific to the #ersion of Windows" While in this phase, ou will also configure our !randing, and install an 'lug and 'la de#ices"

78

First Boot hase

The *irst %oot phase !egins ! running ) sprep )peciali4e to create a new ) stem Identification ()I.) #alue" The phase then launches Windows code5 named ;-onghorn; for the first time, starting Windows Welcome, pre#iousl &nown as ;OO%E"; Once in Windows Welcome, ou can log on to the operating s stem, install our applications, perform our networ& configurations, and then run ) sprep >enerali4e to remo#e an computer5specific settings or information, reset the -icense Terms for Microsoft )oftware, and reseal the computer"

79

Capture hase ,Optional.

The $apture phase uses the ,Image tool to prepare the !oota!le media for the capture and modification of the customi4ed installation "wim file" Once ou capture the custom installation image, ou can use ,Image to appl it from a networ& location"

/ee Also
W!at is %etu& Mana er> Unattend?4ml %ettin s

/etu3 Command,Line 03tions

The following command5line options are associated with )etup and the installation of the operating s stem"

80

5Image Command,Line 03tions

The following command5line options are a#aila!le for )etup< *etu)5e6e S71%?&debu#<channelT Sbaudrate:baudrateT S7debu#:portT S7m:folder nameT S7norebootTS7tem)dri+e:dri!e letterT S7unattend:answer fileT Option 71%?&debu#:channel .escription Ena!les &ernel de!ugging to occur o#er 'ort =:UC during the Windows 'E )etup phase, in addition to !eing a#aila!le for the installed operating s stem" Important If ou do not specif a #alue for the channe$, it defaults to 1"
port

The numeric #alue representing the channel to use for de!ugging" baudrate:baudrate 7debu#:port )pecifies the !aud rate to use while transferring data" The default !aud rate is =U788D howe#er, ou can optionall set the !aud rate to =U788,==9788, or 9IB88" Ena!les &ernel de!ugging during the Windows 'E )etup phase, in addition to !eing a#aila!le for the installed operating s stem" Important If ou do not specif a numeric #alue for the port, it defaults to 18.1" )etup does not perform #alidation to #erif that the $OM #alue is a #alid port on the s stem"
port

The numeric #alue representing the $OM port to use for de!ugging" 7m:folder name )pecifies that )etup cop replacement files from an alternate location" Instructs )etup to loo& in the alternate location first, and, if files are present, to use them instead of the files from the default location"
o$der#na&e

7noreboot

The name and location of the folder containing the replacement files" Instructs )etup not to restart the computer after the file cop phase of )etup finishes, so that ou can e2ecute another command"

81

Option 7unattend: Sanswer fileT

.escription 'erforms a clean or upgrade installation of Windows in unattended )etup mode" 0ou can optionall specif a #alue for answer# i$e<
%&ecifies a #alue0 %etu& runs in unattended %etu& mode@ accessin and usin t!e file #alues?

.oes not s&ecif' a #alue0 %etu& runs in unattended %etu& mode@ u& radin 'our currentl' runnin and su&&orted #ersion of Windows? All settin s are ta5en from t!e &re#ious installation@ so minimal to no user inter#ention is re6uired? $or e4am&le@ %etu& re6uires a #alid -roduct Ke' for t!e new o&eratin s'stem? If t!e &re#ious o&eratin s'stem was not installed usin a #alid -roduct Ke'@ %etu& sto&s to &rom&t t!e user for a -roduct Ke'@ and t!en continues until com&letion? answer# i$e

)pecifies the name of the answer file" *or more information a!out answer files, see the /nattend"2ml topic and related topics in the "etup #anager User's Guide" (ote The file name does not need to !e /nattend"2ml" 1owe#er, it must !e created within the )etup Manager tool" E2amples<
.unatten0:c:\setup\unatten0!xml .unatten0:\\ser2er\s9are\unatten0!xml

82

Option 7 tem)dri+e:dri!e letter

.escription Instructs )etup to place temporar files on the specified partition" *or an upgrade, the 7tem)dri+e option affects onl the placement of temporar filesD the operating s stem is upgraded in the partition from which ou run )etup"e2e" )etup esta!lishes two folders during installation<
65indows78bt0 Contains t!e files needed to *oot t!e s'stem@ includin N1 *oot files@ Windows -3@ %etu& files@ and so on?

)etup copies this folder to the !oota!le, acti#e partition on the s stem" The !oot partition requires a minimum amount of hard dis& space to support installation" If there is not enough space, )etup fails and states, ;+ot enough dis& space on our !oot dri#e" *ree dri#e space and tr again;"
65indows78ls0 Contains t!e installation source files@ includin Install?wim?

)etup copies this folder to the partition specified ! this option" The !oot partition requires a minimum amount of hard dis& space to support installation" If there is not enough space, )etup fails and states, ;+ot enough dis& space on our !oot dri#e" *ree dri#e space and tr again;" Important If the specified temporar dri#e is not +T*), )etup con#erts it to +T*)" Additionall , if ou use this option, it will o#erride an Otempdri#eP information that ou included in the /nattend"2ml file"
drive#$etter

The partition to access while !ooting the operating s stem"

/ee Also
W!at is %etu& Mana er> +ow %etu& Mana er Wor5s

Unattend?4ml %ettin s

Unattend.@ml /ettings
*or %eta =, /nattend"2ml can !e used onl to customi4e< .is& configuration /ser data

83

;(un once; commands ?ideo adapter -ogon credentials Auto logon credentials

1ere is the complete /nattend"2ml for %eta =<

;<xml 2ersion=(:!6(> ;unatten0 xmlns=(urn:sc9emas-microsoft-com:asm!2,(> ;settin#s> ;component name=(Setup(> ;Dis3Confi# S9o1?I=> ;Dis3 ID= WipeDis3=> ;&artition "ction=@Create@ La%el= Letter= 4ormat= Si-e= Aype=.> ;&artition "ction=@Bo0ify@ La%el= Letter= 4ormat= &artitionID= Exten0= "cti2e=.> ;.Dis3> ;.Dis3Confi#> ;Ima#eInstall> ;Ima#e> ;InstallAo S9o1?I= Dis3ID= &artitionID= .> ;.Ima#e> ;.Ima#eInstall> ;?serData> ;"cceptEula>;."cceptEula> ;4ullName S9o1?I=>;.4ullName> ;Or#ani-ation S9o1?I=>;.Or#ani-ation> ;ComputerName S9o1?I=>;.ComputerName> ;&ro0uctCey S9o1?I= >;.&ro0uctCey> ;.?serData> ;*unOnce> ;executa%le comman0line= 0escription= .> ;.*unOnce> ;$ar01are> ;Display"0apter 9*es= 2*es= color0ept9= *efres9*ate= .> ;.$ar01are> ;Security> ;DoinDomain S9o1?I= ?serName= &ass1or0= Bac9ineDomain= .> ;"ccounts S9o1?I=> ;"ccount ?serName= &ass1or0= Eroup=.> ;."ccounts> ;.Security> ;"utoLo#on> ;Lo#on ?serName= &ass1or0= Domain= Count= .> ;."utoLo#on> ;?p#ra0eData> ;?p#ra0e S9o1?I=>;.?p#ra0e> ;.?p#ra0eData> ;.component> ;.settin#s> ;.unatten0>

84

/howUI Attri8ute
The S9o1?I attri!ute is common among man of the elements specified and should onl contain #alues of +es or No !ased on whether to show the /I page associated with that attri!ute or not" If there are an other characters other than +es or No, then /nattended )etup will alwa s assume that S9o1?I is equal to No" The default #alue of S9o1?I is No" If the S9o1?I attri!ute is +es and a #alue for the setting is specified, then )etup will show the /I page with the #alue" If the S9o1?I attri!ute is +es and a #alue for the setting is not specified, then )etup will show the /I page with the default #alue" If the S9o1?I attri!ute is No and a #alue for the setting is specified, then )etup will use the #alue specified and not show the /I page" If the S9o1?I attri!ute is No and a #alue for the setting is not specified, then )etup will use the default #alue and will proceed without user input" This has !een ignored for catastrophic errors such as an in#alid dis& configuration or 'roduct Ke " The specification was not clear a!out the appropriate !eha#ior when a default #alue was not possi!le"

?ntit4 6eferen+es in Chara+ter 7ata

Where appropriate, replace the following characters with their entit reference in )tring #alues< O P V F ; VltD VgtD VampD VaposD VquotD

*or e2ample, the password QthisVthat@ will !ecome QthisVampDthat@"

FUser7ataG
The ;?serData> section contains elements for specif ing user settings during )etup" The ;"cceptEula> element replaces OemS3ipEula in the [?natten0e0] section of ) sprep"inf" ;4ullName>, ;Or#ani-ation>, ;ComputerName>, and ;&ro0uctCey> replace the [?serData] section in /nattend"t2t and ) sprep"inf"

85

?@am3le
;?serData> ;F--A9e elements in t9is section contain elements for pre-populatin# en0-user information an0 personali-in# t9e en0-user experience--> ;"cceptEula>;."cceptEula> ;4ullName S9o1?I=>;.4ullName> ;Or#ani-ation S9o1?I=>;.Or#ani-ation> ;ComputerName S9o1?I=>;.ComputerName> ;&ro0uctCey S9o1?I=>;.&ro0uctCey> ;.?serData>

0lement ?serData >serData 0lements "cceptEula

.inimum7.a6imum 8ccurs =H= !y)e 0es or +o .inimum7.a6imum 8ccurs =H=

1omments

De$ault

<en#t" Descri)tion )pecifies whether the end user accepts the -icense Terms for Microsoft )oftware included with Windows" )pecifies the end userWs full name

4ullName

)tring 8 H =

)hell assigns Windows /ser as registered user

BC

Or#ani-ation )tring 8 H =

BC

)pecifies an organi4ationWs name

86

ComputerName )tring = H =

>enerates a random computer name

=9

&ro0uctCey

)tring = H =

7C

)pecifies a computer name" If the #alue is QM@ , a random computer name will !e generated" )pecifies a product &e for each unique installation of windows

?@am3le
;?serData> ;"cceptEula>+es;."cceptEula> ;4ullName S9o1?I=(No@>4a%ri3am ?ser;.4ullName> ;Or#ani-ation S9o1?I=@No@>4a%ri3am;.Or#ani-ation> ;ComputerName S9o1?I=@No@> ;.ComputerName> ;&ro0uctCey S9o1?I=@+es@>::::-7777-,,,,-GGGG-8888;.&ro0uctCey> ;.?serData>

F7isAConfigG
The [Dis3Confi#] section contains entries for configuring and partitioning one or more ph sical hard dis&s" It replaces the [Dis3Confi#] section in the Win!om"ini file" /se this section to configure all hard dis&s on :75!it and BC5!it operating s stems" The format for hard dis&s on :75!it s stems and AM.BC5!it s stems is alwa s the master !oot record (M%()" The format for hard dis&s on Itanium BC5!it operating s stems is alwa s the >/I. 'artition Ta!le (>'T)" ?@am3le
;Dis3Confi# S9o1?I=> ;Dis3 ID= WipeDis3=> ;&artition "ction=@Create@ La%el= Letter= 4ormat= Si-e= Aype=@&rimaryHE4I@ .> ;&artition "ction=@Bo0ify@ La%el= Letter= 4ormat= &artitionID= Exten0= "cti2e=.> ;.Dis3> ;.Dis3Confi#>

87

0lement Dis3Confi#

.inimum7.a6imum 8ccurs =H=

Descri)tion $ontains nested O.is&P elements for configuring and partitioning one or more ph sical hard dis&s

1omments The current implementation supports the following !eha#ior< If the O.is&$onfigP section is not present and the dis& is unpartitioned, then )etup will create one single primar partition and install Windows code5named ;-onghorn; on it" If the dis& is not unpartitioned and !oth the O.is&$onfigP and OImageInstallP sections are not present, then )etup will force a )how/I in all cases" "

Dis/1on$i# 0lement Dis3

.inimum7.a6imum 8ccurs = H un!ounded

Descri)tion The dis& to configure"

88

Dis/ Attributes ID

!y)e )tring

De$ault

<en#t"

Descri)tion )pecifies the dis& to configure" The #alue is a relati#e 85 !ased inde2" )pecifies whether to erase all partitions on the ph sical dis& !efore configuring the dis& with the remaining partition actions" 1omments

1omments

WipeDis3

)tring Q0es@ Q+o@

Q+o@

If WipeDis3 is equal to +es and the first partition action is QModif ,@ then )etup will force a )how/I in all cases"

Dis/ .in7.a6 Descri)tion 0lements 8ccurs &artition = H + $reate new partitions or modif e2isting partitions

The partition actions are performed in the specified order"

89

Partition Attributes ,common"ction

!y)e )tring Q$reate@ QModif @

De$ault

<en#t" Descri)tion The Q$reate@ action is used to create partitions on the dis&" The onl partition t pes that can !e created are 'rimar and E*I s stem partitions" The QModif @ action is used to modif e2isting partitions on the dis&"

1omments On M%( dis&s setup can create up to C primar partitions on the !asic dis&" E#en though !asic dis&s allow for creation of an e2tended partition with logical dri#es unattended )etup will not allow for creation of an e2tended partition" On >'T dis&s, )etup must !e a!le to create as man partitions as are supported" (It is currentl =7J partitions")

La%el Letter 4ormat

)tring )tring Q$5E@ )tring Q0es@ Q+o@ +e2t *ree -etter

)pecifies the #olume la!el to !e assigned" Assigns a dri#e letter to the partition" )pecifies whether to format the partition"

'artitions are alwa s formatted as +T*)"

90

Partition Attributes ,1reate actionSi-e

!y)e

De$ault

<en#t" Descri)tion

1omments

)tring

All a#aila!le space

)pecifies the si4e of the partition in mega! tes

If the dis& is not partitioned and the si4e is not specified, then all a#aila!le space on the dis& will !e used for the partition" There are scenarios (reuse of the /nattend"2ml file for different dis& si4es) where this !eha#ior is desired" If the dis& is partitioned and the si4e is specified, then )etup will allocate the ma2imum contiguous a#aila!le space on the dis& for that partition" If the specified si4e is larger than the free space on the dis&, then )etup will force a )how/I in all cases"

91

Aype

)tring Q'rimar @ Q'rimar @ QE*I@

)pecifies the t pe of the partition

The Q'rimar @ t pe configures the partition as a primar partition" An M%( ph sical dis& can contain onl four primar partitionsD a >'T ph sical dis& can contain up to =7J primar partitions" Windows code5 named ;-onghorn; must !e installed on a primar partition" /nattended )etup will not support con#erting a >'T dis& to an M%( dis& !ecause data can !e lost during con#ersion" The QE*I@ t pe configures the partition as an E)' partition" If an E)' partition alread e2ists either on the same dis& or on another dis&, )etup will not create a second E)' partition" If forci!l

92

Partition !y)e Attributes ,.odi$y action&artitionID )tring

De$ault

<en#t"

Descri)tion

1omments

Exten0

)tring Q0es@ Q+o@

Q+o@

)pecifies the partition to modif " The #alue is a relati#e = !ased inde2" )pecifies whether to e2tend the current partition (specified ! 'artitionI.) to use all a#aila!le space on the dis&"

If the 'artitionI. is in#alid, then )etup will force a )how/I in all cases" )pecif ing E2tend as Q0es@ without specif ing that 'artitionI. will not e2tend the partition" This entr is #alid onl for !asic dis&s" )etup will not e2tend simple #olumes on d namic dis&s"

93

"cti2e

)tring Q0es@ Q+o@

Q+o@

)pecifies whether the current partition (specified ! 'artitionI.) is Acti#e" This informs the !asic inputHoutput s stem (%IO)) or E2tensi!le *irmware Interface (E*I) that the partition or #olume is a #alid s stem partition or s stem #olume"

If an acti#e partition e2ists, )etup will force the change and set the current partition to acti#e" It will not show the /I"

FImageInstallG
The ;Ima#eInstall> section installs an image on a dis& partition" To install the image to a partition, ou must first create the partition and format it with +T*)" ?@am3le
;Ima#eInstall> ;Ima#e> ;F--Dis3ID is a -ero-%ase0 0is3 num%er--> ;InstallAo S9o1?I=> Dis3ID= &artitionID= .> ;.Ima#e> ;.Ima#eInstall>

0lement

.inimum7.a6imum 8ccurs

1omments

94

Ima#eInstall = H =

If the dis& contains partitions, then )etup will #erif if there is a s stem or !oot partition" If there is a s stem or !oot partition, unattended setup will install to the partition as specified in the ;Ima#eInstall> section and then cop all the !oot files (+tldr, %oot"ini, etc") to the !oot partition" If the dis& contains partitions and there is no s stem or !oot partition, unattended setup will set the partition specified in the ;Ima#eInstall> section to which Windows code5named ;-onghorn; is installed as acti#e" 1omments In the a!sence of a 4ileName attri!ute, unattended )etup uses the "wim file from the default wor&ing director where )etup"e2e is launched" 1omments

Ima#eInstall 0lement Ima#e

.inimum7.a6imum 8ccurs =H=

Ima#e 0lement

.inimum7.a6imum 8ccurs

95

InstallAo

8 H un!ounded

.efaultX Install to the first created partition specified in the ;Create&artition> or ;Bo0ify&artition> section" If Dis3ID is specified and &artitionID is not specified, then )etup will install to the first a#aila!le partition on the dis&" If neither is specified, then )etup will #erif if the ;Create&artition> section (is present) and install to created partition" If the ;Create&artition> section is not present, then )etup will stop and log an error" The preferred !eha#ior is to require that !oth Dis3ID and &artitionID !e specified" <en#t" Descri)tion )pecifies the dis& for the image install action" The #alue is a relati#e 85 !ased inde2" )pecifies the partition for the image install action" The #alue is a relati#e =5 !ased inde2"

Install!o Attributes Dis3ID

!y)e )tring

De$ault

&artitionID )tring

96

F/e+urit4G
The ;Security> section contain details a!out 3oining a computer to a domain and creating new user accounts (or adding an e2isting domain user to a group) on the local computer" The ;DoinDomain> section replaces the DoinDomain setting in the [I0entification] section of the /nattend"t2t and ) sprep"inf files" The ;"ccounts> section replaces the [?ser"ccounts] section in the Win!om"ini file" ?@am3le
;Security> ;DoinDomain S9o1?I=> ?serName= &ass1or0= Bac9ineDomain= .> ;"ccounts S9o1?I=@@> ;"ccount ?sername= &ass1or0= Eroup= .> I I ;."ccounts> ;.Security>

0lement Security *ecurity .inimum7.a6imum 0lements 8ccurs DoinDomain 8 H =

.inimum7.a6imum 8ccurs 8H= Descri)tion This section ena!les the computer to participate in a domain" This section ena!les multiple user accounts to !e created on the local computer" 1omments

"ccounts

8H=

Order dependenc < The ;DoinDomain> section must !e processed !efore ;"ccounts>!

97

JoinDomain Attributes ?serName

!y)e )tring

De$ault <en#t" Descri)tion 79B )pecifies the name of a user authori4ed to 3oin the machine to the Bac9ineDomain"" )pecifies the password" )pecifies the domain to which the computer is 3oined" It can !e different from the domain to which the user !elongs"

1omments The format is QusernameYdomain@ or QdomainKuser@" The attri!ute must specif the domain" 'lainte2t passwords are a securit ris&" The attri!ute must specif the domain" An user who has authorit to 3oin the domain can 3oin the computer to the domain" The Bac9ineDomain can !e different from the domain to which the user !elongs"

&ass1or0

)tring

79B 79B

Bac9ineDomain )tring

Accounts 0lement "ccount

.inimum7.a6imum 8ccurs 8 H un!ounded

Descri)tion ;"ccount> creates local accounts or ena!les a domain account to !e added to a user group on the local computer if the computer is 3oined to the domain" )etup will onl add e2isting domain user accounts to the group on the machine" If the group is not specified setup will add the user to the Administrator group" )etup will determine whether the user is a domain user or 3ust a new local user to !e created ! loo&ing at the QY@ or QK@ in the username entr and add them to the specified group" If no username is specified, then an administrator account with a !lan& password will !e created"

98

Account !y)e De$ault Attributes ?serNam )trin e g

<en#t" 79B

Descri)tion )pecifies a unique user account name for a local computer or an e2isting domain user account name" )pecifies a password for the user account" )pecifies a group for the user account"

1omments *ormat can !e Quser@, QuserYdomain@, or QdomainKuser@"

&ass1or 0 Eroup

)trin g

79B

'lainte2ts passwords are a securit ris&" The group must alread e2ist on the machine or !e one of these groups 5 'ower /sersZ AdministratorsZ>uestsZ /sers" The same user cannot !e 3oined to multiple groups"

)trin QAdministrator BC g s@

?@am3le
;Security> ;DoinDomain S9o1?I=@No@> &ass1or0=@secret@ Bac9ineDomain=@nt0e2@.> ;"ccounts S9o1?I=@+es@> ;"ccount ?sername=@nt0e2\user@ &ass1or0=@secret@ Eroup=@&o1er ?sers@ .> ;"ccount ?sername=@localuser@ &ass1or0=@@ Eroup=@"0ministrator@ .> ;."ccounts> ;.Security>

FAutoLogonG
The ;"utoLo#on> section will automaticall log on to the computer using the user account information, and will run the scripts specified in the ;*unOnce> section" It replaces the "utoLo#on and "utoLo#onCount settings in the [Eui?natten0e0] section of the /nattend"t2t and ) sprep"inf files"

99

?@am3le
;"utoLo#on> ;Lo#on ?sername= &ass1or0= Domain= Count= .> ;."utoLo#on>

Auto<o#on 0lement "utoLo#on

.inimum7.a6imum 8ccurs 8H=

1omments Order .ependenc < The ;Security> section must !e processed !efore ;"utoLo#on>! 1omments /ser credentials

Auto<o#on 0lement Lo#on

.inimum7.a6imum 8ccurs 8H=

100

<o#on !y)e Attributes ?serName )tring

De$ault

<en#t" Descri)tion 799 )pecifies the user name" The user can !e an account created in the ;"ccounts> section" If the computer is not 3oined to a domain, then onl local accounts can !e specified" If the computer is 3oined to a domain, then a domain account can !e specified" )pecifies the password )pecifies the domain to which the computer is 3oined or a domain with which there is a trust relationship

1omments )etup does not specif a limit for these lengths, truncate, or log errors" Winlogon appears to limit these #alues to MA,N)T(I+>" /nli&e !eha#ior in pre#ious #ersions of the O'K, the user does not ha#e to !e an administrator"

&ass1or0 )tring Domain )tring $omputer+ame

799 799

'lainte2t passwords are a securit ris&" The use of a .omain attri!ute is inconsistent with other sections where the domain is specified as part of the ?serName< QdomainKusername@"

101

Count

.WO(.

)pecifies the num!er of times that the computer automaticall logs on, using the specified user account and password after manual re!oots

$ount must !e = relati#e, !ecause a count of 8 means that the auto logon is not performed"

?@am3le
;"utoLo#on> ;Lo#on ?sername=@user@ &ass1or0=@secret@ ;."utoLo#on> Domain=@nt0e2@ Count=: .>

F6un0n+eG
The ;*unOnce> section contains commands to e2ecute the first time an end user logs onto the computer after Windows Welcome completes" It replaces the [Eui*unOnce] section in the /nattend"t2t and ) sprep"inf files" ?@am3le
;*unOnce> ;F--A9e elements in t9is section contain comman0s to execute t9e first time a user lo#s on to t9e computer! A9e executa%le runs in t9e context of t9e user t9at is currently lo##e0 on!--> ;Executa%le Comman0Line= Description= .> I I ;.*unOnce>

0lement *unOnce

.inimum7.a6imum 8ccurs 8H=

1omments Order .ependenc < The ;"utoLo#on> section must !e processed !efore ;*unOnce>"

102

Run8nce 0lement Executa%le

.inimum7.a6imum 8ccurs 8 H un!ounded

Descri)tion ;Executa%les> are run in the order listed in the ;*unOnce> section" Each command is s nchronousD it must finish !efore the ne2t command is processed" Descri)tion )pecifies the command to e2ecute, including an arguments 1omments The commands run in the conte2t of the end user currentl logged on" If the user does not ha#e the permissions necessar to run the command, then the application fails" *ailures are not logged"

06ecutable Attributes Comman0Line

!y)e )tring

De$ault

<en#t" ?aria!le

Description

)tring

?aria!le

.ocuments the command

?@am3le
;*unOnce> ;Executa%le Comman0line=(C:\temp\appinstall:\setup!exe .Jn( Description=(application install :(.> ;Executa%le Comman0line=(C:\temp\appinstall7\setup!exe .Jn( Description=(application install 7(.> ;.*unOnce>

103

F9ardwareG
The ;$ar01are> section specifies the displa settings for the #ideo de#ice" It replaces the [Display] section in the /nattend"t2t and ) sprep"inf files and the Display*esolution and Display*efres9 settings in the [ComputerSettin#s] section of the Win!om"ini file" ?@am3le
;$ar01are> ;Display"0apter $*es= )*es= ColorDept9= *efres9*ate= .> ;.$ar01are>

0lement $ar01are

.inimum7.a6imum 8ccurs 8H=

1omments )ee the comment for the ;Display"0apter> element" Descri)tion 1omments The defaults are the lowest resolution accepted ! the #ideo adapter" Descri)tion )pecifies the hori4ontal resolution in pi2els" 1omments The specified resolution and !it depth must !e a #alue supported ! the installed #ideo adapter"

;ard are .inimum7.a6imum 0lement 8ccurs Display"0apter 8 H =

Dis)layAda)ter Attributes $*es

!y)e )tring

De$ault QJ88@

<en#t"

104

)*es

)tring

QB88@

ColorDept9

)tring

Q=B@

*efres9*ate

)tring

QB8@

)pecifies the #ertical resolution in pi2els" )pecifies the num!er of colors in !its per pi2el" )pecifies the refresh rate in megahert4 (M14)"

The specified refresh rate must !e a #alid #alue supported ! the installed #ideo adapter"

?@am3le
;$ar01are> ;Display"0apter $*es=@K66@ )*es=@566@ ColorDept9=@:5@ *efres9*ate=@L6@ .> ;.$ar01are>

FU3grade7ataG
If the upgrade #alue is an other #alue than +es, )etup will assume that a clean installation is intended"
;?p#ra0eData> ;?p#ra0e S9o1?I=>;.?p#ra0e> ;.?p#ra0eData>

0lement ?p#ra0eData

.inimum7.a6imum 8ccurs 8H= .inimum7.a6imum 8ccurs 8H=

>)#rade 0lement ?p#ra0e

105

?@am3le ;?p#ra0eData> ;?p#ra0e S9o1?I=@+es@>+es;.?p#ra0e> ;.?p#ra0eData> .uring upgrades, the other sections are processed as follows< ?serData )etup will inherit the pre#ious ;?serData> settings from the s stem unless the customer o#errides the settings through unattended )etup" %oth ;"cceptEula> and ;&ro0uctCey> are ignored during an upgrade (Windows code5named ;-onghorn; to Windows code5named ;-onghorn;)" This section is ignored" This section should !e ignored" The current !eha#ior is to chec& the .is&I.H'artitionI. for appropriate space, although the #alues are then ignored if the do not match the e2isting primar partition" This section is ignored" This section is processed as usual" This section is processed as usual" This section is ignored"

Dis3Confi# Ima#eInstall

Security "utoLo#on *unOnce $ar01are

/ee Also
W!at is %etu& Mana er> +ow %etu& Mana er Wor5s

/etu3 *anager <e+hni+al 6eferen+e

The )etup Manager tool ena!les Original Equipment Manufacturers (OEMs), corporations, ) stem %uilders, Independent )oftware ?endors (I)?s), and ?alue Added (esellers (?A(s) to manage installation images within their en#ironments" *eatures of )etup Manager ena!le< Offline image editing, including the addition of ser#ice pac&s, hotfi2es, and applications that use the Microsoft Windows Installer ("msi) format" $ustomi4ation of the installation image settings" $reation of an /nattend"2ml file for unattended )etup" Im)ortant )etup Manager does not support the editing of /nattend"2ml files not created with )etup Manager"

106

In <his /e+tion
W!at is %etu& Mana er> +ow %etu& Mana er Wor5s

6elated /e+tions
Confi ure .is5 Confi uration Confi ure )un"nce Commands Confi ure User %ettin s

What is /etu3 *anagerD

The )etup Manager tool ena!les Original Equipment Manufacturers (OEMs), corporations, ) stem %uilders, Independent )oftware ?endors (I)?s), and ?alue Added (esellers (?A(s) to manage installation images within their en#ironments" This topic includes< %enefits of )etup Manager $ommon )etup Manager )cenarios .ependencies of )etup Manager Technologies (elated to )etup Manager

>enefits of /etu3 *anager

This section will descri!e the issues that )etup Manager sol#es for OEMs, corporations, ) stem %uilders, I)?s, and ?A(s"

Common /etu3 *anager /+enarios

)etup Manager is the program that ena!les ou to create the /nattend"2ml file, which wor&s with )etup to install or upgrade to Windows code5named ;-onghorn"; The most common scenarios for using )etup Manager include performing an unattended )etup" Creating and Using the Unattend.@ml 2ile This section will descri!e the high5le#el scenario of creating and performing an unattended )etup"

7e3enden+ies of /etu3 *anager

%efore ou !egin to use )etup Manager to ena!le offline image editing, the customi4ation of the installation image settings, and the creation of an /nattend"2ml file for unattended )etup, ou must<

107

=" 'repare our new hardware and software" This includes assem!ling the hardware for the computers that ou will distri!ute to our customer and identif ing an additional dri#ers and applications for installation" 7" 'repare the technician computer" This includes installing the OEMHWindows Automated Installation Kit (WAIK) tools, including )etup Manager" (ote If ou ha#e alread created a new configuration set, ou can modif or delete our configuration settings within )etup Manager"

<e+hnologies 6elated to /etu3 *anager

Unattend.@ml /nattend"2ml is the answer file for )etup, created with the )etup Manager utilit " This file ena!les the addition and remo#al of components, the configuration of the offline installation, and the completion of )etup5related tas&s, such as dis& configuration" Additionall , /nattend"2ml ena!les ou to configure multiple components within a single, unified file" 4ote /nattend"2ml replaces the /nattend"t2t file from pre#ious #ersions of MicrosoftG Windows" Windows /etu3 (/etu3.e@e) )etup is the program that ena!les the installation, upgrade, and configuration of MicrosoftG Windows code5named ;-onghorn"; )etup is also the !asis for the following non5interacti#e installation and upgrade methods< unattended )etup, Windows .eplo ment )er#ices (W.)), and image5 !ased installation with the ) stem 'reparation () sprep) tool"

/ee Also
+ow %etu& Mana er Wor5s Confi ure .is5 Confi uration Confi ure )un"nce Commands Confi ure User %ettin s

9ow /etu3 *anager WorAs

The )etup Manager tool ena!les Original Equipment Manufacturers (OEMs), corporations, ) stem %uilders, Independent )oftware ?endors (I)?s), and ?alue Added (esellers (?A(s) to manage installation images within their en#ironments"

108

This topic pro#ides an in5depth re#iew of )etup Manager, including< )etup Manager Terms and .efinitions )etup Manager Architecture )etup Manager )cenarios

/etu3 *anager <erms and 7efinitions

The following terms are associated with )etup Manager"
'erm +e%inition

answer file

configuration set

destination computer

distri!ution ser#er distri!ution share

A script file that automates )etup"e2e" This file ena!les the configuration of offline installations, the addition and remo#al of components, and man of the )etup5related tas&s, such as dis& configuration" The complete collection of files, dri#ers, applications, patches, and answer files installed during )etup" 0ou can create, cop , edit, and delete configuration sets, as needed" The computer on which ou install the operating s stem" *or Windows code5named ;-onghorn,; this is the computer to which ou cop our customi4ed installation image" The computer that contains our installation images for application to destination computers" A networ& share that contains our source files and custom answer files used ! each installation image"

109

'erm

+e%inition

E2tensi!le *irmware Interface (E*I)

master computer master installation image

offline installation

online installation

)etup"e2e technician computer

A specification, primaril intended for IA5:7 and Itanium architecture5!ased computers" It pro#ides a standard for the interface !etween an operating s stem and platform firmware (a com!ination of software and hardware)" The E*I interface includes data ta!les with platform5related information, in addition to !oot and runtime ser#ice calls that are a#aila!le to the operating s stem and its loader" $ollecti#el , the ta!les and calls pro#ide a standard en#ironment for !ooting an operating s stem and running pre5!oot applications" The computer that contains our master installation image" $onsists of our installed and configured operating s stem, in addition to an additional software applications, updated dri#ers, and so on, for application to destination computers" An installation created ! !uilding components from a repositor to a specified, temporar location" The component files are copied to desired locations, the registr entries are written to hi#e files, and an offline configura!le settings are set" The installation is read for application to a destination s stem and the first5!oot phase" An offline installation, applied and !ooted from a destination computer" $onfiguration of the components occurs online, which ma&es the installation unique to the destination computer" The tool that prepares our hard dis&, applies the installation image, and ena!les the addition and remo#al of components" The computer used to create and modif our answer files"

110

'erm

+e%inition

/nattend"2ml

unattended installation Windows Imaging ("wim) file Windows 'reinstallation En#ironment (Windows 'E)

The answer file that automates )etup"e2e" This file ena!les the configuration of offline installations, the addition and remo#al of components, and man of the )etup5related tas&s, such as dis& configuration" The non5interacti#e method of performing )etup ! using an answer file and installation images" A file5!ased imaging format that contains one or more #olume images" Windows 'E is a minimal Windows operating s stem with limited ser#ices, !uilt on the Windows &ernel" It contains the minimal functionalit that ou need to run Windows )etup, install Windows from a networ& share, automate !asic processes, and perform hardware #alidation"

/etu3 *anager Ar+hite+ture

This section will discuss the architecture of )etup Manager, including how it interacts with the /nattend"2ml file and )etup"e2e"

/etu3 *anager /+enarios

This section will discuss the t pical scenarios for using )etup Manager" Creating an Unattend.@ml 2ile This scenario will discuss creating the /nattend"2ml file ! using )etup Manager"

/ee Also
W!at Confi Confi Confi is %etu& Mana er> ure .is5 Confi uration ure )un"nce Commands ure User %ettin s

/4s3re3 <e+hni+al 6eferen+e

The ) stem 'reparation () sprep) tool is a technolog that ou can use with other deplo ment tools to install MicrosoftG WindowsG operating s stems on new

111

hardware" ) sprep prepares a computer for dis& imaging or deli#er to a customer ! configuring the computer to create a new computer securit identifier ()I.) when the computer is restarted" In addition, ) sprep cleans up user5specific and computer5specific settings and data that must not !e copied to a destination computer"

In this /e+tion
W!at is %'s&re&> +ow %'s&re& Wor5s %'s&re& 1ools and %ettin s

What is /4s3re3D
The ) stem 'reparation tool, ) sprep"e2e, is a deplo ment tool that ou can use to install identical configurations on multiple computers" 0ou can also use ) sprep to customi4e and automate Windows Welcome and to audit computers" ) sprep prepares a computer for dis& imaging or deli#er to a customer ! configuring the computer to create a new computer securit identifier ()I.) when the computer is restarted" In addition, ) sprep remo#es user5specific and computer5specific settings and data that must not !e copied to a destination computer" The ma3or ad#antage of ) sprep installation is speed" The image can !e pac&aged and compressedD onl the files required for the specific configuration are created as part of the image" The shortened >/I5mode )etup can ta&e fi#e or si2 minutes instead of C9 to B8 minutes, and prompts the user onl for required and user5specified information, such as accepting the -icense Terms for Microsoft )oftware, entering the 'roduct Ke , and adding user and compan names" This topic includes< %enefits of ) sprep $ommon ) sprep )cenarios -imitations of ) sprep .ependencies of ) sprep Technologies (elated to ) sprep (elated Information

>enefits of /4s3re3
/sing ) sprep pro#ides man !enefits, for e2ample, ) sprep< (esets Windows 'roduct Acti#ation, up to three times" 1elps OEMs to compl with OEM licensing requirements ! resetting the -icense Terms for Microsoft )oftware on the ne2t !oot of the computer"

112

$reates a new computer securit identifier ()I.) when the computer is restarted" Ena!les image5!ased installations ! creating a generic installation that can !e captured with an imaging tool" Ena!les factor floor customi4ation and testing"

Common /4s3re3 /+enarios

) sprep is commonl used in the following scenarios< /imilar hardware +onfigurations If ou install the same configuration on computers that ha#e similar hardware, ou can customi4e hardware configurations on the dis& image, a#oiding man post5installation configuration and installation tas&s" *or e2ample, ou can use Image5!ased )etup with ) sprep to rapidl deplo the same computer configuration to a group of computers that ha#e similar processor configurations and similar storage configurations" 6a3id 7e3lo4ment If ou must install the operating s stem as rapidl as possi!le, ou can cop a preconfigured dis& image onto a destination computer much faster than ou can perform a manual installation" A33li+ation de3lo4ment To deplo applications at the same time that ou deplo the operating s stem, ou can include the applications on the dis& image" *or e2ample, if our organi4ationWs standard computer configuration includes an anti#irus program, an e5mail program, and an office application suite, ou can install and configure these programs on the master installation so that the dis& image includes these programs" C7,8ase Installations If ou install the operating s stem ! using the Windows product .?., ) sprep remo#es user5specific and computer5specific settings and data that our customer must not see" In addition, to help OEMs compl with their OEM licensing agreement, ) sprep resets Windows Welcome so customers can accept the -icense Terms for Microsoft )oftware"

113

Limitations of /4s3re3
) sprep has the following limitations< ) sprep can run onl on dri#e $" 0ou must alwa s use the #ersion of ) sprep that corresponds to the #ersion of the Windows operating s stem that ou deplo " If ou deplo a ser#ice pac&, use the #ersion of ) sprep released with that specific ser#ice pac&" The reference and destination computers must ha#e compati!le hardware a!straction la ers (1A-s)" *or e2ample, Ad#anced 'rogramma!le Interrupt $ontroller (A'I$)[!ased M') (multiprocessor s stems) must use the same A'I$ 1A-" A standard 1A- 'rogramma!le Interrupt $ontroller ('I$)[!ased s stem is not compati!le with either the A'I$ 1A- or the M') 1A-" The master and destination computers must ha#e identical Ad#anced $onfiguration and 'ower Interface (A$'I) support" The 'lug and 'la de#ices on the technician and destination computers, such as modems, sound cards, networ& adapters, and #ideo cards, do not ha#e to !e from the same manufacturer" 1owe#er, the dri#ers for these de#ices must !e a#aila!le" The cloc& for Windows 'roduct Acti#ation !egins its countdown the first time Windows starts" 0ou can use ) sprep for a ma2imum of three times to reset the cloc& for Windows 'roduct Acti#ation" After the third time ou run ) sprep, the cloc& can no longer !e reset" ,Image, third5part dis&5imaging software, or dis&5duplicating hardware de#ices are required for Image5%ased )etup" These products create !inar images of a computerFs hard dis& and either duplicates the image to another hard dis& or stores the image in a file on a separate dis&" The si4e of the hard dis& on the destination computer must !e at least the same si4e as the hard dis& on the technician computer" ) sprep runs onl if the computer is a mem!er of a wor&group, not a domain" If the computer is 3oined to a domain, ) sprep remo#es it from the domain" If ou run ) sprep on an +T*) file s stem partition that contains encr pted files or folders, the data in those folders !ecomes completel unreada!le and unreco#era!le"

7e3enden+ies of /4s3re3
) sprep has the following dependencies<

114

The ) sprep tool consists of three separate programs< ) sprep"e2e, )etupcl"e2e, and *actor "e2e" )etupcl"e2e and *actor "e2e are secondar programs that ) sprep"e2e runs as needed" 0ou need an imaging tool, li&e ,Image, to capture an image of the installation" /sing the )etup Manager tool, ou can script ) sprep configurations during unattended )etup"

<e+hnologies 6elated to /4s3re3

The following technologies are related to ) sprep< 5Image ,Image is a command5line tool that ena!les Original Equipment Manufacturers (OEMs) and corporations to capture, modif , and appl file5!ased dis& images for rapid deplo ment" ,Image wor&s with Windows Imaging (WIM) images for cop ing directl to destination computers, or it can wor& with other technologies that use the WIM images, such as )etup for Windows code5named ;-onghorn,; Windows .eplo ment )er#ices (W.)), Automated .eplo ment )er#ices (A.)), and the )M) Operating ) stem *eature .eplo ment 'ac&" $orporations that do not require the capture functionalit or the low5le#el features included in ,Image can still use related technologies such as unattended )etup, >roup 'olic , and ) stems Management )er#er ()M))" Windows ;rodu+t A+ti1ation Windows 'roduct Acti#ation (W'A) reduces Windows pirac ! ensuring compliance with the -icense Terms for Microsoft )oftware" In product acti#ation, the 'roduct Ke is matched with the indi#idual computer on which the software is installed" It does this ! #alidating the 'roduct Ke , and chec&s that it has not !een used with more than the licensed num!er of computers" An end user has :8 da s from the initial !oot of the computer to acti#ate the installation" The end user can acti#ate the installation ! using the Internet or the telephone" The computer manufacturer can also prepopulate the unique 'roduct Ke from the $ertificate of Authenticit ($OA) stic&er on the specific computer, and acti#ate the computer on !ehalf of the end user" Windows /etu3 Windows )etup is the program that ena!les ou to install or upgrade to Windows code5named ;-onghorn"; )etup is also the !asis for the following non5interacti#e installation and upgrade methods< unattended )etup, Windows .eplo ment

115

)er#ices (W.)), and Image5!ased )etup with the ) stem 'reparation tool () sprep)" /etu3 *anager )etup Manger pro#ides a complete solution for managing images of the operating s stem" The solution ena!les iterati#e offline image editing, the customi4ation of image settings, the creation of an answer file (/nattend"2ml), and the simplification of the entire creation, pu!lishing, and deplo ment process to destination computers, reducing the time to mar&et for customers" Unattend.@ml /nattend"2ml is the answer file for )etup, created with the )etup Manager tool" 0ou can also use /nattend"2ml to automate specific ) sprep actions" The /nattend"2ml file replaces the pre#ious ) sprep"inf file"

/ee Also
+ow %'s&re& Wor5s %'s&re& 1ools and %ettin s

9ow /4s3re3 WorAs

The ) stem 'reparation tool, ) sprep"e2e, is a deplo ment tool that ou can use to install identical configurations on multiple computers" 0ou can also use ) sprep to customi4e and automate Windows Welcome and to audit computers" ) sprep is commonl used in Image5!ased )etup, a method of cop ing or cloning preconfigured operating s stems and software applications onto destination computers" Image5!ased )etup is the fastest method of installing an operating s stem and applications, and is t picall used during large5scale rollouts when it is too slow and costl to ha#e administrators or technicians interacti#el install the operating s stem on indi#idual computers" This topic includes< ) sprep Architecture ) sprep 'rocesses

/4s3re3 Ar+hite+ture
) sprep relies on se#eral components, including three e2ecuta!le programs () sprep"e2e, )etupcl"e2e, and *actor "e2e") and an answer file (/nattend"2ml)" ) sprep"e2e is the main e2ecuta!le file that calls )etupcl"e2e and *actor "e2e as appropriate" 0ou cannot run )etupcl"e2e and *actor "e2e independentl "

116

These components run on !oth the master computer\the computer on which ou create our master installation\and the destination computer\the computer on which ou install a dis& image" An answer file (/nattend"2ml) is created on a technician computer, and is used on the master computer and the destination computer when ) sprep and its associated components run" The dis& imaging tool runs on the master computer, where it is used to create a dis& image, and on the destination computer, where it is used to cop a dis& image from a $. or a remote ser#er onto the destination computerWs hard dis&" The following are components used in Image5!ased )etup with ) sprep< $omponent .estination computer .escription The computer on which ou install an operating s stem" *or Image5!ased )etup, this is the computer to which ou cop a dis& image" .uring a large5scale rollout, there can !e t picall hundreds or thousands of destination computers" *unctionall identical replica of a hard dis& that can !e copied onto multiple computers" 0ou need a dis&5imaging tool to create a dis& image" 'rogram that creates and manages dis& images" 0ou use the dis&5imaging tool on the master computer to create a dis& image and sa#e the dis& image to a $., .?., or a remote ser#er" 0ou use the dis&5imaging tool on the destination computer to cop the dis& image from a $., .?., or remote ser#er to the destination computerWs hard dri#e" 0ou can license Microsoft ,Image or a non5 Microsoft dis&5imaging program to perform Image5!ased )etup with ) sprep" The computer that contains the dis& images that ou cop onto destination computers" A component of ) sprep that controls the *actor 5mode stage of Image5!ased )etup with ) sprep" 0ou can configure ) sprep so that a destination computer starts in *actor mode" *actor mode puts a destination computer into a networ&5ena!led state that ena!les ou to perform installation and configuration tas&s !efore ou prepare the destination computer for final deli#er to customers" *actor "e2e must e2ist in the same folder on the master computer as )etupcl"e2e and ) sprep"e2e, which is t picall the s stemdri#eK) sprep folder"

.is& image .is&5imaging tool

.istri!ution share *actor "e2e

117

$omponent Master computer

(egistr

)etupcl"e2e

)etup Manager

) sprep"e2e

Technician computer /nattend"2ml

.escription The computer from which a dis& image is deri#ed" A master computer contains a master installation, which is the s stem dis& on which ou installed and configured the operating s stem and software applications that ou plan to install onto the destination computers in our organi4ation" The repositor where ) sprep stores configuration and )etup information prior to the dis& imaging process" ) sprep reads the configuration and )etup information from this repositor the first time a destination computer starts after deli#er to a user" A component of ) sprep that resets securit identifiers ()I.s) on the master computer !efore running a dis&5 imaging tool and creating a dis& image of the master computerWs s stem dis&" )etupcl"e2e can also run at the end of the *actor 5mode stage if ou run ) sprep with the *actor mode option" )etupcl"e2e must e2ist in the same folder on the master computer as *actor "e2e and ) sprep"e2e, which is t picall the s stemdri#eK) sprep folder" A deplo ment tool that creates an answer file (/nattend"2ml), which includes settings for ) sprep" 0ou use )etup Manager on the technician computer, and then transfer the answer file to the master computer !efore creating the dis& image" A primar ) sprep component" 0ou run ) sprep"e2e on the master computer !efore running a dis&5imaging tool to create a dis& image" ) sprep"e2e also runs automaticall after ou cop a dis& image to a destination computer and then start the destination computer for the first time" ) sprep"e2e can !e run at a command prompt or it can !e run in the Windows graphical user interface (>/I)" ) sprep"e2e must e2ist in the same folder on the master computer as )etupcl"e2e and *actor "e2e, which is t picall the s stemdri#eK) sprep folder" The computer on which an administrator or technician uses )etup Manager to create and modif answer files, such as the /nattend"2ml file" An answer file that can !e used to automate Windows )etup"

118

/4s3re3 ;ro+esses
) sprep configures #arious operating s stem settings on the master computer to ensure that e#er cop of the master computerWs dis& image is unique when ou distri!ute it to a destination computer" )pecificall , ) sprep configures a master installation (and, thus, the dis& image of that master installation) so that a unique computer securit identifier ()I.) is generated on each destination computer" A )I. is a #aria!le length data structure that identifies a user, a group, or a computer" Internal processes in Windows refer to the )I. instead of the computer name or user name or group name" ) sprep resets )I.s ! running )etupcl"e2e, which is a component of ) sprep" 0ou can also use ) sprep to configure the master computerWs dis& image so that e#er destination computer starts in a special intermediate )etup mode &nown as *actor mode" *actor mode is controlled ! *actor "e2e and is commonl used in a manufacturing en#ironment where e#er computer requires some customi4ation prior to final deli#er D howe#er, it is also useful for some corporate deplo ments" 0ou can use *actor mode to customi4e indi#idual computers or groups of computers after cop ing a dis& image onto a destination computer !ut !efore Windows Welcome runs" *or e2ample, *actor mode gi#es ou the a!ilit to update dri#ers, run 'lug and 'la enumeration, install applications, test hardware and software, and configure computer settings"
*unning Sysprep 9reseal

When ou run sysprep .reseal, ) sprep< $lears an registr &e s and settings that must !e unique, such as Internet connection settings and MicrosoftG Media 'la erL I.s" /ses )etupcl"e2e to reset the securit I.s ()I.s) the ne2t time the operating s stem restarts, !efore Windows Welcome" $loses networ& connections" $onfigures Windows Welcome" $lears an s stem restore points" (esets the time cloc& for Windows 'roduct Acti#ation, if the time cloc& has not alread !een reset three times" .eletes e#ent logs and a list of most recentl used documents, applications, and We! sites"

/ee Also
W!at is %'s&re&> %'s&re& 1ools and %ettin s

119

/4s3re3 <ools and /ettings

This topic descri!es the tools and settings related to ) sprep"

/4s3re3 <ools
The following tools are associated with image5!ased installations with ) sprep" /etu3 *anager Utilit4 (setu3mgr.e@e) )etup Manager is a program that helps ou configure distri!ution shares and answer files that can !e used to perform automated installations, including unattended )etup and Image5!ased )etup with ) sprep" Windows /etu3 (setu3.e@e) )etup is the program that ena!les the installation, upgrade, and configuration of MicrosoftG Windows code5named ;-onghorn"; )etup is also the !asis for the following non5interacti#e installation and upgrade methods< unattended )etup, Windows .eplo ment )er#ices (W.)), and Image5 !ased )etup with the ) stem 'reparation () sprep) tool"

/4s3re3 Command,Line 03tions

The following command5line options are a#aila!le for ) sprep< *ys)re)5e6e S7resealT S7rebootH 7s"utdo n H 7@uitT ]7ima#e^ ]7@uiet^ Option 7ima#e 7reboot .escription 'repares the installation for imaging" *orces the computer to restart automaticall and then start Mini5)etup or enter *actor mode, as specified" This is useful when ou want to audit the computer and #erif that the first5 run e2perience operates correctl " $onfigures Windows code5named ;-onghorn; to use Windows Welcome the ne2t time the computer !oots" )huts down the computer after ) sprep finishes" /se this option if our computers ha#e an A$'I %IO) that does not shut down properl with the ) sprep default settings" (uns ) sprep without displa ing onscreen confirmation messages" This is useful if ou automate ) sprep" *or e2ample, if ou plan to run ) sprep immediatel after unattended )etup" )huts down the computer after ) sprep finishes" This is the default action if no options are set"

7reseal 7s"utdo n 7@uiet 7@uit

120

/ee Also
W!at is %'s&re&> +ow %'s&re& Wor5s

5Image <e+hni+al 6eferen+e

,Image is a command5line tool that uses a set of A'Is, &nown as Windows Imaging A'I (WIM>A'I), to perform tas&s with the Microsoft Windows Imaging ("wim) files" The "wim files contain one or more #olume images for a Windows operating s stem, while a #olume image represents the captured #olume or partition of a Windows operating s stem" The primar purpose of ,Image is to capture, modif , and appl images for deplo ment in a manufacturing or corporate IT en#ironment" 0ou t picall use ,Image with the Windows Imaging *ile ) stem *ilter (WIM *) *ilter) dri#er" The WIM *) *ilter dri#er ena!les ou to mount an image to a director , where ou can !rowse, cop , paste, and edit the files from a file management tool, such as Windows E2plorer, without e2tracting or recreating the image"

In this /e+tion
W!at is (Ima e> +ow (Ima e Wor5s (Ima e Command-Line "&tions

6elated /e+tions
Confi uration $ile Creation Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e Wal5t!rou !0 Mount and Modif' an Ima e Wal5t!rou !0 A&&l' a .e&lo'ment Ima e

What is 5ImageD
,Image is a command5line tool that ena!les Original Equipment Manufacturers (OEMs) and corporations to capture, modif , and appl file5!ased dis& images for rapid deplo ment" ,Image wor&s with Windows Imaging ("wim) images for cop ing to a networ&, or it can wor& with other technologies that use the "wim images, such as )etup for Windows code5named ;-onghorn,; Windows .eplo ment )er#ices (W.)), and the )M) Operating ) stem *eature .eplo ment 'ac&"

121

$orporations that do not require the capture functionalit or the low5le#el features included in ,Image can still use related technologies such as unattended )etup, >roup 'olic , and ) stems Management )er#er ()M))" This topic includes< %enefits of ,Image $ommon ,Image )cenarios -imitations of ,Image .ependencies of ,Image Technologies (elated to ,Image (elated Information

>enefits of 5image
Man OEMs and corporations need to deplo and install Windows as rapidl as possi!le, including all rele#ant updates, applications, and settings" (educed deplo ment and installation time lower manufacturing costs for OEMs, and can decrease cost and scheduling ris& for corporate deplo ments" In the past, if OEMs and corporations wanted to minimi4e the amount of time required to install Windows, the had to use sector5!ased imaging formats, or the M)5.O) 6co)y command, to cop an installation of Windows onto new hardware" The sector5!ased imaging format and the M)5.O) 6co)y command can ha#e a num!er of limitations< )ector5!ased imaging requires that the destination computer use the same 1ardware A!straction -a er (1A-) as the master computer" )ector5!ased imaging requires that the destination computer !oot from the same mass5storage controller as the master computer" )ector5!ased imaging destro s the e2isting contents of the destination computerWs hard dri#e, complicating Windows deplo ment scenarios" )ector5!ased imaging duplicates the hard dri#e e2actl D therefore, the image can deplo onl on partitions that are the same t pe as the master computer, and are at least as large as the partition on the master computer" )ector5!ased imaging does not ena!le direct modification of imaged files" )ector5!ased imaging ma require the purchase of third5part applications and ser#ices" The limitations of sector5!ased imaging led Microsoft to de#elop ,Image and the accompan ing Windows Image file5!ased image format" 0ou can use ,Image to create an image, modif the image without going through the e2traction and re5 creation process, and finall deplo the image to our en#ironment, all from

122

within the same tool" %ecause ,Image wor&s at the file le#el, it pro#ides the following capa!ilities< More fle2i!ilit and control o#er the deplo ed media" (apid e2traction of images to decrease setup time" A reduction in image si4e due to ;single instancing,; which means that the file data is stored separatel from the path information" This ena!les files that e2ist in multiple paths or in multiple images to !e stored once, and shared across the images" +on5destruction application of images" ,Image does not perform an all5 inclusi#e o#erwrite of the contents of our dri#e" 0ou can selecti#el add and remo#e information" The a!ilit to wor& across an platform supported ! Windows" Two different compression algorithms, *ast and Ma2imum, to further reduce our image si4e" The a!ilit to treat an image file li&e a director " *or e2ample, ou can add, cop , paste, and delete files from a file management tool, such as Windows E2plorer"

Common 5Image /+enarios

,Image is a command5line tool that ena!les the creation, modification, and deplo ment of images, ! using a shared imaging format across operating s stem images, including applications" The following scenarios are particularl compati!le with the ,Image process" Creating an Image for 6a3id 7e3lo4ment The most common scenario for ,Image is capturing and appl ing an image from a networ& location for rapid deplo ment" This scenario requires !ooting our technician computer into Windows 'E, capturing the image using ,Image, putting the image on a networ& share, and then appl ing the image to the destination computers" *odif4ing an Image 2ile Another common scenario for ,Image is customi4ing an e2isting image, including updating files and folders" This scenario in#ol#es adding, remo#ing, editing, and cop ing files from our image using the WIM *) *ilter dri#er and a file management tool, such as Windows E2plorer"

123

Limitations of 5Image
,image has the following limitations< 0ou can use ,Image onl to capture and appl a full #ersion of the operating s stem and software applications" 0ou cannot use ,Image to capture and appl upgrades to the operating s stem or applications" 0ou can use onl Windows Imaging formatted images to interact with ,Image" 're#ious images, created with third5part imaging tools, cannot !e used with ,Image" 0ou can use onl a single compression t pe for a "wim file" Appended image files must use the same compression t pe as the initial capture" 0ou can mount an image onl from MicrosoftG Windows ,'G with )er#ice 'ac& 7 ()'7), MicrosoftG Windows )er#er 788:G with )er#ice 'ac& = ()'=), or MicrosoftG Windows code5named ;-onghorn"; 4ote Although ,Image cannot mount an image from a computer running an other operating s stem, it can capture and appl images for an #ersion of Microsoft Windows code5named ;-onghorn,; Microsoft Windows )er#er 788:, Microsoft Windows ,', and Microsoft Windows 7888" 0ou can mount a "wim file with readHwrite permissions onl on an +T*) file s stem" This a#oids the 75giga! te (>%) !arrier imposed ! *AT file s stems and pre#ents data loss that is possi!le with *AT or other non5+T*) file s stems" 4ote Although ,Image can mount a "wim file with readHwrite permissions onl from an +T*) file s stem, ou can mount our image as read5onl from +T*), *AT, I)O, and /.* file s stems" 0ou cannot sa#e changes to the image file while it is mounted as read5onl " 0ou must use other Microsoft tools, such as .is&part and *ormat, to prepare our dis&s for #olume images"

7e3enden+ies of 5Image
,Image has the following dependencies" /sing the )etup Manager, ou ma create an installation image, which will ou will capture later using ,Image"

124

/sing the ) sprep tool, ou ma prepare and clean our data for capture ! ,Image" (unning ) sprep on our master computer remo#es all user5 specific and computer5specific settings and data, resets the product acti#ation cloc& to :8 da s, and ena!les the creation of a new securit identifier ()I.) upon restart" Once ou ha#e run ) sprep, ou can !oot our master computer into the Windows 'reinstallation En#ironment (Windows 'E) to capture the image" 0ou must !oot our technician computer into the Windows 'E en#ironment" *rom Windows 'E, ou ma run ,Image to capture our image" After ou create the image, !oot our technician computer, install the Windows Imaging *ile ) stem *ilter (WIM *) *ilter) dri#er, edit our image, and appl it from a networ& location"

<e+hnologies 6elated to 5Image

,Image is related to the following technologies< Windows 7e3lo4ment /er1i+es (W7/) If ou do not use ,Image for deplo ment, ou ma use Microsoft Windows .eplo ment )er#ices (W.))" W.) ena!les companies to remotel administer and deplo the latest operating s stem and other "wim files, using Windows 'E and W.) )er#er" This deplo ment scenario can !e full unattended, and is customi4a!le and scala!le" 4ote Windows .eplo ment )er#ices replaces the e2isting (emote Operating ) stem Installation ((I)) deplo ment technolog " /4stems *anagement /er1er (/*/) 03erating /4stem 7e3lo4ment 2eature ;a+A If ou do not use ,Image for deplo ment, ou ma use the ) stems Management )er#er ()M)) Operating ) stem .eplo ment *eature 'ac&" The )M) Operating ) stem .eplo ment *eature 'ac& ena!les companies to deplo the latest operating s stems and applications in a customi4a!le, centrali4ed, and scala!le wa " *or more information, refer to htt3=IIwww.mi+rosoft.+omIsmser1er"

/ee Also
+ow (Ima e Wor5s (Ima e Command-Line "&tions Confi uration $ile Creation Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e

125

Wal5t!rou !0 Mount and Modif' an Ima e Wal5t!rou !0 A&&l' a .e&lo'ment Ima e

9ow 5Image WorAs

,Image is a command5line tool that uses a set of A'Is, &nown as Windows Imaging A'I (WIM>A'I), to perform man tas&s with the Microsoft Windows Imaging ("wim) files" The primar purpose of ,Image is to capture, modif , and appl images for deplo ment in a manufacturing or corporate IT en#ironment" 0ou t picall use ,Image with the Windows Imaging *ile ) stem *ilter (WIM *) *ilter) dri#er" The WIM *) *ilter dri#er ena!les ou to mount an image as if it were a director and !rowse, cop , paste, and edit the files from a file management tool, such as Windows E2plorer, without e2tracting or recreating the image" This topic includes< ,Image Terms and .efinitions ,Image Architecture

5Image <erms and 7efinitions

The following ta!le presents the most common terms and definitions used ! ,Image"
'erm +e%inition

,Image

?olume Image Windows Imaging *ile ("wim) )plit Windows Imaging *iles ("swm) Windows Imaging A'Is (WIM>A'I)

A command5line tool utili4ing the Windows Imaging file structure to capture, modif , and appl an image to our networ& or destination computers" The captured image file" One or more #olume image(s) constitute a Windows Imaging ("wim) file" A file5!ased imaging format, which contains one or more #olume images" A collection of read5onl files, which contain one or more #olume images of a Windows s stem, captured using ,Image" An A'I set used ! ,Image for capturing and appl ing images to our networ& or destination computers"

126

'erm

+e%inition

*ile5!ased Imaging

)ector5!ased Imaging )ingle Instancing

WIM *ile ) stem *ilter (WIM *) *ilter) .ri#er

The process of capturing information at the file le#el into a single #olume, with metadata descri!ing the files" Also &nown as single instancing" The process of capturing e#er non5!lan& sector into a ph sical file" This is not the process used ! ,Image" The process of storing the file data separatel from the path information, with the path information stored as image metadata" A dri#er that ena!les ou to mount our image file and wor& with it through a file management tool, such as Windows E2plorer"

5Image Ar+hite+ture
,Image relies on se#eral components, including the ,Image e2ecuta!le (2image"e2e), the WIM *ile ) stem *ilter (wimfltr"inf), the WIM A'I set (WIM>A'I), and the "wim file format" The following diagram shows the interaction !etween these components"

127

Component

+escription

,Image"e2e

An e2ecuta!le that uses an A'I la er to support interaction with the "wim file" This interaction includes capturing our image, compressing our image, mounting and unmounting our image, appl ing our image, and so on"

128

Component

+escription

WIM *ile ) stem *ilter

Once ou install the WIM *) *ilter dri#er, the WIM *ile ) stem *ilter handles the !rowsing and editing capa!ilities for the "wim file" After ou mount a "wim file to a director , the filter monitors all file s stem requests for files or data and maps the requests to the appropriate data within the "wim file" This ena!les ou to #iew the contents of our image file from an standard file management tool, such as Windows E2plorer" Additionall , the offline ser#icing of our image ena!les ou to #iew and edit our "wim files without ha#ing to reappl and recapture the image" To mount and edit the contents of our "wim file, a user5mode tool and a &ernel5mode file s stem filter interact with each other using a communication protocol and the WIM A'I set" WIM A'I )et (WIM>A'I) The A'I la er that interacts with !oth the ,Image e2ecuta!le and the WIM *) *ilter dri#er" It is also the primar interface for third part tools and setup technolog " The A'Is can !e categori4ed into the following groups< AddHupdateHremo#e file data AddHupdateHremo#e image data E2tract image data Mounting an Image using the WIM *ile ) stem *ilter )panning of images Messaging status and progress Windows Imaging ("wim) A collection of image files that contain an operating file s stem and its components" ,Image uses the "wim file format for the capture, offline ser#icing, and the deplo ment process, pro#iding a comprehensi#e imaging solution for our deplo ment scenarios"

/ee Also
W!at is (Ima e> (Ima e Command-Line "&tions Confi uration $ile Creation

129

Wal5t!rou Wal5t!rou Wal5t!rou Wal5t!rou

!0 !0 !0 !0

Ca&ture an Ima e Com&ress an Ima e Mount and Modif' an Ima e A&&l' a .e&lo'ment Ima e

5Image Command,Line 03tions

,Image is a command5line tool in Windows code5named Q-onghorn,@ that ou can use to create and manage Microsoft Windows Imaging ("wim) files" A "wim image file contains one or more #olume images, dis& #olumes that contain images of an installed Windows operating s stem" To modif our #olume images, ou must install the Windows Imaging *ile ) stem *ilter (WIM *) *ilter) dri#er on a computer running Microsoft Windows ,' with )er#ice 'ac& 7 ()'7), Microsoft Windows )er#er 788: with )er#ice 'ac& = ()'=), or Windows code5named ;-onghorn"; Installing the WIM *) *ilter dri#er ena!les ou to mount a "wim file as if it were a director and to !rowse, cop , paste, and edit the #olume images from a file management tool, such as Windows E2plorer, without e2tracting or recreating the image" Im)ortant 0ou must run each of these command5line options indi#iduall " Additionall , if ou do not pro#ide a location for our captured "wim file, the process automaticall creates it in our ,Image director " *or e2ample, if ou enter data.wim instead of d:\imaging\data.wim while using the Hcapture option, the data.wim file appears in our ,Image director "

5Image Command,Line 03tions

The following command5line options are a#aila!le for ,Image< 6ima#e S7a))end director imageNfile ;description; S7+eri$yTT 6ima#e S7a))ly imageNfile director inde2Nnum!er S7+eri$yTT 6ima#e S7boot imageNfile inde2Nnum!er ]7ca)ture director imageNfile ;description;^ Z ]7a))end director imageNfile ;description;^ Z ]7e6)ort destination"wimNfile source"wimNfile inde2Nnum!er^T 6ima#e S7ca)ture director imageNfile ;description; S7+eri$yTT 6ima#e S7com)ress ]ma6imum Z $ast Z none^ 7ca)ture director imageNfile ;description;T 6ima#e S7con$i# configurationNfile"ini ]Hcapture director imageNfile ;description;^ Z ]Happend director imageNfile ;description;^T 6ima#e S7delete imageNfile inde2Nnum!erT 6ima#e S7dirSimageNfileT inde2Nnum!erT 6ima#e S7e6)ort destination"wimNfile source"wimNfile inde2Nnum!erT 6ima#e S7in$o imageNfileT 6ima#e S7mount Sdirector T imageNfile inde2Nnum!er S7+eri$yTT

130

6ima#e S7mountr Sdirector T imageNfile inde2Nnum!er S7+eri$yTT 6ima#e S7re$ splitwim7"swm 7a))ly splitwim"swm dri#e inde2Nnum!erT 6ima#e S7s)lit imageNfile destination"wimNsi4eT 6ima#e S7unmount S7commitTSdirector TT Option 7a))end director imageNfile ;description; S7+eri$yT .escription Appends a #olume image to an e2isting image ("wim) file" $reates a single instance of the file, comparing it against the resources that alread e2ist in the "wim file, so ou do not capture the same file twice" Im)ortant 0ou must run this option from the Windows 'reinstallation En#ironment (Windows 'E)" Additionall , ou must ensure that ou ha#e enough dis& space for the 7a))end option to run" If ou run out of dis& space during the 7a))end option, ou ma corrupt the appended "wim file" Important The "wim file can ha#e onl one assigned compression t peD therefore, ou can append onl files with the same compression t pe" directory The name and location of the e2isting "wim file to append" ima#eA$ile The name and location of the #olume image that appends the e2isting file" Bdescri)tionB The te2t that pro#ides additional reference information" The straight quotation mar&s are required" 0ou ma also use the 7+eri$y option, which ena!les file #erification, chec&ing for errors and file duplication" E2ample< xima#e .appen0 0: 0:\ima#in#\0ata!1im (Dri2e D( .2erify

131

Option 7a))ly imageNfile director inde2Nnum!er S7+eri$yT

.escription Applies a #olume image to a specified dri#e" Im)ortant 0ou must run this option from Windows 'E" ima#eA$ile The name and location of the #olume image applied to the director " directory The name and location where to appl the image" inde6Anumber The num!er that references the specific #olume within the "wim file" 0ou must create all hard dis& partitions !efore !eginning this process, unless ou run this option using a script" If ou use the 7a))ly option for a director structure, the option will include the specified director , including all su!directories and files" Im)ortant 0ou must include the parent director for the 7a))ly optionD otherwise, when the image is applied, the image will o#erwrite e#er thing in that location" *or e2ample, if ou appl the image to dri#e $, the 7a))ly option can o#erwrite e#er thing that e2ists in dri#e $ with our image files" To automate the creation of a director , ou must add the m/dir $target director%& command to our script, !efore ,Image performs the 7a))lyoption" E2ample< xima#e .apply 0:\ima#in#\0ata!1im 0:\Ne1/Directory : .2erify

132

Option 6ima#e 7boot imageNfile inde2Nnum!er ]7ca)ture director imageNfile ;description;^ Z ]7a))end director imageNfile ;description;^ Z ]7e6)ort destination"wimNfile source"wimNfile inde2Nnum!er^

.escription .efines the "wim and #olume image from which to !oot Windows 'E" Onl one #olume image can !e mar&ed as !oota!le within a "wim file" Im)ortant 0ou must run this option from Windows 'E" ima#eA$ile The name and location of the "wim file, which contains the #olume image to ma&e !oota!le" inde6Anumber The num!er that references the specific #olume to !oot within the "wim file" E2ample< xima#e .%oot 0:\ima#in#\0ata!1im : .2erify .capture 0: 0:\ima#in#\0ata!1im (Dri2e D(

133

Option 7ca)ture director imageNfile ;description; S7+eri$yT

.escription $aptures a #olume image from a dri#e to a new "wim file" $aptured directories include all su!folders and data" Im)ortant 0ou must run this option from Windows 'E" .uring the capture operation, fast compression is automaticall applied" If ou require a different compression t pe, ou must use the 7com)ress option" directory The name and location of the #olume image for capture" ima#eA$ile The name and location of the new "wim file" Bdescri)tionB The te2t that pro#ides additional reference information" The straight quotation mar&s are required" 0ou ma also use the 7+eri$y option, which ena!les file #erification, chec&ing for errors and file duplication" 4ote The 7ca)ture option is onl capa!le of creating a single "wim fileD howe#er, ou ma split this image file ! using the 7s)lit option, as necessar " E2ample< xima#e .capture 0: 0:\ima#in#\0ata!1im (Dri2e D( .2erify

134

Option 7com)ress ]ma6imum Z $ast Z none^ 7ca)ture director imageNfile ;description;

.escription )pecifies the t pe of compression used for the initial capture operation" 0ou can use onl one t pe of compression for each "wim fileD therefore, this option is #alid onl on the initial capture" 0ou must use this option with the 7ca)ture option" Im)ortant 0ou must run this option from Windows 'E" ma6imum 'ro#ides the !est compressionD howe#er, it also ta&es the longest time to capture the image" $ast 'ro#ides faster image compression, !ut pro#ides less compression than that pro#ided ! ma6imum" This is also the default compression t pe, used if ou lea#e this parameter !lan&" none 'ro#ides no compression to the captured image" 4ote While the compression t pe that ou choose affects the capture time, it slightl affects the appl time" E2ample< xima#e .compress fast .capture 0: 0:\ima#in#\0ata!1im (Dri2e D(

135

Option 7con$i# configurationNfile"ini ]7ca)ture director imageNfile ;description;^ Z ]7a))end director imageNfile ;description;^

.escription Ena!les ou to create and use a configuration file, defining the following for the captured or appended "wim file< *olders and files that must !e e2cluded from the 7ca)ture operation" *olders, files, and file t pes that must !e e2cluded from the 7com)ress operation" Whether the "wim file must align on a BCK !oundar " Im)ortant 0ou must run this option from Windows 'E" Additionall , ou must use either the 7ca)ture or 7a))end option with the 7con$i# option" con$i#urationA$ile5ini The name and location of the configuration file" 0ou can rename this file, as necessar " Im)ortant If ou name our configuration_list"ini file Wimscript"ini, and store it in our ,Image director (where the ,Image"e2e file is located)D it will automaticall run when ou run the 7ca)ture option, without requiring ou to use the 7con$i# option" E2ample< xima#e .confi# c:\confi#uration!ini .capture 0: 0:\ima#in#\0ata!1im (Dri2e D(

136

Option 7delete imageNfile inde2Nnum!er

.escription .eletes the specified #olume image from a "wim file with multiple #olume images" This option deletes onl the metadata entries and ,MentriesD it does not delete the stream data and does not optimi4e the "wim file" Once the file is mounted, ou ma #iew, !ut not modif , all the information contained in the director " If ou do not specif the parameters to mount, this option will list all mounted images" ima#eA$ile The name and location of the "wim file specified for deletion" inde6Anumber The num!er that references the specific #olume within the "wim file" Im)ortant 0ou must run this option from Windows 'E" Additionall , there must alwa s !e at least one #olume image in a "wim fileD therefore, ou can delete a #olume image onl if more than one image e2ists" E2ample< xima#e .0elete 0:\ima#in#\0ata!1im : .ispla s a list of the files and folders within a specified #olume image" ima#eA$ile The name and location of the #olume image for re#iew" If ou do not pro#ide a #olume image, this option returns a director listing for all #olume images in the "wim file" inde6Anumber The num!er that references the specific #olume within the "wim file" E2ample< xima#e .0ir 0:\ima#in#\0ata!1im :

7dir SimageNfileT inde2Nnum!er

137

Option 7e6)ortdestination"wim source"wim inde2Nnum!er

.escription E2ports a cop of the specified "wim file ()ource"wim) to another "wim file (.estination"wim)" The )ource"wim and .estination"wim files must use the same compression t pe" Im)ortant 0ou must run this option from Windows 'E" Additionall , ou must ensure that ou ha#e enough dis& space for the 7e6)ort option to run" If ou run out of dis& space while the 7e6)ort option runs, ou might corrupt the .estination"wim file" destination5 imA$ile The name and location of the "wim file, appended with the source'wim file data" source5 imA$ile The name and location of the "wim file that appends the destination'wim file data" inde6Anumber The num!er that references the specific #olume within the "wim file" E2ample< xima#e .export 0:\ima#in#\0ata!1im 0:\ima#in#\sample!1im : (eturns the stored ,M- descriptions for the specified "wim file, including !ut not limited to the total file si4e, the image inde2 num!er, the director count, file count, and a description" ima#eA$ile The name and location of the "wim file for ,M- data re#iew" E2ample< xima#e .info 0:\ima#in#\0ata!1im

7in$o imageNfile

138

Option 7mount Sdirector T imageNfile inde2Nnum!er

.escription Mounts a "wim file from Microsoft Windows ,' with )er#ice 'ac& 7 ()'7), Microsoft Windows )er#er 788: with )er#ice 'ac& = ()'=), or Windows code5named ;-onghorn,; with read5 onl permission, to a specified director " Once the file is mounted, ou ma #iew, !ut not modif , all the information contained in the director " Im)ortant 0ou must install the WIM *) filter !efore ou can mount an image" directory The complete director location to mount the files" If ou do not specif a director , this option will list all mounted images" ima#eA$ile The name and location of the "wim file to mount with read5onl permission" 4ote The image file must !e a #alid "wim file" 0ou cannot mount "swm files using ,Image" inde6Anumber The num!er that references the specific #olume within the "wim file" E2ample< xima#e .mount c:\mounte0/ima#es 0:\ima#in#\0ata!1im 7

139

Option 7mountr Sdirector T imageNfile inde2Nnum!er

.escription Mounts a "wim file from Microsoft Windows ,' with )er#ice 'ac& 7 ()'7), Microsoft Windows )er#er 788: with )er#ice 'ac& = ()'=), or Windows code5named ;-onghorn,; with readHwrite permission, to a specified director " Once the file is mounted, ou ma #iew and modif all the information contained in the director " Im)ortant 0ou must install the WIM *) filter !efore ou can mount an image" The 7mountr option requires e2clusi#e access to the "wim fileD therefore, ou cannot use the 7mountr option if an image is currentl mounted using either the 7mount or 7mountr options" Im)ortant 0ou must not mount an image to the parent or su!directories of an alread mounted director " /pon mounting an image to a director that contains files, the e2isting files will !e mas&ed until ou run the 7unmount option" Additionall , ou must not mount our image to Windows reser#ed folders" directory The complete director location to mount the "wim file" If ou do not specif a director , this option will list all mounted images" ima#eA$ile The name and location of the "wim file to mount with readHwrite permission" 4ote The image file must !e a #alid "wim file" 0ou cannot mount "swm files using ,Image" inde( number The num!er that references the specific #olume within the "wim file" E2ample< xima#e .mountr1 c:\mounte0/ima#es

140

Option 7re$splitwim7"swm 7a))ly splitwim"swm dri#e inde2Nnum!er

.escription Ena!les the reference of split "wim files ()WMs)" Im)ortant 0ou must run this option from Windows 'E" Additionall , ou must run this option with the 7a))ly option" s)lit im25s m The name and location of the split "wim files" These ma !e specified with wildcard characters (for e2ample, M) or e2act names" )plit "wim files alwa s contain a num!er within the file name, for e2ample, .ata7"swm, .ata:"swm, and so on" Im)ortant 0ou must specif all "swm files" If file resources are not located for the specified image in the supplied set, the option will fail" s)lit im5s m The name and location of the initial split "wim file, t picall displa ed without a num!er in the file name, for e2ample, .ata"wim" inde6Anumber The num!er that references the specific #olume within the "wim file" 4ote 0ou ma use multiple 7re$ options with the 7a))ly option" E2ample< xima#e .ref 0:\ima#in#\0ata7!s1m .apply 0:\ima#in#\0ata!s1m D: :

141

Option 7s)lit imageNfile destination"wimNsi4e

.escription )plits an e2isting "wim file into multiple read5 onl split "wim files ("swm)" Im)ortant 0ou must run this option from Windows 'E" ima#eA$ile The name and location of the "wim file to split" destination5 imAsi3e .etermines the si4e in mega! tes (M%) for each created file" This option generates the "swm files into the specified director D naming the files the same as the specified image file, !ut with an additional num!er and the "swm file name e2tension" *or e2ample, if ou choose to split a file named .ata"wim, this option creates a .ata"swm file, a .ata7"swm file, a .ata:"swm file, and so on, defining each portion of the split "wim file" E2ample< xima#e .split 0:\ima#in#\0ata!1im 566

142

Option 7unmount S7commitT Sdirector T

.escription /nmounts the mounted image from a specified director " Im)ortant $onfirm that ou ha#e enough hard dis& space to add the files for our image" 0ou must account for the si4e of the files that ou add to the "wim file, plus an increase in file si4e due to the modification of e2isting files, minus an files that ou deleted, !efore performing the 7commit option" If ou do not ha#e enough hard dis& space, an error will occur" directory The complete director location to unmount the files" If ou do not specif a director , this option will list all mounted images" If ou use the 7unmount option without the 7commit option, our changes will !e discarded" To sa#e our changes, ou must meet !oth of the following conditions< =" 0ou used the 7commit option with the 7unmount option" 7" 0ou mounted the image using the 7mountr option" E2ample< xima#e .unmount .commit c:\mounte0/ima#es

/ee Also
W!at is (Ima e> +ow (Ima e Wor5s Confi uration $ile Creation Wal5t!rou !0 Ca&ture an Ima e Wal5t!rou !0 Com&ress an Ima e Wal5t!rou !0 Mount and Modif' an Ima e Wal5t!rou !0 A&&l' a .e&lo'ment Ima e

<rou8leshooting Installation ;ro8lems

This section will descri!e common questions and scenarios and their resolutions"

143

;ro8lems with Image *aintenan+e

%elow ou will find commonl as&ed questions a!out trou!leshooting imaging pro!lems"

9ow do I modif4 an e@isting image on+e I ha1e resealed it without a+ti1ating itD
)tart with an original image and add our hardware in audit mode" $onfigure the image 3ust the wa ou li&e it, and then reseal, image, and appl to other computers" /se ) sprep to reseal the image after ou ha#e added our custom applications and hardware" 0ou can then use the image on multiple computers of the same configuration"

Wh4 does /4s3re3 not worA when I insert the flo334 disA with /4s3re3.infD
%ecause ) sprep"inf must !e in the $<K) sprep director " If it is located elsewhere, ou cannot enter Audit mode or use $T(-A)1I*TA*:"

Wh4 does /4s3re3 not remo1e a user a++ount that was +reated to 3reinstall the o3erating s4stem from the C7,60*D
.o not create a user account !efore running ) sprep" The account will remain !ecause ) sprep does not remo#e an user accounts" Instead, log on ! using the Administrator account for auditing and resealing the destination computer" To pre#ent a user account from !eing created when ou preinstall the operating s stem from a $.5(OM, add the following entr to our /nattend"t2t or Winnt"sif answer file<
[?natten0e0] ?natten0S1itc9 = +es