Preparing to Deploy Windows Vista Lesson 1. Skills Matrix Technology SkillObjective Domain SkillDomain # Choosing a Deployment Method Analyze the business

Preparing to Deploy Preparing to Deploy Windows VistaWindows Vista

Lesson 1

Skills MatrixSkills Matrix

Technology Skill Objective Domain Skill Domain #Choosing a Deployment Method

Analyze the business environment and select an appropriate deployment method: network, offline media, USB, DVD

1.1

Preparing for Deployment Prepare a system for clean installation or upgrade

1.2

Understanding System Requirements

Verify Windows Vista installation requirements

1.2

Understanding ScanState Perform user state backup with USMT

1.2


Technology Skill Objective Domain Skill Domain #Analyzing User Profile and Data Storage Requirements

• Analyze use profile and data requirements• Roaming user profiles/folder redirection

1.2

Migrating User Profiles by Using USMT

Perform user state backup with USMTPerform post-installation tasks• Restore user state with USMT

1.2

1.4


Technology Skill Objective Domain Skill Domain #Understanding USMT Perform user state backup

with USMTRestore user state with USMT

1.2

1.4

Understanding What USMT Migrates

Perform user state backup with USMTRestore user state with USMT

1.2

1.4

Using USMT Perform user state backup with USMTRestore user state with USMT

1.2

1.4


Technology Skill Objective Domain Skill Domain #Understanding the .xml Control Files


1.2

1.4

Understanding Manifests Perform user state backup with USMTRestore user state with USMT

1.2

1.4


Technology Skill Objective Domain Skill Domain #Completing a Simple Profile Migration by Using USMT


1.2

1.4

Understanding LoadState Restore user state with USMT

1.4

Analyzing Application and Device Compatibility

Troubleshoot deployment issues• Resolve application compatibility issues• Resolve device driver issues

1.5

Over the network using a Windows Imaging Format (WIM) image

Offline media, such as DVD or USB storage device

Choosing a Deployment Method

Choosing a Deployment MethodChoosing a Deployment Method

Minimum system requirements to run the core features of Windows Vista

800MHz 32-bit (x86) or 64-bit (x64) processor

512MB system memory

SVGA (800x600) graphics processing unit (GPU)

20GB hard disk drive (HDD) with 15GB free space

CD-ROM optical drive

Understanding System Requirements

Preparing for DeploymentPreparing for Deployment

Windows Vista Capable PC

Modern processor (at least 800MHz)

512MB system memory

DirectX 9 capable GPU

Understanding System Requirements (cont.)


Windows Vista Premium Ready PC

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

1GB system memory

GPU that supports DirectX 9 graphics with a Microsoft Windows Vista Display Driver Model (WDDM) driver, 128MB of graphics memory (minimum), Pixel Shader 2.0, and 32 bits per pixel.



Windows Vista Premium Ready PC (cont.)

40GB HDD with 15GB free space

DVD-ROM drive

Audio output capability

Internet access capability



Windows Vista Hardware Assessment tool

Application Compatibility Toolkit 5.0 (ACT)

Windows Vista Upgrade Advisor (for stand-alone computers)

Used to analyze both hardware and application compatibility issues

Analyzing Application and Device Compatibility


Following its analysis, the Windows Vista Hardware Assessment tool creates the following reports:

An Excel workbook comprehensively covering the device inventory and assessment

A Word document summarizing the device inventory and assessment

Getting Started with the Windows Vista Hardware Assessment Tool


ACT uses the following distributed compatibility evaluators:

Inventory Collector — Identifies installed applications and gathers system information

User Account Control Compatibility Evaluator (UACCE) — Identifies potential compatibility issues due to permissions restrictions enforced by User Account Control (UAC)

Getting Started: Application Compatibility Toolkit


Update Compatibility Evaluator (UCE) — Gathers information on application dependencies and can identify potential effects of Windows operating system security updates on applications

Internet Explorer Compatibility Evaluator (IECE) — Identifies potential Web application and website issues that occur due to the release of a new operating system

Getting Started: Application Compatibility Toolkit (cont.)


Windows Vista Compatibility Evaluator — Identifies other issues related to compatibility with Windows Vista

Getting Started: Application Compatibility Toolkit (cont.)


Windows Vista Upgrade Advisor only runs on Windows XP.

Using the Windows Vista Upgrade Advisor


Using the Windows Vista Upgrade Advisor (cont.)


System Requirements

Devices

Programs

Configuring Roaming Profiles


Click the Profile tab.

In the User profile section, key the path where the user’s profile resides.

Click OK.

Windows Vista allows up to thirteen folders to be redirected (five in Windows XP).

Folder Redirection configured for Windows XP will work when a user logs on to Windows Vista.

Understanding Folder Redirection


Configuring Folder Redirection


Group or UserName

NTFSPermission Apply onto:

CREATOR OWNER Full Control Subfolders and Files Only

SYSTEM Full Control This Folder, Subfolder, and Files

Domain Admins Full Control This Folder, Subfolder and Files

Everyone

Create Folders/Append Data

List Folder/Read Data

Read Attributes

Traverse Folder/Execute File

This Folder Only


Redirecting a Folder to Separate Target Folders

Expand User Configuration > Windows Settings > Folder Redirection.

Select Properties.


Redirecting a Folder to Separate Target Folders (cont.)

Select Basic - Redirect everyone’s folder to the same location.

Select Create a folder for each user under the root path.

Enter the path: \\server01\ RedirectStore1.


Redirecting a Folder to Separate Target Folders (cont.)

Grant the user exclusive rights to RedirectedFolderName.

Move the contents of RedirectedFolderName to the new location.

Leave the folder in the new location when policy is removed.


Redirecting a Folder to the Same Target Folder for All Users

Expand User Configuration > Windows.

Right-click Settings > Folder Redirection, and select Properties.



Redirecting a Folder to the Same Target Folder for All Users (cont.)

Select Redirect to the following location.

Enter the path: \\ServerName\ ShareName\ TargetFolderName.



Select Move the contents of RedirectedFolderName to the new location.

Select Also apply redirection to Windows 2000, Windows 2000 Server, Windows XP, and Windows Server 2003 operating systems.



Select Redirect the folder back to the local userprofile location when policy is removed.


Redirecting a Folder to the Local ‘userprofile’ Location

Expand User Configuration > Windows Settings.

Right-click Folder Redirection, and select Properties.


Redirecting a Folder to the Local ‘userprofile’ Location (cont.)


Select Redirect to the local userprofile location.


Redirecting a Folder According to Group Membership



Select Advanced - Specify locations for various user groups.


Redirecting a Folder According to Group Membership (cont.)

In the Security Group Membership section, click Add. The Specify Group and Location dialog box appears.



Select Grant the user exclusive rights to RedirectedFolderName.

Select Move the contents of RedirectedFolderName to the new location.



Select Also apply redirection to Windows 2000, Windows 2000 Server, Windows XP, and Windows Server 2003 operating systems.

Select Redirect the folder back to the local userprofile location when policy is removed.


Configuring Media Folders to Follow the Documents Folder



Select Follow the Documents Folder.

Migrating User Profiles by Using USMTMigrating User Profiles by Using USMT


USMT is composed of five major components ScanState

LoadState

.xml control files

Component Manifests

Downlevel Manifests



The following are migrated using the default control files:

User data

Operating system settings

Supported application data and settings


Using USMT

Using USMT in an enterprise environment to migrate data and settings can be divided into three broad stages:

Planning the migration

Collecting files and settings from the source workstation

Migrating files and settings to the destination workstation


Stage 1: Planning the Migration

Choose what to migrate within the following categories:

Users

Application settings

Operating system settings

Files and folders

Registry keys


Stage 1: Planning the Migration (cont.)

Determine where to store the migration data

On the source workstation

On a network share

On the destination workstation



Modify the migration .xml files, and create Custom .xml files if necessary.

To configure user data migration, modify the MigUser.xml file.

To configure application data migration, modify the MigApp.xml file.



Modify the migration .xml files, and create Custom .xml files if necessary.

To exclude anything from the migration, create a custom Config.xml file.

To customize the migration for your organization’s unique needs, create a Custom .xml file.


Stage 2: Collecting Profile Data and Settings

Back up the source workstation.

Close all applications. If any applications are running, they might prevent USMT from being able to capture files.

Run ScanState on the source workstation to collect the profile data and settings as specified in the .xml control files.


Stage 3: Restoring Profile Data and Settings

Deploy the operating system to the destination workstation.

Install all applications that were on the source workstation that will be on the destination workstation.


Stage 3: Restoring Profile Data and Settings (cont.)

Close all applications. If any applications are running, LoadState might not be able to restore all data and settings.

Run LoadState on the destination workstation to restore the files and settings as specified in the .xml control files.

Log off after running LoadState so that settings are fully refreshed during the next logon.


Understanding ScanState and LoadState

ScanState and LoadState can use the following .xml control files:

MigSys.xml

MigApp.xml

MigUser.xml

Config.xml

Custom .xml


Understanding .xml Control Files

MigSys.xml — Controls which operating system and browser settings to migrate when the source workstation is running Windows XP

MigApp.xml — Controls which application settings are migrated from the source workstation


Understanding .xml Control Files (cont.)

MigUser.xml — Controls which profile folders, files, and file types to migrate from the source workstation

Config.xml — Contains all settings defined by Component Manifests or Downlevel Manifests. You create this file by using the ScanState /genconfig option.


Understanding .xml Control Files (cont.)

Custom .xml — Defines custom migration rules

Can be used for such tasks as migrating the settings for a custom business application. You can define multiple custom control files. To call custom control files, you modify CustomSettings.ini.


Collecting Profile Data and Settings Using ScanState

scanstate \\ServerName\path /i:miguser.xml /i:migapp.xml /o


Restoring Profile Data and Settings Using LoadState

loadstate \\ServerName\path /i:miguser.xml /i:migapp.xml /lac /lae

SummarySummary

You learned how to choose a deployment method as well as how to judge system requirements based on Windows Vista Capable PC minimum requirements and Windows Vista Premium Ready PC minimum requirements.

The Windows Vista Hardware Assessment tool analyzes and reports on device compatibility across an enterprise.

You Learned

SummarySummary

The Application Compatibility Toolkit 5.0 analyzes and reports on application compatibility across an enterprise.

You can use the Windows Vista Upgrade Advisor on stand-alone computers to analyze both hardware and application compatibility issues before upgrading to Windows Vista.

You Learned (cont.)

SummarySummary

Before deploying Windows Vista, you need to plan and prepare for user profile and data storage requirements.

Roaming profiles are configured in the Active Directory Users and Computers Properties dialog box for the user.

You Learned (cont.)

SummarySummary

Folder Redirection enables you to redirect the saving and loading of data from a profile folder to another folder (almost always a network share).

You learned how to redirect folders as well as how to configure the Pictures, Music, or Video folder to follow the Documents folder for Folder Redirection.

You Learned (cont.)

SummarySummary

USMT 3.0 is a tool for migrating profile settings and data that consists of two command-line executables (ScanState and LoadState) as well as other components.

Roaming profiles are configured in the Active Directory Users and Computers Properties dialog box for the user.

You Learned (cont.)

SummarySummary

The .xml control files determine what USMT migrates.

You learned how to collect and restore profile data and settings using ScanState and LoadState.

You Learned (cont.)