Term
| Migration and Deployment challenges? |
|
Definition
-Application incompatibilities
-Complicated user state migrations
-Lack of migration resources
-Lack of best practices and implementation guides
-Deficient end-user training and support |
|
|
Term
|
Definition
-Client lifecycle
-Hardware lifecycle
-Desktop Deployment lifecycle |
|
|
Term
|
Definition
-Procurement
-Deployment
-Management
|
|
|
Term
| Client lifecycle: Procurement |
|
Definition
| Procurement is the complete action or process of acquiring or obtaining personnel, material, services, or property from a vendor by means authorized in relevant, specific directives. It is the action or process of acquiring or obtaining items at the operational level, for example, purchasing, contracting, and negotiating directly with the source of supply for the purchase of computers. |
|
|
Term
|
Definition
-In-place upgrade
-Wipe-and-load |
|
|
Term
| In-Place Deployment: In-place upgrade |
|
Definition
| upgrade existing computers to Windows 7, maintaining their configurations |
|
|
Term
| In-Place Deployment: Wipe-and-load |
|
Definition
| replace the computer’s current configurations and selectively migrating parts of the previous configurations |
|
|
Term
|
Definition
Back up computer’s entire hard disk: use the backup program built in to whichever version of Windows that you are upgrading, a third-party backup program, or disk-imaging software that saves an image of the computer’s hard disk, to back up the user’s hard disk.
Perform upgrade to Windows 7: run setup.exe, the Windows 7 installation program, and select Upgrade. You can run setup.exe from the product DVD or from a network share.
Upgrade, uninstall, and install additional applications as required: many applications work correctly after you install Windows 7 using an in-place upgrade scenario. However, if some do not, you can upgrade or reinstall them. |
|
|
Term
|
Definition
Back up the computer’s entire hard disk: similar to an in-place upgrade, you can use the built-in Windows backup, a third-party backup program, or disk-imaging software.
Save user settings and data for migration: in one-off scenarios, you can use the Windows® Easy Transfer introduced in Windows 7 to save your user settings. In large-scale deployments, you can use the User State Migration Tool (USMT), customizing it to save exactly the settings that you want to migrate.
Perform a clean installation of Windows 7: run setup.exe, the Windows 7 installation program, and select Custom. The Custom option allows you to install Windows 7 on a partition that already has an operating system, such as earlier versions of Windows.
After the installation is done, the earlier version of Windows will be placed in a folder called Windows.old, along with the previous Program Files and Documents and Settings folders.
Run setup.exe from the product DVD or from a network share. Alternatively, you can choose to format the partition using a disk management tool, such as Diskpart.exe, before performing a clean installation.
Re-install applications: before restoring your user settings and files, re-install all applications so that migration will also restore application settings.
Restore user settings and data from Step 2: you can use the same tool to restore user settings and data as was used to save them in Step 2. In addition, you can automate the migration process so that users do not have to interact with it.
|
|
|
Term
| In-place Upgrade Advantages |
|
Definition
Retains user settings, application settings, and files with no additional effort.
Preserves installed applications and typically does not require re-installation of applications.
Does not require additional storage space for migration files.
Has minimal impact to user productivity. User settings and data are preserved just as in the source computer.
|
|
|
Term
|
Definition
Offers the opportunity to clean up existing work stations and to create more stable and secure desktop environments. It takes advantage of the opportunity for a fresh start, a significant advantage when creating a managed environment.
Avoids the application migration issues associated with the in-place upgrade scenario, where preserved applications may not work correctly with Windows 7.
Avoids the performance degradation issues associated with the in-place upgrade scenario, because there are no remnant files and settings.
Allows for installation of any edition without concern about what edition was previously on the workstations.
Provides the opportunity to reconfigure hardware-level settings, such as disk partitioning before installation.
Exploits, such as virus, spyware, and other malicious software do not migrate to new installation of Windows, and security settings can be hardened by using Group Policy and Security Templates. |
|
|
Term
| Wipe-and-load Disadvantages |
|
Definition
Requires the use of migration tools, such as Windows Easy Transfer or User State Migration Tool, to save and restore user settings and data.
Requires re-installation of applications.
Requires storage space for user settings and files to be migrated.
May have an impact on user productivity because of the reconfiguration of applications and settings.
|
|
|
Term
| In-place Upgrade Disadvantages |
|
Definition
Does not take advantage of the opportunity to start fresh with standardized reference configurations.
Preserved applications may not work correctly after upgrading from an earlier version of Windows.
Remnant files or settings from in-place upgrade may contribute to performance and/or security issues.
Does not allow for edition changes. For example, you cannot upgrade Windows Vista® Enterprise to Windows 7 Ultimate.
Can only be done on supported operating systems, which is Windows Vista with SP1 or later. |
|
|
Term
| In-place upgrade considerations |
|
Definition
Infrastructure: in-place upgrade requires no additional computer hardware or storage space. You can use the following tools to upgrade your computer from an earlier versions of the Windows operating system to Windows 7:
Windows Setup (setup.exe): this is the program that installs the Windows operating system or upgrades earlier versions of the Windows operating system. You can run Windows setup from the product CD/DVD or from a network share.
Windows images using network share: you can create images of a reference computer and deploy them to destination computers. You can deploy these Windows images by using ImageX tool, included in Windows Automated Installation Kit (Windows AIK).
Windows Deployment Services (WDS): this is a server-based deployment solution that enables an administrator to set up new client computers over the network. You can deploy Windows images through the network without visiting each client.
A WDS server must be at least a member of an Active Directory domain. You must also have a working DHCP and DNS server on the network. In addition, you cannot configure WDS server role on a server core installation.
Consider using Windows Automated Installation Kit (Windows AIK). This is a collection of tools and documentation designed to help IT professionals deploy Windows. The tools in Windows AIK include:
Windows System Image Manager (Windows SIM): the tool used to open Windows images, create answer files, and manage distribution shares and configuration sets.
ImageX: the tool used to capture, create, modify, and apply Windows images.
Deployment Image Servicing and Management (DISM): the tool used to apply updates, drivers, and language packs to a Windows image. DISM is available in all installations of Windows 7 and Windows Server 2008 R2.
User State Migration Tool (USMT): the tool used to migrate user data from a previous Windows operating system to Windows 7.
Depending on how you deploy Windows 7, you may require file servers and a local area network.
Budget: in-place upgrade requires no investment in additional hardware. Most organizations already have file servers and a local area network. Therefore, no additional investment is required other than the effort to prepare and set the tools and technologies. If you are using the product CD/DVD to perform the upgrade, you do not even need file servers and network connection.
The phase of the desktop: in-place upgrade requires no new hardware. Therefore, it is not important to consider the organization’s hardware life-cycle.
Valid upgrade options for Windows 7: only Windows Vista® with Service Pack 1 or later supports in-place upgrades to Windows 7. Windows versions earlier than Windows Vista with Service Pack 1 do not support in-place upgrade to Windows 7. In-place upgrade also does not support the following:
Cross architecture: this means that you cannot upgrade from a 32-bit platform to a 64-bit platform or vice versa. You can only upgrade to the same platform, even if your hardware supports both architectures.
Cross language: this means that you cannot upgrade, for example, a U.S. English (EN-US) version of Windows to a German (DE-DE) version of Windows.
Edition changes: this means that you cannot upgrade Windows Vista Enterprise to Windows 7 Ultimate.
Amount of interaction: in-place upgrade has no significant impact on user productivity. You can use the answer file to minimize the user interaction and effort when performing an in-place deployment.
Answer File: you can use the answer file to help configure Windows settings during installation. You can configure the default Internet Explorer® settings, networking configurations, and other customizations. The answer file contains all the settings required for an unattended installation. You will not be prompted with the user interface pages during the installation.
State of user data: in-place upgrade deployment does not require reinstallation of applications, or any of the user settings, data, hardware device settings, applications, or other configuration information. However, some applications may not work correctly and may have to be reinstalled after the upgrade is performed.
|
|
|
Term
Wipe-and-load considerations
|
|
Definition
Infrastructure: wipe-and-load deployment requires no additional computer hardware, because the scenario refreshes your existing operating system. However, wipe-and-load requires you to save the existing user state data on the computer. Therefore, you must have additional space to store the user state. You can use any appropriate media to store the user data. You can use the same set of tools as for an in-place upgrade.
Budget: wipe-and-load deployment requires no additional costs for hardware or software. In fact, wipe-and-load can reduce deployment, management, and support costs. In addition, because the wipe-and-load deployment scenario is less complex than the in-place upgrade deployment, the overall cost can also be reduced.
The phase of the desktop: wipe-and-load deployment requires no new hardware. Therefore, it is not important to take the organizations hardware life cycle into consideration.
Amount of interaction: the wipe-and-load refresh scenario does not require much user interaction. However, when compared to the in-place upgrade scenario, it may have more impact on user productivity. This is because users may have to reconfigure their own settings and reinstall the particular applications manually, after the wipe-and-load deployment is performed. The following tools can be used to help migrate user settings and data:
Windows Easy Transfer (WET): supports user settings and data transfer to the destination computer by using the network, WET cable, removable media, or a writable CD or DVD. You can use WET to transfer the following files and settings:
Files and folders
E-mail settings
Contacts and messages
Program settings
User accounts and settings
Internet settings and favorites
Music
Pictures and videos
Note: Windows Easy Transfer does not transfer any system files such as fonts and drivers. To do this, install custom fonts and updated drivers in Windows 7.
User State Migration Tool (USMT): supports user settings and data transfer for large deployments. You can automate most of migration tasks by using USMT to minimize user interaction in deployment.
State of user data: wipe-and-load deployment requires a reinstallation of applications. While user data is preserved in the new Windows installation, you must migrate the user settings by using migration tool.
Use the User State Migration Tool (USMT) to create a snapshot of current user data files before reinstallation. This will keep data in the same location on the disk while you are upgrading the system and rebuild the links after Windows 7 is installed. This is known as hard-link migration. Hard-link migration reduces the time required to migrate a user state, because the user settings data is never moved, which is faster than copying the user settings and data to another disk. Hard-link migration also eliminates the need for storage space to store migration data.
In the wipe-and-load deployment, you can also use the Windows.old folder. The Windows.old folder helps to recover all personal files when you perform a custom installation of Windows 7. The Windows.old folder is automatically generated when you perform a custom installation of Windows 7.
The Windows.old folder contains the following folders:
Windows: this contains programs and files required to run the earlier version of Windows.
Documents and Settings: this contains the My Documents folder, the Favorites folder and folders stored on the desktop.
Program Files: this contains the programs that were installed on the earlier version of Windows. To use these programs in Windows 7, you must reinstall them. Before doing this, verify that the programs are compatible with Windows 7.
When you have moved all important data from the Windows.old folder, remove the folder by using Windows Disk Cleanup. In the Disk Cleanup Options dialog box, select Files from all users on the computer and then click Clean up system files. This will remove the Windows.old folder.
The wipe-and-load deployment scenario refreshes the computers and standardizes the configurations in your organization. If you choose this scenario to re-image the computers in your organization so that there is a standard configuration across the organization, or to address any other problems, this scenario may reduce the number of Help desk calls, troubleshooting and debugging time, and minimize other support problems that can result from nonstandard configurations.
|
|
|
Term
| Considerations of Side-by-Side Deployment |
|
Definition
Infrastructure: side-by-side deployment requires an existing computer, intermediate storage space, and a destination computer. Use the following tools to install Windows 7:
Windows Setup (setup.exe): this is the program that installs the Windows operating system or upgrades earlier versions of the Windows operating system. You can run Windows setup from the product CD/DVD or from a network share.
Windows images using network share: you can create images of a reference computer and deploy them to destination computers. You can deploy these Windows images by using ImageX tool, included in Windows Automated Installation Kit (Windows AIK).
Windows Deployment Services (WDS): this is a server-based deployment solution that enables an administrator to set up new client computers over the network. You can deploy Windows images through the network without having to visit each client. You need to have an Active Directory, DHCP, and DNS on the network to use WDS.
Also consider using Windows AIK to assist in deploying Windows operating system. To migrate user settings and data, you can use the following tools:
Windows Easy Transfer (WET) for small volume deployment.
User State Migration Tool (USMT) for large volume deployment.
Budget: this deployment scenario requires a new destination computer. This can generate additional costs in replacing the existing computer hardware.
The phase of the desktop: this deployment scenario is typically used when replacing computers in the organization. In this case, the hardware life cycle is an important factor because new computers are required.
Amount of interaction: this deployment method enables the user to continue working, while new computers are installed and configured. You can automate the deployment and minimize the user interaction by using the following tools:
Answer file: to assist configuring Windows settings during Windows installation.
User State Migration Tool (USMT): to perform the migration for many computers.
State of user data: this deployment method requires a reinstallation of applications on the destination computer. Before performing the side-by-side deployment scenario, identify which elements to migrate to the new computer. These may include:
User accounts: computer workstations may have settings related to both domain and local user accounts. You must determine whether local user accounts must be migrated. Your consideration must also include whether the account must be enabled on the destination computer and how you will deal with password requirements.
Application settings: you must determine and locate the application settings that you want to migrate. This information can be obtained when you are testing the new applications for compatibility with the new operating system.
Considerations include whether the destination version of the application is newer than the source version and where the specific application settings are stored.
Settings may be stored in the registry, .ini files, or a text or binary file. To determine the location of a setting, begin by reviewing the vendor’s documentation or Web site. Migration does not include migrating the actual application itself.
Operating system settings: when planning for your migration, you need to identify which operating system settings to migrate and to what extent you want to create a new standard environment on each of the computers.
Operating system settings may include appearance, mouse actions (for example, single-click or double-click) and keyboard settings, Internet settings, e-mail account settings, dial-up connections, accessibility settings, and fonts.
File types, files, folders, and settings: when planning your migration, identify the file types, files, folders, and settings to migrate. For example, you need to determine and locate the standard file locations on each computer, such as the My Documents folder and company-specified locations. You must also determine and locate the nonstandard file locations. For nonstandard locations, consider the following:
File types: consider which file types must be included and excluded in the migration.
Excluded locations: consider the locations on the computer that must be excluded from the migration (for example, %windir% and the Program Files folder).
New locations: decide where you want to migrate files on the destination computer (for example, the Documents folder, a designated folder, or the original location).
|
|
|
Term
| Determining a Deployment Scenario |
|
Definition
-Wipe-and-load
-In-place Upgrade
-Side-by-Side |
|
|
Term
|
Definition
WIM Header: defines the .wim file content, such as memory location of key resources (metadata resource, lookup table, and XML data) and .wim file attributes (version, size, and compression type).
File Resource: a series of packages that contain captured data, such as source files.
Metadata Resource: stores information on how captured data is organized in the .wim file, including directory structure and file attributes. There is one metadata resource for each image in a .wim file.
Lookup Table: contains the memory location of resource files in the .wim file.
XML Data: contains additional miscellaneous data about the WIM image, such as directory and file counts, total bytes, creation and modification times, and description information. The ImageX /info command displays information based on this resource.
Integrity Table: contains security hash information used to verify the integrity of the image during an apply operation. This is created when you set the /check switch during an ImageX capture operation. |
|
|
Term
| benefits of WIM file format |
|
Definition
A single WIM file can address many hardware configurations. WIM does not require that the destination hardware match the source hardware. This helps you to reduce the number of images tremendously, and you have the advantage of only having one image to address the many hardware configurations.
WIM can store multiple images in a single file. This is useful because you can store images with and without core applications in a single image file. Another benefit is that you can mark one of the images as bootable, which allows you to start a machine from a disk image contained in a WIM file.
WIM enables compression and single instancing. This reduces the size of image files significantly. Single instancing is a technique that enables multiple images to share a single copy of files that are common between the instances.
WIM enables you to service an image offline. You can add or remove certain operating system elements, files, updates, and drivers without creating a new image. For example, to add an update to a Windows XP® image, you must start the master image, add the update, and then prepare the image again. With Windows 7, you can mount the image file and then slipstream the update into the image file without the need to start or recapture the master image.
WIM enables you to install an image on a partition that is smaller, equal to, or larger than the original partition that was captured, as long as the target partition has sufficient space to store the image content. This is unlike sector-based image formats that require you to deploy a disk image to a partition that is the same size or larger than the source disk.
Windows 7 provides an API for the WIM image format called WIMGAPI that developers can use to work with WIM image files.
WIM allows for nondestructive image deployment. Nondestructive image deployment means that you can leave data on the volume where you apply the image, because, when the image is applied, it does not delete the disk’s existing contents.
WIM enables you to start Windows PE from a WIM file. The Windows 7 setup process uses Windows PE. The WIM file is loaded into a random access memory (RAM) disk and run directly from memory.
|
|
|
Term
| Windows 7 Modularization benefits |
|
Definition
You can add device drivers and updates to the image file used to deploy Windows 7. You can add these drivers and updates offline without actually deploying the image on a computer.
You can customize some optional Windows 7 elements to your specific requirements.
When Microsoft releases an update for one of the features, you can update just that feature in the installation image without re-creating the entire image.
You can deploy multiple Windows 7 language versions with a single image file. The core operating system features for Windows 7 are not based on any particular language. Languages, including English, are optional features and can be added separately from the operating system.
|
|
|
Term
| five high-level phases in the Microsoft deployment process |
|
Definition
Envisioning
Planning
Developing
Stabilizing
Deploying
|
|
|
Term
|
Definition
| thick image, thin image, or hybrid image |
|
|
Term
| image strategy key elements |
|
Definition
Type of images
Number of images
Number of WIM files
Preconfigured settings in an image
Additional operating system elements |
|
|
Term
| The process to deploy Windows 7 by using WDS involves the following |
|
Definition
Plan and design the WDS environment
Install WDS
Configure WDS
Add boot and install images
Configure the boot menu
Prestage clients for deployments
Deploy the operating system on clients by using WDS
|
|
|
Term
The process of deploying Windows 7 by using ZTI with MDT 2010 consists of several high-level steps:
|
|
Definition
Design the ZTI environment
Implement the ZTI infrastructure
Install Configuration Manager 2007
Install MDT 2010
Integrate Configuration Manager and MDT 2010
Configure the PXE service
Create and distribute images and packages
Configure and advertise a Task Sequence
Create collections as needed
|
|
|
Term
| Effective client configuration planning provides benefits? |
|
Definition
Reduced administrative efforts
Reduced total cost of ownership (TCO)
Minimized security risks
Minimized training requirements
Consistent user experience
|
|
|
