Microsoft®Microsoft®

Desktop

Deployment Assistance Program

Deployment Assistance Program

3. Deploying Windows XP3. Deploying Windows XP

Thomas LeeChief Technologist QA plcthomas.lee@qa.com

AgendaAgenda

Windows XP SP2 Setup ImprovementsWindows XP SP2 Setup Improvements

Two types of Automated DeploymentTwo types of Automated DeploymentScripted InstallScripted Install

ImageImage

Automation of the Installation processAutomation of the Installation process

Win PEWin PE

XP SP2XP SP2

Setup AgendaSetup Agenda

Unattended setupUnattended setup

WinPE WinPE newnew

ImagingImaging

RISRIS

Setup ToolsSetup Tools

Why not use OEM Build?Why not use OEM Build?

Breaks the license Breaks the license

SysPrep is differentSysPrep is different

Lots of “OEM Stuff”Lots of “OEM Stuff”

Product KeysProduct Keys

Automated InstallationsAutomated Installations

Unattended setupUnattended setupIntroduced in NT4 workstationIntroduced in NT4 workstation

Scripted automated Windows SetupScripted automated Windows Setup

Still supported, not recommend for production deploymentStill supported, not recommend for production deployment

ImagingImagingUses SysPrep and Microsoft (WIM) or 3Uses SysPrep and Microsoft (WIM) or 3rdrd Party Disk Imaging technology Party Disk Imaging technology

Copies “Master build” to multiple PCsCopies “Master build” to multiple PCs

Remote Installation ServicesRemote Installation ServicesUnattended Setup from ServerUnattended Setup from Server

Imaging from Server (SMS OSD or 3Imaging from Server (SMS OSD or 3rdrd party products) party products)

Great for that first buildGreat for that first build

Not recommended for Production deployment, due to broadcasts and Not recommended for Production deployment, due to broadcasts and network bootnetwork boot

Unattended Setup Unattended Setup

Most flexible deployment optionMost flexible deployment option

Also slowestAlso slowest

Starts and runs Windows XP Setup on each computer Starts and runs Windows XP Setup on each computer individuallyindividually

What you need:What you need:

Winnt.exe, Winnt32.exe or CD (BIOS must support bootable CD)Winnt.exe, Winnt32.exe or CD (BIOS must support bootable CD)

A distribution share with Setup files or Windows XP CDA distribution share with Setup files or Windows XP CD

An answer file (text file) or winnt.sif if running unattended from CDAn answer file (text file) or winnt.sif if running unattended from CD

Consider speed and amount of data transfer this involves Consider speed and amount of data transfer this involves compared to an imagecompared to an image

Unattended InstallationUnattended Installation

ManualSetup

Input of information based on boot menu, or missing points from answer file.

First boot experience may require some information input.

Unattend.txt

Starting Unattended Install Starting Unattended Install

From DOS/Windows 3.x:From DOS/Windows 3.x:

winnt.exe /u:<answer file> /s: <source sharewinnt.exe /u:<answer file> /s: <source share>>

Make sure you have smartdrv.exe loadedMake sure you have smartdrv.exe loaded

From Windows 9x/NT/WinPE: From Windows 9x/NT/WinPE:

winnt32.exe /unattend:<answer file> /s: <source share> winnt32.exe /unattend:<answer file> /s: <source share> [ /tempdrive:<target drive> /syspart:<target drive> ][ /tempdrive:<target drive> /syspart:<target drive> ]

From CD (computer supports CD boot) - Place winnt.sif file on a From CD (computer supports CD boot) - Place winnt.sif file on a floppy disk, boot Setup from CD and insert the floppy when Setup floppy disk, boot Setup from CD and insert the floppy when Setup starts starts

Understand the implications this has on time and network Understand the implications this has on time and network bandwidthbandwidth

Win PEWin PE

OverviewOverview

FeaturesFeatures

LimitationsLimitations

ScenariosScenarios

Features for Windows PEFeatures for Windows PE

DiscussionDiscussion

What is Windows PE?What is Windows PE?

Reduced version of Windows XPReduced version of Windows XP

Can be created from either an x86 based 32 bit OS Can be created from either an x86 based 32 bit OS SKU X64 or an IA64 bit OS Sku today SKU X64 or an IA64 bit OS Sku today

Windows PE provides full networking, driver Windows PE provides full networking, driver injection, WMI support, Ramdisk(SrSP1)injection, WMI support, Ramdisk(SrSP1)

Windows PE is used to build, test and deploy OS Windows PE is used to build, test and deploy OS imagesimages

Windows PE is a base platform for a variety of 3Windows PE is a base platform for a variety of 3 rdrd party support related solutions: party support related solutions:

Virus scanning and recovery based products Virus scanning and recovery based products

Hardware and software test and diagnostic toolsHardware and software test and diagnostic tools

OS and utilities based deploymentOS and utilities based deployment

Windows PE OverviewWindows PE Overview

An NTFS-capable boot disk withAn NTFS-capable boot disk with

TCP/IP networkingTCP/IP networking

Mass-storage controller supportMass-storage controller support

VESA mode video supportVESA mode video support

What is it used for?What is it used for?

DeploymentDeployment

RecoveryRecovery

TroubleshootingTroubleshooting

Originally designed to provide cross-architecture Originally designed to provide cross-architecture deployment platformdeployment platform

Windows PE OverviewWindows PE OverviewRelease historyRelease history

First release was concurrent with Windows XP in 2001First release was concurrent with Windows XP in 2001

Windows XP Service Pack 1:Windows XP Service Pack 1:Standalone DFS root connectivityStandalone DFS root connectivity

New (easier) boot from HDD abilityNew (easier) boot from HDD ability

Windows Server 2003Windows Server 2003Ability to build Windows PE from Windows Server 2003 Ability to build Windows PE from Windows Server 2003 productsproducts

Windows XP Service Pack 2 release called WinPE2004Windows XP Service Pack 2 release called WinPE2004WMIWMI

FirewallFirewall

Driver injectionDriver injection

Updated with Windows Server 2003 Service Pack 1Updated with Windows Server 2003 Service Pack 1USB BootUSB Boot

Any PXE Server BootAny PXE Server Boot

FeaturesFeaturesWorks with all systems that Windows XP and Works with all systems that Windows XP and Windows Server 2003 supportWindows Server 2003 support

Can be built from Windows XP or Windows Can be built from Windows XP or Windows Server 2003Server 2003

Device support:Device support:

Networking*Networking*

Mass-storage*Mass-storage*

VESA video support (single driver)VESA video support (single driver)

*Includes all built in drivers for this class from the version of Windows it was *Includes all built in drivers for this class from the version of Windows it was built from. New drivers of this class can be easily added.built from. New drivers of this class can be easily added.

FeaturesFeatures

VESA support specified by display controller hardware VESA support specified by display controller hardware determines resultant color depth and resolutiondetermines resultant color depth and resolution

Can connect to standalone DFS roots and other SMB Can connect to standalone DFS roots and other SMB sharesshares

Ability to build-out storage, partition, do native FAT or Ability to build-out storage, partition, do native FAT or NTFS disk formatting, 32-bit disk imaging, I/ONTFS disk formatting, 32-bit disk imaging, I/O

FeaturesFeaturesBoot supportBoot support

CDCD

DVD (ISO only)DVD (ISO only)

Hard diskHard disk

PXE (RIS only for WinPE 2004)PXE (RIS only for WinPE 2004)

Supported for deployingSupported for deploying

Windows 2000Windows 2000

Windows XPWindows XP

Windows Server 2003Windows Server 2003

Non-FeaturesNon-Features

Windows Explorer shellWindows Explorer shell

Audio supportAudio support

DirectXDirectX

Visual Studio .NET applicationsVisual Studio .NET applications

ADSI connectivityADSI connectivity

Uses For WinPEUses For WinPE

Deployment (broadest use today)Deployment (broadest use today)

Maintenance/repair/recoveryMaintenance/repair/recovery

Other utilities ISVs use;Other utilities ISVs use;

Anti-virusAnti-virus

DiagnosticsDiagnostics

File-system repair toolsFile-system repair tools

Non-Uses For WinPENon-Uses For WinPE

Embedded operating systemEmbedded operating system

Reboots every 24 hoursReboots every 24 hours

Use Windows XP EmbeddedUse Windows XP Embedded

General use operating systemGeneral use operating system

No Explorer ShellNo Explorer Shell

No IENo IE

Limited Application SupportLimited Application Support

Building WinPEBuilding WinPEmkimg.cmdmkimg.cmd

Creates directory structure for CDCreates directory structure for CD

If required manually tailor the platformIf required manually tailor the platformDrivers, utilitiesDrivers, utilities

Optionally customize the default scriptsOptionally customize the default scriptsstartnet.cmdstartnet.cmd

Optionally create custom shellOptionally create custom shellC/C++C/C++

Windows Script Host*Windows Script Host*

HTA (HTML Applications)*HTA (HTML Applications)*

*Support can be added using buildoptionalcomponents.vbs*Support can be added using buildoptionalcomponents.vbs

Building WinPE continuedBuilding WinPE continued

OSCDimg.exeOSCDimg.exe

Creates ISO CD image of your directoryCreates ISO CD image of your directory

El-torito bootableEl-torito bootable

Same tool to create supported custom CDSame tool to create supported custom CD

DemoDemo

• Using Setup Manager to build answer Using Setup Manager to build answer filesfiles

• WinPE and Diskpart.exe WinPE and Diskpart.exe

New Licensing ModelNew Licensing Model

The new licensing model enables 3 options:

Ability to use Windows PE in-house for tools development, Ability to use Windows PE in-house for tools development, testing, and OS deployment (free)testing, and OS deployment (free)

IHV/OEM ability to develop support related test and IHV/OEM ability to develop support related test and diagnostic tools and ship these BIOS-locked to their diagnostic tools and ship these BIOS-locked to their hardware (free)hardware (free)

IHV/ISV/SI/OEM/ODM ability to create support related IHV/ISV/SI/OEM/ODM ability to create support related products (Virus scan, test and diagnostic, recovery etc) and products (Virus scan, test and diagnostic, recovery etc) and ship these tools in a retail setting for a profit. (pay royalty ship these tools in a retail setting for a profit. (pay royalty when ship)when ship)

licwinpe@microsoft.comlicwinpe@microsoft.com for all queries for all queries

Scenario - ScriptedScenario - ScriptedScenario: Deploying new systems, using scripted installation – Scenario: Deploying new systems, using scripted installation – Windows PE launched via RISWindows PE launched via RIS

1.1. New system arrives and is sent to employeeNew system arrives and is sent to employee

2.2. Machine is powered on and PXE bootsMachine is powered on and PXE boots

3.3. Boots to Windows PEBoots to Windows PE

4.4. Disks are partitioned and formatted using diskpart and formatDisks are partitioned and formatted using diskpart and format

5.5. Winnt32 is launched with a custom unattendWinnt32 is launched with a custom unattend

6.6. Exit Windows PE when that completesExit Windows PE when that completes

7.7. Install applications when setup completesInstall applications when setup completes

Scenario - ScriptedScenario - ScriptedTask examples: DISKPARTTask examples: DISKPART

CleanCleanSEL DIS 0SEL DIS 0

CLEANCLEAN

Partition CreationPartition CreationSEL DIS 0SEL DIS 0

CRE PAR PRICRE PAR PRI

ACTIVEACTIVE

ASSIGN LETTER=CASSIGN LETTER=C

EXITEXIT

Scenario - ScriptedScenario - Scripted

Task examples: Task examples:

Format /Q /Y /FS:NTFSFormat /Q /Y /FS:NTFS

Winnt32 syntaxWinnt32 syntaxWinnt32 /syspart:C: /tempdrive:C: /makelocalsource /dudisable Winnt32 /syspart:C: /tempdrive:C: /makelocalsource /dudisable /unattend:unattend.txt/unattend:unattend.txt

Scenario – Imaging (SMS OSD?)Scenario – Imaging (SMS OSD?)Scenario: Migrating to XP, using USMT and Windows PE (with Scenario: Migrating to XP, using USMT and Windows PE (with imaging tools)imaging tools)

1.1. USMT migrates files and settings off system USMT migrates files and settings off system

2.2. CD of Windows PE provided to employeeCD of Windows PE provided to employee

3.3. Machine is powered on and CD bootsMachine is powered on and CD boots

4.4. Boots to Windows PEBoots to Windows PE

5.5. Imaging tool used to apply image from UNCImaging tool used to apply image from UNC

6.6. Exit Windows PE when that completesExit Windows PE when that completes

7.7. USMT migrates files and settings backUSMT migrates files and settings back

Building An OS ImageBuilding An OS Image

Clean install OSClean install OS

Ensure same HAL type (ACPI, non-ACPI)Ensure same HAL type (ACPI, non-ACPI)

Customize installationCustomize installation

Install applicationsInstall applications

Prepare for management infrastructurePrepare for management infrastructure

Generally handled by domainGenerally handled by domain

User State MigrationUser State Migration

Group PolicyGroup Policy

Building An OS Image Building An OS Image (cont.)(cont.)

Run Sysprep.exeRun Sysprep.exe

-reseal for end-user boot experience-reseal for end-user boot experience

-factory for customizing on reboot -factory for customizing on reboot

Create “image”Create “image”

33rdrd party imaging tools party imaging tools

Boot to Windows PE and xcopy to serverBoot to Windows PE and xcopy to server

Maintain “image”Maintain “image”

Edit Sysprep.inf on imageEdit Sysprep.inf on image

Add files, driversAdd files, drivers

Problems with Previous WinPEProblems with Previous WinPE

1.1. No support for WMINo support for WMI

2.2. No support for retrieving SMBIOS infoNo support for retrieving SMBIOS info

3.3. Can only PXE boot from RISCan only PXE boot from RIS

4.4. CD swapping is complicated (/INRAM)CD swapping is complicated (/INRAM)

5.5. If Windows PE boots from hard-disk that disk If Windows PE boots from hard-disk that disk cannot be repartitioned/reformattedcannot be repartitioned/reformatted

Windows PE 2004 New FeaturesWindows PE 2004 New FeaturesTargeted Windows PE specific changes include:Targeted Windows PE specific changes include:

Ability to inject 32/64 bit device drivers easily into Ability to inject 32/64 bit device drivers easily into Windows PE (Windows XP and Windows Server 2003 Windows PE (Windows XP and Windows Server 2003 drivers)drivers)

WMI support for hardware based diagnostic tool accessWMI support for hardware based diagnostic tool access

Built in firewall support enabled by defaultBuilt in firewall support enabled by default

Build scripts documented to reduce the size of Build scripts documented to reduce the size of Windows PEWindows PE

Boot Windows PE in a RAMDisk via PXE, from Hard Boot Windows PE in a RAMDisk via PXE, from Hard disk or CDdisk or CD

Full support for all architectures Windows supportsFull support for all architectures Windows supports

Add Device DriversAdd Device Drivers

Change build scripts to support additional Change build scripts to support additional hardware device classes and drivers in base hardware device classes and drivers in base Windows PE imageWindows PE image

Provide ability to add additional 32 drivers outside Provide ability to add additional 32 drivers outside of “in-box” drivers to existing build of Windows PE of “in-box” drivers to existing build of Windows PE using drvinst.cmdusing drvinst.cmd

Add drivers after Windows PE image is built for Add drivers after Windows PE image is built for test and diagnostic of the latest hardware/drivers test and diagnostic of the latest hardware/drivers avoiding full rebuildsavoiding full rebuilds

DRVINST.CMDDRVINST.CMDSource OptionsSource Options

[/inf] – path to specific driver[/inf] – path to specific driver

[/oscd] – path to OS CD[/oscd] – path to OS CD

Filter OptionsFilter Options

[/onlyid] – only install with matching PNP IDs[/onlyid] – only install with matching PNP IDs

[/ignoreid] - do not install these PNP IDs[/ignoreid] - do not install these PNP IDs

[/onlyclass] – only install this class of driver[/onlyclass] – only install this class of driver

[/ignoreclass] – ignore these classes of driver[/ignoreclass] – ignore these classes of driver

Action OptionsAction Options

[/inject] – specifies path to WinPE image (c:\winpe)[/inject] – specifies path to WinPE image (c:\winpe)

[/preview] – list drivers that would be installed[/preview] – list drivers that would be installed

WMI SupportWMI Support

Add WMI base support to provide access to Add WMI base support to provide access to underlying hardware within Windows PEunderlying hardware within Windows PE

Support for over 40+ providers and 1500+ Support for over 40+ providers and 1500+ classes.classes.

Leverage the ability to load a native driver for Leverage the ability to load a native driver for hardware validation and queryhardware validation and query

RAMDisk BootRAMDisk Boot

Ability to boot, load and run Windows PE within a Ability to boot, load and run Windows PE within a RAMDisk on a PC via network (any PXE server), RAMDisk on a PC via network (any PXE server), hard disk, or CDhard disk, or CD

Provides ability to run tests and diagnostics Provides ability to run tests and diagnostics remotely from the server or on local mediaremotely from the server or on local media

Allows for CD swapping for deployment/recovery Allows for CD swapping for deployment/recovery mediamedia

Windows PE New Features - SummaryWindows PE New Features - Summary

Windows XP Service Pack 2Windows XP Service Pack 2

WMI Support w/ 47 providers and 1500 classesWMI Support w/ 47 providers and 1500 classesEnables IP addresses to be changed on the fly after Enables IP addresses to be changed on the fly after the WinPE CD has booted.the WinPE CD has booted.

Driver Injection and PnP supportDriver Injection and PnP support

Windows Firewall supportWindows Firewall support

Set IP for multiple NICs, rather than just first NIC Set IP for multiple NICs, rather than just first NIC enumeratedenumerated

Windows PE New Features - FutureWindows PE New Features - FutureWindows Server 2003 Service Pack 1Windows Server 2003 Service Pack 1

All features listed for XPSP2 plusAll features listed for XPSP2 plus

Major Overhaul release; lots of bug fixesMajor Overhaul release; lots of bug fixes

Documentation getting a major clean upDocumentation getting a major clean up

RAMDisk boot support for HD, CD and any vendors PXE*RAMDisk boot support for HD, CD and any vendors PXE*

Full support for all architectures Windows Server 2003 Service Pack Full support for all architectures Windows Server 2003 Service Pack 1 will support1 will support

MKIMG -- No longer need to maintain separate build directories with MKIMG -- No longer need to maintain separate build directories with ia64/amd64/x86 tools.  Correct tools pulled from platform-specific ia64/amd64/x86 tools.  Correct tools pulled from platform-specific build directories, allowing same modified build scripts across build directories, allowing same modified build scripts across architectures to be used.architectures to be used.

ADO -- support named-pipe as well as TCPIP transportADO -- support named-pipe as well as TCPIP transport

*Requires minimum of 256MB*Requires minimum of 256MB

Installing Windows XP from SourceInstalling Windows XP from Source

Windows XPWindows XP

Copy i386 folder from XP CD ROMCopy i386 folder from XP CD ROM

Windows XP SP2Windows XP SP2

Run XPSP2.EXE /S:d:\winxpRun XPSP2.EXE /S:d:\winxp(see support\tools\spdeploy.htm)(see support\tools\spdeploy.htm)

(see support\tools\deploy.cab for GREAT info)(see support\tools\deploy.cab for GREAT info)

Let SUS/WU add the restLet SUS/WU add the rest

\i386\i386\$OEM$\$OEM$

\Textmode\Textmode

\$$\$$\$1\$1

\<drive_letter>\<drive_letter>

\<drivers_dir>\<drivers_dir>

\<drive_letter>\<drive_letter>

Windows XP filesWindows XP files

Contains all OEM filesContains all OEM files

Maps to %systemdrive%. Maps to %systemdrive%.

Contains PnP drivers and infsContains PnP drivers and infs

Maps to a drive on the computer. E.g. E:\Maps to a drive on the computer. E.g. E:\

Contains Txtsetup.oem, SCSI and HAL filesContains Txtsetup.oem, SCSI and HAL files

Maps to %systemroot%Maps to %systemroot%

Distribution Share/Folder ExplanationDistribution Share/Folder Explanation

What do the various directory structures in a Build source What do the various directory structures in a Build source look like?look like?

Below contains installation files - Windows XP, device Below contains installation files - Windows XP, device drivers, any additional filesdrivers, any additional files

Structure ($OEM$ can be moved in unattend.txt)Structure ($OEM$ can be moved in unattend.txt)

Customising the BuildCustomising the Build

$OEM$ copies files to local disk$OEM$ copies files to local disk

Cmdlines.txt executes commands at the end of setupCmdlines.txt executes commands at the end of setup

Cmdlines.txt is run synchronouslyCmdlines.txt is run synchronously

Commands in cmdlines.txt execute asynchronouslyCommands in cmdlines.txt execute asynchronously

Use start /wait to call a CMD fileUse start /wait to call a CMD file

Use start /wait for each command in the CMD fileUse start /wait for each command in the CMD file

Cmdlines.txt has no user environment and no network access – Cmdlines.txt has no user environment and no network access – useful only for $OEM$useful only for $OEM$

Cmdlines.txt cannot install MSI packagesCmdlines.txt cannot install MSI packages

Use GUIRunOnceUse GUIRunOnce

Use GUIRunOnce for network app installsUse GUIRunOnce for network app installs

Adding support for PnP hardwareAdding support for PnP hardware

DriversDrivers must be available during GUI mode setup must be available during GUI mode setup

Place files in $OEM$\$1\Drivers – can make this a more detailed sub structurePlace files in $OEM$\$1\Drivers – can make this a more detailed sub structure

Create sub-folders (audio, net, etc) or vendor specificCreate sub-folders (audio, net, etc) or vendor specific

Unattend.txtUnattend.txt

[Unattend][Unattend]

OEMPnPDriversPath=“drivers\audio;drivers\net;drivers\etc”OEMPnPDriversPath=“drivers\audio;drivers\net;drivers\etc”

Setup prepends %systemdrive% to each pathSetup prepends %systemdrive% to each path

Sysprep =Sysprep =

Prepares a reference system duplication Prepares a reference system duplication

SMS OSDSMS OSD

3rd party imaging tools 3rd party imaging tools

XCopyXCopy

Similar to RIPrep, used for RIS imagingSimilar to RIPrep, used for RIS imaging

Requires relatively similar hardwareRequires relatively similar hardware

Runs Mini-Setup (or Windows WelcomeRuns Mini-Setup (or Windows Welcome in Windows XP) rather than full setup in Windows XP) rather than full setup

System preparation tool

Sysprep 2.0Sysprep 2.0

Support for longer OEMPnPPath stringsSupport for longer OEMPnPPath strings

Increased to 4096 charactersIncreased to 4096 characters

Administrator profile copied to Default UserAdministrator profile copied to Default User

Simplifies Default User configuration Simplifies Default User configuration

Factory switchFactory switch

Allows for updated or out of box drivers to be picked up by Allows for updated or out of box drivers to be picked up by image at install time when PnP occursimage at install time when PnP occurs

Winbom.ini Allows gathering of files (e.g., drivers, apps) from Winbom.ini Allows gathering of files (e.g., drivers, apps) from network or custom scripting/application installsnetwork or custom scripting/application installs

-PnP switch -PnP switch not recommendednot recommended

Enhancements

SysprepSysprep

Reference Computer is prepared as Reference Computer is prepared as desired – Windows and applicationsdesired – Windows and applications

11

Sysprep is run on the Computer, Sysprep is run on the Computer, which then powers offwhich then powers off

22

Using Windows PE or an imaging Using Windows PE or an imaging tool, the image is stored (here, to a tool, the image is stored (here, to a server)server)

33

Destination Computer is booted Destination Computer is booted using Windows PE or an imaging using Windows PE or an imaging tool, image is installed.tool, image is installed.

44

Destination Computer is powered Destination Computer is powered on, mini-setup runson, mini-setup runs

55

Destination Computer is powered Destination Computer is powered off & ready to redistributeoff & ready to redistribute

66

File File ServerServerReference Reference

ComputerComputer

33

Steps 4-6 repeated as needed for Steps 4-6 repeated as needed for each new Computer desiredeach new Computer desired

77

44

Destination Destination ComputerComputer

How it works

SyspreSysprepp

Sysprep.exeSysprep.exeMain toolMain tool

Setupcl.exeSetupcl.exeused to regenerate security IDsused to regenerate security IDs

Factory.exeFactory.exeWhen sysprep is run with the –factory optionWhen sysprep is run with the –factory option

Sysprep.infSysprep.infAnswer file used by SysprepAnswer file used by Sysprep

Files must be in Files must be in %systemdrive%systemdrive%\Sysprep folder%\Sysprep folder

Components

Unattend And Setup ManagerUnattend And Setup Manager

Setup Manager creates and modifies unattended Setup Manager creates and modifies unattended setup answer filessetup answer files

UnattendUnattend

SysprepSysprep

RISetupRISetup

Can be found with other deployment tools and Can be found with other deployment tools and guides in Deploy.cab on the product CDguides in Deploy.cab on the product CD

Updated versions of tools with XP SP1 and XP SP2Updated versions of tools with XP SP1 and XP SP2

Unattend And Setup ManagerUnattend And Setup Manager

Local admin password can be encryptedLocal admin password can be encrypted

Setup Manager features Improved Setup Manager features Improved user interfaceuser interface

Improved .chm file on the product CD Improved .chm file on the product CD for unattended setup and deploymentfor unattended setup and deployment

Enhancements

Remote Installation ServiceRemote Installation Servicess

Remote Installation ServiceRemote Installation ServiceAllows for network initiated setupAllows for network initiated setup

Clean scripted install (RISetup)Clean scripted install (RISetup)

Clean imaged install (RIPrep)Clean imaged install (RIPrep)

Uses PXE network cards to initiate setup with Uses PXE network cards to initiate setup with minimal user interactionminimal user interaction

Boot floppy supports select additional network cards Boot floppy supports select additional network cards that are not PXE capablethat are not PXE capable

RIS

RISRIS

The client requests an IP addressThe client requests an IP address11

The IP address is supplied by a The IP address is supplied by a DHCP serverDHCP server

The client contacts the RIS serverThe client contacts the RIS server

The RIS server checks Active The RIS server checks Active Directory to see if the client has Directory to see if the client has been pre-stagedbeen pre-staged

22

33

44

RIS responds or forwards the RIS responds or forwards the request to another RIS serverrequest to another RIS server

55

The RIS server sends startrom.com The RIS server sends startrom.com to the client – launches OSChoiceto the client – launches OSChoice

66

11

22

33

44

55

66

DHCP ServerDHCP Server

RIS ServerRIS Server Active Directory DCActive Directory DC

ClientClient

How it works

RISRIS

Support for deployingSupport for deployingAll retail versions of Windows 2000 (including Server and All retail versions of Windows 2000 (including Server and Advanced Server)Advanced Server)

Windows XP ProfessionalWindows XP Professional

All Windows Server 2003 productsAll Windows Server 2003 products

All 64-bit versions of Windows Server 2003*All 64-bit versions of Windows Server 2003*

Significant performance increase over RIS Significant performance increase over RIS in Windows 2000in Windows 2000

*RISetup only, not RIPrep-based images*RISetup only, not RIPrep-based images

Windows 2003 Enhancements

RIS InstallationRIS Installation

RiPrep

RiPrep.sif

Mini Setup or Windows Welcome

RISSetup

Ristndrd.sifRIS

RIS Server Services RIS Server Services

BINL (Boot Information Negotiation Layer)BINL (Boot Information Negotiation Layer)

The boot server service; interacts with the ADThe boot server service; interacts with the ADand other boot servers to remote install a clientand other boot servers to remote install a client

TFTPD (Trivial File Transfer Protocol Daemon)TFTPD (Trivial File Transfer Protocol Daemon)

Protocol used to transfer files needed to remote install, maintain and Protocol used to transfer files needed to remote install, maintain and troubleshoot a client machinetroubleshoot a client machine

SIS (Single Instance Storage)SIS (Single Instance Storage)

Runs on NTFS partition to reduce disk space usage by removing Runs on NTFS partition to reduce disk space usage by removing duplicate files from RIS imagesduplicate files from RIS images

Creating RIS OS InstallCreating RIS OS Install

Configure RIS Server as mentionedConfigure RIS Server as mentioned

Creates a default CD-based imageCreates a default CD-based image

Configure client computer names and locationsConfigure client computer names and locations

Configure client installation optionsConfigure client installation options

Modify installation using answer fileModify installation using answer file

Set permissions on image - set ACLs on .sif files (or Set permissions on image - set ACLs on .sif files (or templates folder)templates folder)

RIS TipsRIS Tips

Must have Windows 2000 SP2 on serverMust have Windows 2000 SP2 on server

Must have new RISETUP.EXEMust have new RISETUP.EXE

See Q287546See Q287546

Must copy new files from .NET serverMust copy new files from .NET server

RIPREP.EXERIPREP.EXE

IMIRROR.DLLIMIRROR.DLL

SETUPCL.EXESETUPCL.EXE

RIPREP.INFRIPREP.INF

© 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only.© 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only.MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.