Deploying Windows Vista with Microsoft Systems Management Server 2003 R2Executive Summary

This white paper describes the process of deploying Windows Vista with Systems Management Server (SMS) 2003 Release 2 (R2). This document describes the tools and techniques to combine the operating system imaging technologies in Windows Vista with SMS 2003 R2. IT professionals can use this white paper to help plan their own deployments of Windows Vista.

The combination of Windows Vista and SMS 2003 R2 makes Zero Touch and Lite Touch desktop deployment easier than ever before. These two products combine to drive down the cost of desktop deployment in today's competitive marketplace.

IntroductionThe need to remain competitive in a global market and constantly improving hardware platforms place the need to control information systems costs at the highest priority. Organizations must control deployment and continuing management costs while still maintaining security. Many organizations have deployed earlier Microsoft operating systems using a variety of methods that have not always been cost effective.

Microsoft SMS 2003 R2 is the most recent version of the Microsoft desktop, server, and device management system, aimed at medium to large organizations. SMS 2003 R2 builds on SMS 2003 Service Pack 2 (SP2) to provide additional functionality in the areas of third-party application updates and system vulnerability assessment. Although the guidance in this paper is identical for SMS 2003 and SMS 2003 R2, all product references are to SMS 2003 R2.

When combined with the new deployment features in Windows Vista, SMS 2003 R2 provides the best solution for deploying Windows Vista in medium-sized and large networks.

AimThe aim of this paper is to provide detailed technical guidance on the planning, processes, and procedures when using SMS 2003 R2 to deploy Windows Vista Enterprise in a medium to large network environment.

1

Note: This paper does not cover multisite scenarios, wide area network (WAN) links, or VPN connections. For further guidance from Microsoft, see the Systems Management Server 2003 Product Documentation Web site.

AudienceThe target audience for this paper is IT professionals, including those who currently do not use SMS 2003. These IT professionals could include network managers, consultants, and IT managers who work for or with medium to large enterprises.

PrerequisitesPrior knowledge and experience will help readers understand and apply the information in this paper, particularly experience in the following areas:

Windows Server 2003 Service Pack 1

SMS 2003 or SMS 2.0

Windows Vista Enterprise and Business Editions

Microsoft Windows XP Service Pack 2

Network EnvironmentRather than address a complex network environment, which would require a significantly longer white paper, the authors have confined this discussion to a simpler setup. Hence, this document includes the following network environment: Microsoft Windows Server® 2003 Service Pack 1 SMS 2003 R2 Single SMS Site Windows Vista Enterprise Edition Microsoft Windows XP with Service Pack 2 clients Single local area network (LAN)

2

IPreparing to Deploy Windows Vista

Microsoft Windows is the most successful operating system in the world. Windows Vista seeks to builds on this success by offering more features that securely support today’s hardware and functionality requirements. Windows Vista includes six editions, with each edition specifically tailored to specific users' requirements.● Windows Vista Starter● Windows Vista Home Basic● Windows Vista Home Premium● Windows Vista Ultimate● Windows Vista Business● Windows Vista Enterprise

This paper focuses on Windows Vista Enterprise. However, the recommendations also apply to Windows Vista Business. Together, these editions are the two that medium to large enterprises are most likely to deploy. For more information on Windows Vista Enterprise, see the Windows Vista Enterprise page on the Microsoft Get Ready for Vista site. For information on other versions of Windows Vista, see the Windows Vista Editions page on the Microsoft Get Ready for Windows Vista site.

FeaturesWindows Vista offers significant new features over Windows XP. All of these features enhance user productivity and reduce the costs of implementing the operating system. Windows Vista provides enhancements to the following areas:

Data Protection

Networking

Performance

Security

The User Experience

Services such as BitLocker and Device installation control provide improved data protection. The Encrypting File System (EFS) now allows the storage of encryption keys on Smart Cards.

3

The new Network Center enhances networking services, discovering and mapping devices dynamically. Diagnostics analyze and correct networking problems and new connection wizards help to maintain network security.

Windows SuperFetch, Windows ReadyBoost, and Windows ReadyDrive are all new services that improve performance.

The new User Account Control (UAC) feature ensures that all accounts, even administrator accounts, usually run with Limited User Access (LUA). This change minimizes the attack profile of the operating system.

The User Interface (UI) provides new features such as Windows Aero, live taskbar thumbnails, Windows Flip and Windows Flip 3D. These features improve users' interaction with the operating system.

You can find more information from the Windows Vista web site.

Deployment Techniques and ToolsDepending on the environment, organizations can deploy Windows Vista in a number of different ways:

DVD-Based Installation

Script-Based Installation

Windows Deployment Services

Systems Management Server

Deployment tools can validate hardware configurations or applications that run on Windows Vista. Other tools can control the way that Windows Vista deploys. These tools include:

Windows Vista Upgrade Advisor

Windows Vista Hardware Assessment

Windows Automated Installation Kit

User State Migration Tool 3.0

Microsoft Solution Accelerator for Business Desktop

Deployment 2007

Application Compatibility Toolkit

Vista Volume License Keys

Although this paper focuses on the use of SMS 2003 for deployment, the following section outlines these other methods for comparison.

DVD-Based InstallationThe Windows Vista DVD supports several methods for installing the operating system and can provide a recovery environment. The Windows Vista setup program uses a new Windows Image (WIM) format, which significantly decreases the time required to install or upgrade the operating system.

For a computer that has an already has an operating system installed, administrators can use the Windows Vista DVD to carry out an in-place upgrade. An in-place upgrade preserves existing data and applications, but only works with a compatible operating system. If the DVD drive does not have auto-run enabled, double-clicking D:\Setup.exe (where D is the letter of the DVD drive) starts the setup process.

4

The Windows Vista DVD is bootable, enabling installation of the operating system on to a computer without an existing operating system. First, configure the computer to boot from the DVD drive. Boot devices can be configured in the computers BIOS or on some computers, a boot menu may be available.

The final use for the Windows DVD is to start the Windows Recovery Environment (Windows RE). To start Windows RE, carry out the following steps:

1. Configure your computer to boot from the Windows Vista DVD.

2. Choose your language settings and click Next.3. Click Repair Your Computer.4. Choose your operating system and click Next.5. On the System Recovery Options, click Startup Repair.

Script-Based InstallationWindows Vista uses a new type of XML formatted answer file, unlike the plain text answer files used by earlier versions of Windows. You can use this answer file in two ways; as an argument provided on the command line for Setup.exe or as a file when booting from the DVD media.

When running Setup.exe from the DVD directly the switch /unattend: should be used. The switch defines the location and name of the XML answer file, for example, D:\Setup.exe /unattend:A:\VistaAnswer.xml.When booting from the DVD, the setup program scans all available drives for a file called Autounattend.xml. This answer file can be on any local drive available at boot but would usually be a removable disk such as a floppy diskette or USB key.

Windows Deployment ServicesWindows Deployment Services (Windows DS) is the successor to Remote Installation Service (RIS). RIS is an optional component of a Windows 2003 Server install. RIS enables network users to carry out a file-based installation of Windows clients onto a computer without an operating system using a computer equipped with a Pre-boot Execution Environment (PXE) network card.

Because Windows Vista installation is WIM based, and not file based, Vista is incompatible with RIS. By installing Windows Server 2003 Service Pack 2 (estimated release Q1 2007) onto an existing Windows Server 2003 RIS server, the RIS service updates to support Windows DS. Windows DS installs WIM based distributions such as Vista and the upcoming “Longhorn” server product.

To enable WDS on a Windows Server 2003 SP2 RIS server, you must run the following command, WDSUTIL /initialize-server. This command configures the RIS server as a mixed mode RIS\WDS server to support the transition between the old RIS and new Windows DS format.

Systems Management ServerSMS provides the most flexible means to operating systems on a network. Using the Operating Systems Deployment Feature Pack (OSDFP) SMS provides administrator control over targeting of users or systems, elevation of user rights for installation, specifying when an installation can take place, user interaction levels, controlled restarts, security accounts, and more. This paper focuses on how administrators can use SMS 2003 R2 and OSDFP to deploy Windows Vista to users and computers across their networks.

5

SMS 2003 R2 eases the burden on support departments by allowing operating system installation with a special account that has administrative privileges and to which the user has no access. This account enables the SMS client to perform administrative tasks, while limiting user account privileges.

Windows Vista Upgrade AdvisorThe Windows Vista Upgrade Advisor is available from the Get Ready for Vista site. Primarily designed as an interactive tool, it can run on Windows XP or Windows Vista computers to advise on the suitability of the system to run various editions of Windows Vista.

When run on a Windows XP computer it will advise on the compatibility of software and hardware running on that XP computer. All hardware should be connected and enabled before running the compatibility tool.

When run on a Windows Vista system, its primary purpose is to identify what editions of Windows Vista can run on that system. This information is useful to a user who has upgraded their hardware to see what enhanced additions of Vista will now run. They could then make use of Windows Vista Live Upgrade to upgrade their version of Vista.

Supplied with the Windows Vista Upgrade Advisor is a command line command Winsat.exe. This command line command can collect information about the hardware using a variety of tests. The results of these tests can log information to an XML file.

Windows Vista Hardware AssessmentWindows Vista Hardware Assessment Solution Accelerator is a centralized and agentless tool designed to assess the readiness of client computers for Windows Vista. It quickly inventories computers, identifies the supported Windows Vista experience, and recommends specific hardware upgrades as appropriate. This tool runs from a single networked PC to assess all PCs within the network with proper network credentials.

Specifically, this tool provides detailed reporting that clearly shows the three different levels of Vista readiness of existing PCs:

Clients that are incompatible with Windows Vista

Clients ready for the Windows Vista Capable Experience

Clients ready for the Windows Vista Premium Ready Experience

Windows Automated Installation KitThe Windows Automated Installation Kit (WAIK) downloads from Microsoft as a DVD image file that you must burn to a DVD disk before installation. You can download WAIK from the Microsoft Download Center. You can also download WAIK documentation from the same site.

WAIK provides various tools, including:

Windows System Image Manager

Windows PE Tools

The Windows System Image Manager is a graphical tool that creates the XML file that you use in scripted Windows Vista Installations. You can save these files for later modification.

The Windows PE tools include tools to build WIM images, make modifications to these images, and modify an offline version of Windows Vista prior to Windows Vista image capture.

6

User State Migration Tool 3.0You can download the latest version of the User State Migration Tool (USMT) from the Microsoft Download Center. USMT migrates files and settings during deployments of Windows Vista for multiple users. Version 3.0 adds support for migrating encrypted files and for encrypting the stored copy of migrated files.

Microsoft Solution Accelerator for Business Desktop Deployment 2007The Solution Accelerator for Business Desktop Deployment (BDD) provides best-practice guidance for desktop deployment. BDD assists companies who want to reduce thetime, effort, and cost when deploying standardized desktops.BDD provides Zero Touch and Lite Touch deployments for desktop computers.

BDD provides a Deployment Workbench, which acts as a font end for the following tools:

Windows Automated Installation Kit

Application Compatibility Toolkit 5.0

User State Migration Tool 3.0

To use BDD on Windows XP you must install Microsoft Management Console 3.0 (MMC 3.0.) You can download BDD from the Microsoft Download Center.

Application Compatibility Toolkit 5.0The Application Compatibility Toolkit (ACT) enables you to:

Inventory applications

Analyze compatibility

Track fixes

ACT validates migrations and manages these applications once they are in production use. You can analyze hot fixes and Service packs against your inventory of application to ensure compatibility. You can download the release candidate of ACT from Microsoft TechNet.

Vista Volume License KeysWindows Vista is the first product to support Volume Activation 2.0 (VA 2.0). There are two types of volume activation keys:

Multiple Activation Key (MAK): Microsoft must activate Computers using MAK keys. You can complete activation either individually or by proxy activation.

Key Management Services (KMS): An internal server hosts KMS and activates internal clients automatically. You must have a minimum of 25 clients to run KMS and clients must contact the KMS server on an ongoing basis otherwise they will become feature limited.

You can find more information on the Volume Licensing - Volume Activation website.

Introducing Microsoft Systems Management Server 2003 R2

SMS 2003 R2 is a graphical tool that enables system administrators to manage change across large network environments. Its capabilities enable organizations to keep systems updated and secure, and to provide the right software at the right time to the right user.

7

FeaturesSMS 2003 R2 enables system administrators to exert a high degree of centralized or decentralized control over desktop and mobile computers. SMS 2003 provides the following features: ● Hardware and software inventory● Automated software deployment and provisioning ● Software usage tracking● Software update and patching tools● Remote control tools ● System status reporting● Operating System Deployment (OSD)● Windows Mobile Device Management

SMS 2003 R2 includes functional improvements in existing tools and extra functionality, including: ● System vulnerability assessment scanning● Inventory Tool for Custom Updates (ITCU) for third-party and customer

applications

SMS 2003 R2 Operating System Deployment Feature Pack (OSDFP) provides tools and methods to deploy operating systems images to computers. You can use these images with Windows Deployment Services (Windows DS) to deploy images to computers without an operating system installed.

BenefitsThe functions and tools in SMS 2003 R2 allow system administrators to perform system and device configuration tasks in a controlled, staged manner, according to the support policies within an organization. This control means that you can deploy operating systems packages and applications in a way that enables you to maintain service at a level appropriate to the organization and without intrusive interruptions to network operations.

For example, Windows Vista can be deployed to users or computers within an organization on a specific basis—perhaps initially to a pilot group, and then later to more departments and general users. The Background Intelligent Transfer Service (BITS) can significantly reduce the demands on network bandwidth when distributing WIM images. BITS uses spare network capacity to transfer SMS Image packages to the local distribution points. Client computers will then access these distribution points when installing WIM images.

System Requirements for Windows VistaTo ensure adequate performance, Microsoft recommends that client computers conform to minimum processor, memory, graphic card, and disk space requirements. There are two types of certification programs for hardware:

Windows Vista Capable

Windows Vista Premium Ready

8

Computers which meet the Windows Vista Capable computers specifications will meet or exceed the requirements to deliver the core Windows Vista experiences. However, some premium features may require advanced or additional hardware.

A Windows Vista Premium Ready computer delivers an even better experience than a Windows Vista Capable computer. Computers meeting the Windows Vista Premium Ready requirements can deliver Windows Aero.

When upgrading from earlier versions of Microsoft Windows, organizations must ensure that their computers meet the minimum Windows Vista requirements, as shown in the following table.Table 1 System requirements for Windows VistaComponent Windows Vista Capable Windows Vista Premium Ready

Processor Modern processor (at least 800 MHz)

1 GHz 32-bit (x86) or 64-bit (x64) processor

Memory 512 MB 1 GB

GPU DirectX 9 Capable (WDDM Driver recommended)Minimum 800x600 SVGA

Windows Aero CapableDirectX 9-class GPU that supports:

A WDDM Driver Pixel Shader 2.0 in

hardware 32 bits per pixel Adequate graphics

memory

Graphics Memory - 128 MB

HDD 20 GB 40 GB

HDD Free 15 GB 15 GB

Optical Drive CD-ROM DVD-ROM

Describing the SMS Software Distribution ProcessIn order to understand what is required to deploy operating system images by using SMS, administrators should be familiar with the following SMS object types that the image deployment process uses:● Collections● Packages● Programs● Advertisements● Distribution points● Clients

CollectionsCollections are groups of SMS resources, such as users, user groups, or computers, against which you target software deployments. A collection’s membership is controlled

9

by membership rules: a direct membership rule specifies arbitrary resources that do not have common attributes in the SMS database, whereas a query rule dynamically adds resources that have common criteria, such as the same operating system or service pack. The system administrator uses the SMS Administrator Console to define collections.

Although SMS has a number of default collections, it is often best to create custom collections for operating system deployment. This is because administrators usually want to deploy operating systems selectively to specific departments, users, or computers.

Query-based rules offer more flexibility and future proofing for collections. For example, if new computers are added to an organizational unit in Active Directory, then at the next Active Directory discovery they are automatically added to the relevant collection in SMS.

When planning to deploy Windows Vista, administrators should consider the following questions:● Will Windows Vista be deployed to users or to computers?● Will Windows Vista first be deployed to a small number of users, and then later to

larger numbers of users?● How will the pilot group be selected? For example, will it include users from a

single department, or users from different areas throughout the organization?● Do different users or groups require different features or components of Windows

Vista?

Answers to these questions provide information for creating collections. For example, if the administrator wants to deploy Windows Vista to pilot computers, he or she must create a collection that includes the pilot computers.

Note: The number and descriptions of default collections is based upon the SMS service pack level and additional tools installed. The examples shown in this paper include the default collections for SMS 2003 R2.

Image PackagesAn image package is the set of installation source files that SMS must manage and distribute for operating system deployment. The administrator typically specifies a source folder when creating a package in SMS. For Windows Vista, this source folder would be a folder containing a pre-prepared WIM file. You will discover how to prepare this WIM file later in this paper.

ProgramsPrograms are part of the package configuration in SMS, and most importantly, define the way that the operating system should be deployed. Program settings control how the user will be notified of an operating system upgrade, if it is mandatory or if it can be differed. Licensing and network configuration, such as domain membership can also be configured through the SMS program.

AdvertisementsAdvertisements tie packages and programs together with collections, enabling administrators to target operating system deployment to collections of computers or users. An advertisement specifies a package and program, and the collection to which it will be advertised or deployed. Advertisements have a schedule that controls when the operating system deploys and whether users can accept, postpone, or reject the

10

operating system package. The advertisement also controls how the package uses the network for the installation.

Advertisements contain a number of settings that give administrators a fine degree of control over how the software is deployed to the client. It is possible to control the advertisement schedule and start, and whether the advertisement is mandatory.

Non-mandatory advertisements allow users to choose whether to install the software package, and when. For example, this setting could allow users taking part in the pilot distribution to upgrade the operating system at a time that impacts them the least.

Mandatory advertisements force the installation to occur according to the specified schedule without giving the user a choice. This option could be used schedule the main roll out to happen during specific, controlled, non-production times.

Distribution PointsDistribution points are SMS site systems that store designated image packages for deployment to SMS clients. When the SMS client receives and processes a relevant advertisement, the client then contacts a distribution point to download the Windows Pre-installation Environment (WinPE) and then start the installation process. Administrators can set up multiple distribution points to provide good connectivity to the image package source files.

For example, an administrator can place distribution points in branch offices or in each Active Directory site. Distribution points can be managed individually or as part of a distribution point group. This arrangement simplifies administration of multiple image packages across several distribution points.

ClientsSMS clients are computers that run Windows and have the SMS client software installed. The SMS client software enables SMS site systems on the network to manage and control the computer. There are two types of SMS client: ● Advanced Client. The Advanced client is the supported client for SMS 2003 R2 on

Windows 2000 and later operating systems. The SMS Advanced Client introduces features such as the ability to roam between SMS 2003 sites and to use BITS for package download, which enables more efficient use of network bandwidth.

● Legacy Client. The Legacy client exists to connect older operating systems, such as Windows NT 4.0 and Windows 98. SMS 2003 SP2 and later does not support the legacy client on any computer capable of running the SMS Advanced client.

ReportingSMS can produce reports that record the software deployment progress and highlight problems. These reports help identify any issues and allow administrators and managers to see that a software pilot or rollout is on track. SMS 2003 R2 reports are Web-based so non-administrative users, such as department managers or directors, can be given direct access to up-to-date information about the network.

InventoryOne of the most powerful functions of SMS 2003 R2 is the ability to record inventory information from clients. This inventory data is of two types: ● Hardware Inventory. SMS Hardware Inventory records computer information such

as processor speed and memory, Add or Remove Programs data, and software update information

11

● Software inventory. SMS Software Inventory searches the client computers' hard disks and generates a detailed breakdown of installed software by vendor, listing specific files such as .exe files, and provides the ability to collect specified configuration or log files for storage and analysis.

Inventory information can be used in reports or queried by using a tool called Resource Explorer.

Planning Windows Vista DeploymentAs with any large network operation, good planning is the key to success. The Windows Vista deployment process must take into account a large number of factors, so it is essential that network administrators formulate a properly structured deployment plan.

Applying Microsoft Operations Framework The Microsoft Operations Framework (MOF) provides operational guidance that enables organizations to achieve mission-critical system reliability, availability, supportability, and manageability of Microsoft products and technologies. With MOF guidance, organizations can assess their current IT service management maturity, prioritize processes of greatest concern, and apply proven principles and best practices to optimize management of the Windows Server platform.

This paper deals with the Changing and Operating quadrants of the MOF process model.

Figure 1 The Microsoft Operations Framework quadrants

For more information on MOF, see the Microsoft Operations Framework Web page.

12

Planning Distribution PointsTo deploy software effectively by using SMS 2003, it is necessary to ensure that an organization’s network has enough distribution points in place. This paper covers a single site environment, so the main consideration is that the distribution points covering the site can cope with the number of clients and the number of packages to be distributed.

Additional SMS sites may require additional distribution points, and if the network supports dial-up, VPN, or WLAN clients, then additional consideration must be given to whether these systems should be allowed to receive particular software packages, due to bandwidth constraints. In these environments, the configuration of SMS local and remote roaming boundaries can control the way clients behave.

Note: Because of the large size of WIM files, planning the availability and distribution of these files is of critical importance to the success of deploying Windows Vista with SMS 2003 R2. Not creating a detailed plan on how to distribute these images will cause significant impact on the operation of the organizations production network.

Identifying Suitable Client ComputersIf an organization has a mix of computer hardware, it is necessary to evaluate existing systems with regard to the minimum requirements described in the earlier section on "System Requirements for Windows Vista." SMS 2003 R2 can facilitate this process by using queries, and by specifying criteria for attributes such as processor, memory, and logical disk under the System Resource attribute class. Collections can then be defined using one or more of these queries.

Additional specialist tools may also be used. Hardware can be evaluated using the Windows Vista Hardware Assessment tool and software can be evaluated using the Application Compatibility Toolkit described in the section “Deployment Techniques and Tools.”

Deployment ScenariosWhile planning the Windows Vista deployment, it is necessary to examine the types of deployment an organization may require. Typical deployments are new installations or upgrades.

New DeploymentFor new deployments, administrators need not consider any existing versions of operating systems on the computers where Windows Vista will be installed. Administrators should choose the desired method of installation, create WIM files if required, and proceed with installation.

UpgradeIn an upgrade deployment, the data and user settings on the existing computer is maintained although this does not necessarily include applications. This deployment method means that after installation users experience the same environment that they received from the earlier operating system. Some configuration, and therefore user training may be required to maximize the benefits that Windows Vista offers.

13

Checking Network BandwidthTo deploy Windows Vista using SMS 2003 R2 requires at least one distribution point server in each SMS site. The nature of the network infrastructure or the deployment plan may require additional distribution point servers, and factors to consider include:● Network bandwidth between SMS clients and SMS distribution points● Number of SMS clients installing Windows Vista concurrently● Existing network usage level

Assessing Working HoursThe Windows Vista deployment plan must consider user working hours. This consideration can help ease deployment issues related to network bandwidth and service interruption. In addition, if an organization has shift workers, then consideration must be given for pilot users, support, and training on all relevant shifts.

Informing UsersAny large-scale or large-impact software rollout should include a project stakeholder meeting that brings together representatives of all parties that are affected by the project. For a Windows Vista deployment, these stakeholders must include end-user representatives.

A stakeholder meeting is a good time to outline benefits from the Windows Vista deployment. The meeting can also directly outline what the deployment will and will not achieve, thereby setting user expectations.

The end-user representatives may also be able to identify good candidates for the pilot of the Windows Vista deployment. Pilot deployment users should include users in a variety of roles. This diversity ensures that issues around multiple configurations and application compatibility can be tested, and that any issues are identified and fed back to the IT department. The end-user stakeholder representative can also keep the end-user community informed by acting as a liaison throughout the project.

Training UsersUser training is another aspect that the deployment plan must address. Although the new user interface and product capabilities were designed to allow users to discover and use these features intuitively, users will benefit from access to training and support resources.

The deployment plan should include pilot user training as a high priority, as pilot users are the first to use the new software. Pilot users can then help deal with user requests as Windows Vista is deployed across the organization. It also may be possible to create product champions within departments or locations to assist in the transition to the new release.

14

IIDeploying Windows Vista with Systems Management Server 2003 R2Creating the Reference Image

In order to deploy Windows Vista using SMS 2003 R2, you need to create a WIM file. Creating this WIM file is broken down into four steps:

Build a lab environment

Build an answer file

Build a master installation

Create an image

Building a Lab EnvironmentThe first step in creating an image is to build a clean environment where this image can be built. You will need:

Technician Computer

Reference Computer

Image Server

Windows AIK

CD Software to create CD from ISO Image

Windows Vista DVD Media

The Technician computer is where you will install the tools required to build the Windows PE CD to use when creating the image. This computer can be running Windows XP, Windows Server 2003 or Windows Vista. The following table lists the tools and files required during the process:

15

Table 2 and Files Used on Technician ComputerTool or File Purpose

Windows System Image Manager (Windows SIM)

This graphical tool enables you to create answer files used for the building of the clean Windows Vista installation on the reference computer

Copype.cmd This command enables you to create a local WinPE build directory

Oscdimg.exe Builds a WinPE ISO image from the local WinPE directory

Imagex.exe Copied to the WinPE tools directory so that the WinPE CD will be able to capture the reference computer image

Install.wim Windows Vista Installation WIM file from Windows Vista Media

Once you have installed Windows AIK onto the technician computer you are ready to create your answer file.

Building an Answer FileThe cleanest way to create a reference computer is to use an answer file (Autounattend.xml) with the Windows Vista DVD media to automatically install the operating system. The following procedure can be used to create the answer file:

1. Insert the Windows Vista product DVD into the local DVD-ROM drive on the technician computer.

2. Navigate to the \Sources directory on your DVD-ROM drive. Copy Install.wim from the product DVD to a location on your technician computer, for example, C:\Vista_Installation.

3. Open Windows SIM by clicking Start, All Programs, Microsoft Windows AIK, and then clicking Image Manager.

4. On the File menu, click Select Windows Image.

5. Navigate to the location where you saved Install.wim, and then click Open.

6. If you see a message that a catalog does not exist, click Yes to create a new one.

Figure 2 Window SIM Catalog Error7. On the File menu, click New Answer File.

8. Add the components in the following table to your answer file by right-clicking the component in the Windows Image, Components pane and then selecting the appropriate configuration pass.

16

Table 3 Unattended Answer File ComponentsComponent Configuration Pass

Microsoft-Windows-Setup\DiskConfiguration\Disk\CreatePartitions\CreatePartition 1 Windows PE

Microsoft-Windows-Setup\DiskConfiguration\Disk\ModifyPartitions\ModifyPartition 1 Windows PE

Microsoft-Windows-Setup\ImageInstall\OSImage\InstallTo 1 Windows PE

Microsoft-Windows-Setup\UserData 1 Windows PE

Microsoft-Windows-Shell-Setup\OOBE 1 Windows PE

9. Verify that the result looks like Figure 3.

Figure 3 Unattended Answer File Components Result10. In the Answer File pane, all the settings you added are displayed. Select and

configure each setting as specified in the following table:Table 4 Unattended Answer File Component ValuesComponent Value

Microsoft-Windows-Setup\DiskConfiguration WillShowUI = OnError

Microsoft-Windows-Setup\DiskConfiguration\Disk DiskID = 0

WillWipeDisk = true

17

Component Value

Microsoft-Windows-Setup\DiskConfiguration\Disk\CreatePartitions\

CreatePartition

Extend – false

Order = 1

Size = 16000

(Note: This example creates a 16

GB partition.)

Type = Primary

Microsoft-Windows-Setup \DiskConfiguration\Disk\ModifyPartitions\

ModifyPartition

Active = true

Extend = false

Format = NTFS

Label = OS_Install

Letter = C

Order = 1

PartitionID = 1

Microsoft-Windows-Setup\ImageInstall\OSImage\ WillShowUI = OnError

Microsoft-Windows-Setup\ImageInstall\OSImage\InstallTo DiskID = 0

PartitionID = 1

Microsoft-Windows-Setup\UserData AcceptEula = true

Microsoft-Windows-Setup\UserData\ProductKey Key = Product key

WillShowUI = OnError

Microsoft-Windows-Shell-Setup\OOBE HideEULAPage = true

ProtectYourPC = 3

SkipUserOOBE = true

Microsoft-Windows-Setup\DiskConfiguration WillShowUI = OnError

Microsoft-Windows-Setup\DiskConfiguration\Disk DiskID = 0

WillWipeDisk = true

Microsoft-Windows-Setup\DiskConfiguration\Disk\CreatePartitions\

CreatePartition

Extend – false

Order = 1

Size = 16000

(Note: This example creates a 16

GB partition.)

Type = Primary

Microsoft-Windows-Setup \DiskConfiguration\Disk\ModifyPartitions\

ModifyPartition

Active = true

Extend = false

Format = NTFS

Label = OS_Install

Letter = C

Order = 1

PartitionID = 1

Microsoft-Windows-Setup\ImageInstall\OSImage\ WillShowUI = OnError

11. Verify that the result looks like Figure 4.

18

Figure 4 Unattended Answer File Component Values Results12. In Windows SIM, click Tools, and then click Validate Answer File. The setting values

in the answer file are compared with the available settings in the Windows image.

13. On the File menu, click Save Answer File. Save the answer file as Autounattend.xml.

14. Copy Autounattend.xml to the root of removable media such as a USB Flash Device or floppy disk.

Building a Master InstallationOnce the answer file has been created, you can create your reference computer by following this procedure:

1. Turn on the new computer and insert the removable media containing the answer file (Autounattend.xml) and the Windows Vista product DVD.

2. Restart the computer (CTRL+ALT+DEL). Windows Vista Setup (Setup.exe) starts automatically and searches all removable media for an answer file named Autounattend.xml.

3. After Setup is complete, ensure that all customizations in the answer file were applied as specified.

4. Install necessary service packs and patches.

5. Install any other required applications.

19

Note: Careful thought should be given as to what applications to install as part of the image, and what applications to install using SMS. Best practice is to keep the base images as small as possible and install applications with SMS where possible. This practice enables the number of different OS images required to a minimum.

6. Install the Advanced SMS client.

7. From the command prompt, type the following command to reseal (generalize) and shut down the computer:

C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdownThere is no need to install sysprep onto the Vista image as Sysprep is installed as part of Windows Vista. Computer specific information will stripped from the computer by Sysprep and the computer shut down. Do not boot the computer yet because if you do, mini-setup will start to configure the computer and undo the changes made by Sysprep.

Note: The Master Installation should not be joined to the domain. This will happen later in the process when the image is deployed to a production computer.

Creating an ImageNow that the Master Installation has been prepared for imaging, you are nearly ready to take an image. Before you can take an image, you must create the WinPE media used for capturing the image. To create the WinPE media follow this procedure:

1. On your technician computer, open a command-line window with administrative permissions.

2. Type Cd \Program Files\Windows AIK\PE Tools to change to the PE tools directory.

3. Type Copype.cmd x86 C:\WinPE_X86, where x86 is the processor architecture and C:\WinPE_x86 is the destination directory.

Note: Replace x86 with amd64 or ia64 as appropriate.a.

4. Type Mkdir C:\WinPE_x86\ISO\Tools to create a directory to hold Imagex.exe.

5. Type Copy “C:\Program Files\Windows AIK\Tools\x86\Imagex.exe” C:\WinPE_x86\ISO\Tools to copy Imagex.exe to the tools subdirectory created in the previous step.

6. Use notepad to create an exclusions file for Imagex.exe and save it to the same location as Imagex.exe. Call the file Wimscript.ini:

[ExclusionList]

ntfs.log

hiberfil.sys

pagefile.sys

"System Volume Information"

RECYCLER

Windows\CSC

[CompressionExclusionList]

20

*.mp3

*.zip

*.cab

\WINDOWS\inf\*.pnf

7. Type Cd \Program Files\Windows AIK\Tools\PETools\ to change back to the

PETools directory.

8. Type Oscdimg -n –bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso to create the WinPE ISO image.

9. Use your CD burning software to transfer this ISO image to a CD disk. Refer to the

manufacturers instructions for information on how to transfer an ISO image.

After you create the WinPE image, you are ready to capture the Master Installation

image. Complete the following procedure to capture the image to a network share.

1. Prepare the image server to receive the image by creating or identifying a network

share. You will need approximately two GB for a base Windows Vista image. Ensure

that the share is secured using permissions and that you know the username and

password required to access this share.

2. Prepare the reference computer by ensuring that it is set to boot from the WinPE CD

media. Refer to the manufacturer’s instructions to configure the Master Installation to

boot to CD.

3. On the Master Installation, insert your Windows PE media and restart the computer.

Windows PE starts and launches a command-line window.

4. Wait for WinPE to startup.

5. Type D:\Tools\Imagex.exe /compress fast /capture C: C:\VistaImage.wim "Vista Enterprise" /verify to capture the image where C: is the volume you are imaging; C:\

VistaImage.wim is the file you are capturing too; and "Vista Enterprise" is the image

description.

6. Type Net use X: \\Server\Share to map a network drive where X: is the drive you

wish to map and \\Server\Share is the UNC path of the share you wish to use.

7. Type Copy C:\VistaImage.wim X: to copy the image file where C:\VistaImage.wim is

the name of the image and X: is the drive mapped previously.

The WIM image is now ready to be imported into SMS.

Importing the WIM ImageOnce the WIM image has been captured, you will import the WIM image into SMS 2003 R2. This process makes use of a wizard called The New Operating System Package Wizard.

Once this step is complete you will be ready to distribute the WIM image to SMS distribution points.

To import the WIM image, carry out the following procedure:

1. Start SMS Administrator by clicking Start, All programs, Systems Management Server, SMS Administrator Console.

21

2. Double-click Site Database, and then double-click Image Packages.

3. Right-click Image Packages, click New and then click Operating System Package.

4. In the New Operating System Package Wizard, click Next.5. In the Package Name, type the required package name (for example,

VistaEnterprise.)

6. In the image file, browse and select the WIM file that was copied from the Windows Vista Installation Master (e.g. Z:\Images\Sysprep\VistaEnterprise.Wim.)

7. In the Package Source, browse and create a folder to contain the image. (for example, \\SMSSERVER\Images\Wim\VistaEntV1.00) then click Next.

8. Click Finish to import the Image.

Figure 5 Image Packages9. Verify that the following files exist:

Figure 6 Image Packages Files

Managing Distribution PointsBefore the image can be used, it must be distributed to appropriate SMS distribution points. These distribution points should be located close to the clients that will use them. There should be at least one distribution site per physical LAN location but it may sometimes be better to have more than one. If it is a large site or has many computers for example.

22

Configuring the Distribution PointTo distribute the image files to a distribution point or distribution points, carry out the following procedure:

1. Double-click the Operating System package (for example, VistaEnterprise.)

2. Right-click Distribution Points, click New and then click Distribution Points.

3. If the Welcome to the New Distribution Points Wizard screen appears, click Next.4. Select appropriate Distribution Points and then click Finish.

Figure 7 SMS Distribution Points

Checking the Distribution ProcessOnce the distribution points have been configured, SMS server will start to distribute them. Be aware that because of the large size of the image files, this process can take some time. It is worthwhile checking the distribution process to make sure that it is proceeding without error.

Carry out the following procedure to check the distribution process.

1. Double-click System Status, double-click Package Status and then double-click the Image Package (for example, VistaEnterprise.)

2. Right click the Distribution Site (for example, LON – London,) click Show Messages and then click All.

3. In the Status Messages:Set Viewing Period dialog, either choose a specific date and time or select a time period, and then click OK.

23

Figure 8 Status Messages:Set Viewing Period4. In the SMS Status Message Viewer for <Site Code> <Site>, (for example, <Lon>

<London>,) look for Message ID 2342 and 2330.

Figure 9 SMS Package Status Message Details

You have now verified the successful distribution of your operating system image.

The Operating System ProgramIn order to distribute the Image Package to computers you must create and optionally, customize, an Operating System Program. This Operating System Program contains the logic required to distribute the WIM image.

Program WizardTo help you create the Operating System Program, SMS 2003 R2 will launch a Wizard. To configure this wizard, follow this procedure:

1. Start SMS Administrator, double-click Site Database, double-click Image Packages and then double-click the previously imported image (for example, VistaEnterprise.)

2. Right click Programs, click New and then click Operating System Program.

3. In the New Operating System Program Wizard, click Next.4. Type your Program name (for example, DeployVista), and then click Next.

24

Figure 10 Operating System Program Wizard5. Enter the product key and then click Next.

Figure 11 Operating System Program - Licensing Settings6. Click Domain and type the Domain name (for example, SMSDOMAIN.), click the Set

button and type the details of an account that you will use to join the computer to the domain (for example, SMSDOMAIN\DomainJoin), click OK, and then click Next.

25

Figure 12 Operating System Program - Domain Settings7. Click Finish.

8. If a dialog box appears saying SMS Distribution points will require updating, click OK.

9. Verify the contents of the folder containing the Image:

Figure 13 Operating System Package FilesYou have now created the Operating System Program.

Program Customization The Program default settings do not necessarily suit all types of distribution so you may decide to customize the Operating System Program:

1. Double-click Site Database, double-click Image Packages, and then double-click the Image Package (for example, VistaEnterprise).

2. Click Programs, right click the previously created Operating System Program (for example, DeployVista,) and then click Properties.

26

3. On the General tab you can edit the following settings:

Comments: Comments for the Operating System Program.

Category: Displays the Operating System Program in the selected category in the Advertised Programs list.

Run another program first: Optionally deply another SMS application package before installing this image.

Disable: Temporarily disable an image from being used.

Figure 14 Operating System Program - General4. On the User Notification tab you can customize the following options:

Department Name: Type the department name you wish the user to see in the notification.

Rich Text Document: Select a rich text file that you wish to display to the user during the application of the image to the computer. The default file only includes an SMS 2003 image. Any text file you select will be copied to the distribution point(s) for you.

User Postpone Options: If the users is logged on, they can be allowed to postpone image application until a more convenient time. Specify those settings here.

27

Figure 15 Operating System Program - User Notification5. On the Windows tab you can customize the following options:

Organization name: You can select to keep the existing organization name if set, or specify your required organization name.

Time Zone: You can select to keep your existing time zone if set, or specify your required time zone.

Figure 16 Operating System Program - Windows6. On the Licensing tab you can customize the following options:

Use this product key: Enter the product key to be used for this image.

Use this encrypted volume product key: Enter an encrypted version of your product key.

28

Specify no product key required: Users will enter product keys manually or use are using Vista Volume Key Services on your network. Volume Key Services will provide a product key automatically.

Figure 17 Operating System Program - Licensing7. On the Network tab you can customize the following options:

Use static IP address: If the computer currently uses a static IP address, the static IP address can be preserved onto the new computer.

Note: WinPE will still need a dynamic address during the image application process so you must have a DHCP server available to the LAN where the build is taking place.

Workgroup or Domain: Select the Workgroup or Domain membership of the computer.

Domain account: If joining a domain, specify the credentials of an account with sufficient privileges to join the computer to the domain.

Local administrator password: Select to create a random administrator password. Domain administrators will automatically have administrator access to the computer and the local administrator password can be changed.

29

Figure 18 Operating System Program - Network8. On the SMS Client tab you can customize the following options:

SMS Client ID: Select to preserve the SMS client ID or to create a new one.

Site Assignment: Select to preserve the site assignment, allow the client to locate its site automatically or to always assign the client to a specific site.

Figure 19 Operating System Program - SMS Client9. On the Advanced tab you can create new actions to take place during certain

phases of the Image application. The table below documents these options:

30

Table 5 Operating System Program - AdvancedPhase Action Type Description

Validation Custom A user defined action (for example, Run a script to confirm hardware compatibility)

State Capture Custom A user defined action (e,g. Scripts to turn off Windows features that will interfere with Scanstate.exe)

Capture User State Run USMT Scanstate.exe

Connect to UNC Path Used to store user state

Reboot System Reboot computer

Preinstall Custom A user defined action (for example, Copying some custom files to the computer)

Connect to UNC Path A network connection (for example, Used to store custom files)

Reboot System Reboot computer

Postinstall Custom A user defined action (for example, Copying some custom files to the computer)

Connect to UNC Path A network connection (for example, Used to store custom files)

State Restore Custom A user defined action (for example, Copying some custom files to the computer)

Connect to UNC Path A network connection (for example, Used to store custom files)

Restore User State Run USMT Loadstate.exe

Run Software Distribution Program

Deploy SMS software packages to the computer at build time

10. Click OK.

11. If you receive a message stating that Distribution Points Need to be Updated, click OK.

Identifying WorkstationsMeeting the minimum hardware requirements is not the only requirement for identifying which computers can support Windows Vista. Hardware devices and drivers, as well as applications all need to be validated before a migration takes place. Testing computers on an individual basis with tools such as the Windows Vista Upgrade Advisor would be difficult in a medium to large organization. Microsoft have developed two tools to help in this situation:

Vista Hardware Assessment Tool

Application Compatibility Toolkit v5.0

31

Note: These two tools will not complete all tasks required to verify software and hardware compatibility for migration. They will flag any issues that require further verification to reduce the timescales required.

Hardware AssessmentThe Windows Vista Hardware Assessment Tool (previously called the Vista Readiness Advisor) is a tool that can scan your entire network from a single location. It is designed to indicate if any problems are likely to occur with hardware or device drivers currently used in computers within your organization.

The tool is installed onto a workstation that can connect to all computers within your organization and a simple configuration wizard is completed. This configuration wizard details the scope of the computers that you wish to analyze and also the credentials you wish to use to connect to these computers.

Depending on your organization size, the configuration tool will take from a few minutes to several hours to complete its run. Results are stored in a SQL Express 2005 database so that further differential scans and reports may be run from the database.

The first type of output that the Hardware Assessment Tool produces is a Word document. This document is a finished report regarding the status of your computers and their drivers. Problems are identified and easy to understand tables and figure indicate exactly where you are and where you could be with minor changes.

Figure 20 Windows Vista Hardware Assessment - WordThe second type of output that is produced is a spreadsheet. This spreadsheet has summary and detailed statistics about your current environment which you can use as a basis for planning.

32

Figure 21 Windows Vista Hardware Assessment - ExcelThe Windows Vista Hardware Assessment tool can give you a useful insight into the status of your existing hardware and help you estimate costs for your upgrade.

Application CompatibilityThe second useful tool is the Application Compatibility Toolkit v5.0 (ACT5). This tool is designed to:

Collect application information

Analyze application information

Track the results of testing

Figure 22 BDD 2007 - WorkbenchA wizard enables the easy configuration of agents to be deployed to computers. These agents can be easily distributed via SMS 2003 R2 and will automatically stop collection at a predefined time. These agents can collect an inventory of Applications, Internet Explorer usage, monitor situations where administrator access is required and look for specific Windows Vista compatibility issues.

33

Figure 23 BDD 2007 - Capture Agent Configuration

Once the information has been collected, ACT5 can analyze this information for issues. The criteria used for analysis can be downloaded from a constantly updated Microsoft source and this community information used to help you make informed decisions regarding application compatibility.

Once application compatibility issues have been identified, the status of the issues can be tracked in the ACT5 SQL database. Applications that have issues and are installed on the majority of computers can be granted a higher priority than a few non-business critical applications. As compatibility issues are solved, this can also be marked into the database.

Defining CollectionsOnce your environment has been analyzed and all issues solved it is time to start the deployment. It is good practice to carry out a pilot implementation before rolling out to a wider audience to pick up any issues that have been missed by testing. Be prepared to analyze failures in the pilot stage and change practices to solve these failures. Try to pick a representative group of computers to give you the best possible validation for deployment.

Pilot CollectionBecause there are likely to be relatively few computers in a pilot deployment, you might find that something as simple as specifying the names of computers to be deployed will work. To do this you can create a Collection based upon

To create the pilot collection, follow this procedure:

1. Double-click Site Database, and then double-click Collections.

2. Right click Collections, click New, and then click Collection.

3. The General tab supports the following customizations:

Name: The display name of the collection.

Comment: An administrative comment.

34

Figure 24 Collection Properties - General4. The Membership Rules tab is where you can select the direct membership rules to

add your required clients:

5. Click the Computer Icon.

6. In the Create Direct Membership Rule Wizard dialog, click Next.7. Against Resource Class, select System Resource.

8. Against Attribute name, select Name.

9. Against Value, type the wildcard character %, and then click Next. This will allow you to select from all computer names.

10. In the Collection Limiting dialog box, type the name or browse for an existing collection you wish to use as the initial source (for example, All Windows XP Systems.)

11. Select the resources you wish to add as direct members, click Next and then click Finish.

Figure 25 Collection Properties - Membership Rules12. Click OK to close the dialog.

35

13. Right click the Collection just created, click All Tasks, and then click Update Collection Membership.

14. Right click the Collection just updated, and then click Refresh. Verify the membership is as expected.

This collection can now have the Install Image advertised to it for installation.

Computers Not Vista CapableThe following query or collection can be used as a starting point to decide if a computer is not currently capable of running Windows Vista:

Figure 26 Criteria - Not Vista Capable

Windows Vista Capable ComputersThe following query or collection can be used as a starting point to decide if a computer is currently capable of running Windows Vista:

Figure 27 Criteria - Windows Vista Capable

36

Windows Vista Premium Ready ComputersThe following query or collection can be used as a starting point to decide if a computer is currently capable of running Windows Vista Premium:

Figure 28 Criteria - Windows Vista Premium

Note: Relying on Video Adaptor RAM being 128 MB or higher is not a reliable indicator that Windows Vista Aero will run. Other requirements can be seen in the earlier section on Windows Vista Hardware Requirements.

Advertising the Install ImageAfter you have configured collections to receive the Windows Vista install image, you can advertise the image to these collections. Follow this procedure to advertise the install image to a collection:

1. Double-click Site Database, and then click Advertisements.

2. Right click Advertisements, click New, and then click Advertisement.3. On the General tab you can customize the following options:

Name: The name of the advertisement as it appears to the user.

Comment: An administrative comment.

Package: The name of the Image Package to deploy.

Program: The Operating System Program to be used in deployment.

Collection: The collection to advertise the package too.

Subcollections: If the package should also be advertised to subcollections.

37

Figure 29 Advertisement Properties - General4. On the Schedule tab you can customize the following options:

Advertisement start time: What time the advertisement should start.

Mandatory Assignments: Can the client defer the installation. For a pilot you may allow clients to defer, but in a major rollout you may prefer to mandatory assign for more control.

Advertisement expiry: When the advertisement is no longer available.

Figure 30 Advertisement Properties - ScheduleThe advertisement is now ready to be collected by SMS clients.

Customizing the Windows Vista ImageA key factor in using WIM imaging technology is to reduce the number of WIM images required to deploy Windows Vista. The WIM image can be installed to any supported hardware platform because there is no longer the Hardware Abstraction Layer (HAL) limitation that Windows XP and earlier had. There are other reasons why images may be

38

changed. The following topics will describe how existing images can be updated rather than creating new images.

Adding Language SupportWindows XP was available in separate versions; Native language versions and Multilingual User Interface (MUI) versions. Because Windows Vista is language-neutral, all that is needed is to add the appropriate language pack to the WIM file to support that language.

To copy a language pack to a Windows Vista distribution, you can follow this procedure:

1. On your local workstation computer, create a folder to contain the Windows Vista distribution, such as C:\Windows_distribution.

2. Copy the entire contents of the Windows Vista DVD to the distribution folder.

3. Remove the Read-only file attribute from the files that will be modified.

4. From the Windows Vista DVD for the language you are installing, browse to the Langpacks folder. For example, if your DVD-ROM drive is D, insert the language-specific Windows Vista DVD and browse to D:\Langpacks.

5. Copy the language pack (Lp.cab) and its parent folder to the Langpacks folder in your distribution. For example:

Mkdir C:\windows_distribution\Langpacks\de-DECopy D:\Langpacks\de-DE\lp.cab C:\windows_distribution\Langpacks\de-DE

6. Copy the license files and Setup resources for the language pack to the distribution folder. For example:

Xcopy D:\Sources\de-DE\* C:\windows_distribution\Langpacks\de-DE /cherkyi7. Use ImageX to mount the Install.wim image from your distribution folder. This step is

required to configure the international settings and create the answer file in later steps. Browse to your ImageX folder in the Windows AIK, typically C:\Program Files\Windows AIK\Tools\x86. Use a command similar to:

Imagex /mountrw c:\windows_distribution\Sources\install.wim 4 c:\wim_mount8. Recreate the lang.ini file to include the settings for the new language. Whenever you

add or remove a language pack to a Windows Vista installation you must run intlcfg.exe to recreate the lang.ini file. For example:

Intlcfg -genlangini -dist:c:\windows_distribution -image:c:\wim_mount -all:de-DE

9. Unmount the Install.wim image to commit the changes. For example:

Imagex /unmount /commit c:\wim_mount

Adding DriversA tool called Package Manager can add Out Of Box driver to offline Windows images.To add drivers to an offline Windows image:

1. Locate the device driver .inf files that you intend to install on your Windows image.

2. Use Windows System Image Manager (Windows SIM) to create an answer file that contains the paths to the device drivers that you intend to install.

3. Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the offlineServicing pass.

39

4. Expand the Microsoft-Windows-PnpCustomizationsNonWinPE node in the answer file. Right-click DevicePaths, and then select Insert New PathAndCredentials.

A new PathAndCredentials list item appears.

5. For each location that you intend to access, add a separate PathAndCredentials list item.

6. In the Microsoft-Windows-PnpCustomizationsNonWinPE component, specify the path to the device driver and the credentials used to access the file if the file is on a network share.

Note: You can include multiple device driver paths by adding multiple PathAndCredentials list items. If you add multiple list items, you must increment the value of Key for each path. For example, you can add two separate driver paths where the value of Key for the first path equals to one and the value of Key for the second path equals to two.

7. Save the answer file and exit Windows SIM. The answer file must be similar to the following sample.

<?xml version="1.0" ?><unattend xmlns="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"> <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"> <DriverPaths> <PathAndCredentials wcm:keyValue="1"> <Path>\\networkshare\share\drivers</Path> <Credentials> <Domain>Fabrikam</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> </DriverPaths> </component> </settings></unattend>

8. Mount the Windows image that you intend to install the drivers to by using ImageX. For example:

imagex /mountrw C:\windows_distribution\sources\install.wim 1 C:\wim_mountThe first Windows image in the Install.wim file is mounted to C:\wim_mount. For more information, see ImageX Command-Line Options.

40

9. Enable logging of specific device driver injection actions in a separate log file. Edit the following registry key on the computer on which you are running Package Manager:

Path: HKLM\Software\Microsoft\Windows\CurrentVersion\Device InstallerKey: DebugPkgMgrType: REG_DWORDValue: 0x01This registry key will create a Drivers.log file during the driver package injection. This log file will log all actions of the driver injection process.

10. Use Package Manager to apply the unattended installation answer file to the mounted Windows image. Specify a location for the log file to create. For example,

pkgmgr /o:"C:\wim_mount\;C:\wim_mount\Windows" /n:"C:\unattend.xml" /l:"C:\pkgmgrlogs\logfile.txt"For more information about using Package Manager, see Package Manager Command-Line Options.

The .inf files referenced in the path in the answer file are added to the Windows image. A log file is created in the directory C:\pkgmgrlogs\. You can open the Drivers.log file and review the Package Manager driver injection actions.

11. Review the contents of the %WINDIR%\inf\ directory in the mounted Windows image to ensure that the .inf files were installed. Drivers added to the Windows image are named oem*.inf. This convention is to ensure unique naming for new drivers added to the computer. For example, the files MyDriver1.inf and MyDriver2.inf are renamed oem0.inf and oem1.inf.

12. Unmount the .wim file and commit the changes. For example,

imagex /unmount /commit C:\wim_mountDrivers may also be added to a shared network folder using Pnputil.exe. When the Vista image is deployed by SMS 2003 R2 to the computer, the computer can scan this network share by match device PnP IDs to the catalog held on this shared folder.

Further information on Pnputil.exe can be found on TechNet and in the BDD documentation and Workbench tool.

FeaturesAs Windows Vista is deployed from a file based image file, and all features are part of this image, features can be turned on and off in the WIM image. Use the following steps to enable or to disable Windows features in an offline image file:

1. Using Windows SIM, create an answer file with the desired Windows features enabled.

2. Mount the image with ImageX.

3. Run Package Manager with the answer file as input.

4. Commit changes and unmount the image.

UpdatesTo install an update to an offline image carry out the following procedure:

1. Expand the update package to a temporary directory.

41

2. Mount the WIM Image by using ImageX.

3. Use the Pkgmgr.exe command to install the package.

Pkgmgr /ip Iw.pathWhere path is the directory containing the expanded update package.

4. Unmount and commit changes to the WIM image.

Service PacksService packs must be installed online on a running Windows installation with the Windows Update Standalone (WUSA) installer. Service packs are provided as .msu files. To Install a Service Pack:

1. Download the service pack to the computer.

2. Open a Command Prompt window.

3. Install the service pack with the following command.

wusa pathWhere path is the full path of the .msu file. You can also use the /quiet and /norestart options.

Adding ApplicationsIt is recommended that applications be installed using SMS 2003 R2 to reduce the size and number of WIM packages to be managed. Applications can easily be installed during the State Restore phase of image restore.

42

IIIManaging the Windows Vista Deployment

It is important to monitor the progress of the Windows Vista deployment to provide information on the following areas:

Whether the deployment project is on track

Which computers have Windows Vista successfully installed for support purposes

Which computers do not have Windows Vista installed

Which computers require upgrades to support Windows Vista

The following section covers how to produce these reports.

Producing ReportsSMS 2003 can produce reports that identify whether software has deployed successfully throughout an SMS site.

To run a report on software deployment status1. Open the SMS Administrator Console, and connect to the site database.

2. Expand Reporting, and click Reports.

3. In the right pane, right-click Status of a specific advertisement, point to All Tasks, point to Run, and click <servername>.

4. If a Connect to dialog box appears requesting credentials, enter the credentials of a user who has permission to run reports.

5. For Advertisement ID, click the Values button, and on the Select Value page click the Advertisement ID for an advertisement of Windows Vista.

6. Under Report Information click Display. A report screen similar to Figure xx appears.

43

Figure 31 SMS Report

Running QueriesSMS 2003 R2 can also use queries to show all computers with common features, such as the same hardware or software. This feature is useful for identifying computers with Windows Vista installed.

To create a query showing all systems with Windows Vista installed

1. Open the SMS Administrator Console, and expand the Site Database.

2. Right-click Queries, point to New, and then click Query.

3. In the Query Properties dialog box (Figure 32), enter a Name for the query for example, All Systems with Windows Vista.

Figure 32 Query Properties4. Click Edit Query Statement.

44

5. In the All Systems with Windows Vista Query Statement Properties dialog box on the Criteria tab, click New.

6. In the Criterion Properties dialog box, as shown in Figure 33, click Select.

Figure 33 Criterion Properties7. In the Select Attribute dialog box, in the Attribute Class list select Operating

System, in the Attribute list select Version, and then click OK.

8. In the Operator list, select is greater than or equal to.

9. Type 6.0 into the Value field, and click OK.

10. Click OK to close the Criterion Properties dialog box, and then click on the General tab, as shown in Figure 34.

Figure 34 Vista Query General11. Click the new button, and in the Result Properties dialog box, click Select.12. In the Select Attribute dialog box, select System Resource in the Attribute Class

list, and select Name in the Attribute list.

13. Click OK to close the Select Attribute dialog box, and then click OK to close the Result Properties dialog box,

45

14. Click New, and then in the Result Properties dialog box click Select.15. In the Select Attribute dialog box, select System Resource in the Attribute Class

list, and select IP Addresses in the Attribute list.

16. Click OK to close the Select Attribute dialog box, and click OK to close the Result Properties dialog box.

17. Click New, and then in the Result Properties dialog box click Select.18. In the Select Attribute dialog box, select System Resource in the Attribute Class

list, and select Operating System Name and Version in the Attribute list.

19. Click OK to close the Select Attribute dialog box, and OK to close the Result Properties dialog box.

20. Click OK to close the Query Statement Properties dialog box.

21. Click OK to close the Query Properties dialog box.

22. Expand Queries, right-click the new query, and select Run Query.

It is important to consider that queries are run against the SMS site database, and the inventory data in the site database is updated only when inventory data is run at the client and collected by SMS site systems. Hence, the frequency of inventory collections will control how up-to-date the query is.

The pilot users of Windows Vista can help identify deployment issues within the organization. Establish a clear procedure for pilot users to provide feedback to the IT department and to the Windows Vista deployment project team. This procedure may use whatever resources the organization has available, for example an IT help desk, a special e-mail alias for the project, or designated users who are involved in the project. A good idea at the start of the project is to create an issue database or log to track all issues as the project moves forward.

The following resources can assist with deployment issues:

The SMS 2003 Technical Resources: Overview Web page

The Business Desktop Deployment Solution Accelerator 2007 Web page

Maintaining Windows Vista by Using SMS 2003 R2Following a successful deployment of Windows Vista, maintenance tasks may be necessary on Windows Vista installations throughout the organization. Maintenance tasks can include:

Changing the WIM image (offline).

Installing Windows Vista updates, such as patches (offline) or service packs (online).

Deploying additional language packs to support a global workforce by using the new multi-language architecture.

SMS 2003 R2 can also be used to carry out these maintenance tasks. Information regarding offline changes and service pack updates was cover earlier in the section titled “Customizing the Windows Vista Image".

SMS 2003 R2 includes the inventory Tool for Microsoft Updates (ITMU) that can be used to install online updates. ITMU scans computers against a catalogue downloaded from Microsoft Update, to identify systems that require updates. The administrator can then deploy updates using the Deploy Software Updates wizard in SMS 2003 R2.

46

SummaryWindows Vista provides a considerable number of improvements over previous versions of Microsoft Windows. In a large network environment, automated processes for deployment and maintenance generate significant cost reductions and minimize administrative workload. These automated processes are also significantly improved in Windows Vista by the use of the compressed, file based WIM format.

SMS 2003 R2 is a powerful systems management tool that can assist deployment of Windows Vista to a large number of computers across a network. Use of Windows AIK with SMS 2003 R2 enables network administrators to carefully control and target deployments to different users and departments with differing requirements This ability is particularly useful with pilot deployments. SMS 2003 R2 can also be used to provide reports and data on the progress of the deployment project, and deploy tools that can assist in a smooth transition to the new applications.

47