P2V Solution Accelerator Prerequisites Beta 2

For Lite Touch Installation (LTI) deployments using MDT 2010 Update 1, P2V Migration for Software Assurance requires the following components:

· A functional installation of MDT 2010 Update 1 with mapped deployment shares on the client computer targeted for P2V Migration installation. The installation process for P2V Migration automatically copies required components to the MDT 2010 installation folder and deployment shares mapped in the MDT 2010 Deployment Workbench.

· An Internet connection or downloadable components listed in the previous section, available in C:\Program Files (x86)\P2V Migration for Software Assurance\Tools. If no Internet connection is available, you will need to copy these files manually.

· Sysinternals Disk2vhd 1.62 or later. The P2V Migration for Software Assurance installer will download Disk2vhd as part of the installation process. Pre-1.62 versions of Disk2vhd are not supported.

For Zero Touch Installation deployments using Microsoft System Center Configuration Manager 2007, P2V Migration requires the following components:

· A configured System Center Configuration Manager Operating System Deployment environment, with MDT 2010 Update 1 add-in components installed.

· An Internet connection or downloadable components listed in the previous section, available in C:\Program Files (x86)\P2V Migration for Software Assurance\Tools.

The client computers targeted for VHD conversion must meet the following requirements:

· 32-bit Windows 7 Professional or Windows 7 Enterprise, Windows Vista Business or Windows Vista Enterprise with SP1 or SP2, or Windows XP Professional with SP3 must be installed.

· Client computers were installed and activated using Microsoft Volume Licensing or full packaged product installation media. Installations using OEM installation media are not valid. Full packaged product installation media provide the right to transfer the installation to another computer but will require reactivation once the system has been converted to a VHD.

· Windows is installed to a single partition without using a separate system or boot partition. Note that this limitation should be resolved in a subsequent beta or the final release of P2V Migration for Software Assurance.

· Hard disks must be 127 gigabytes (GB) or smaller in size, regardless of the amount of data stored on them. This is a limitation of Windows Virtual PC. For example, if the computer has a 160-GB hard disk consuming only 20 GB of data (even if it is configured with partitions smaller than 127 GB), P2V Migration will not work in either configuration.

· The P2V and deployment processes will target Disk 0 partitions only (Windows and system partitions). Attached disks other than Disk 0—including USB storage and external hard disks—will not be converted to a VHD in the process.

· For multinational clients targeted for P2V Migration and starting with Windows XP with SP3, KB961742-v3.exe should be installed in advance, with the language-appropriate version matching the operating system language. By default, P2V Migration installs the English-language version of KB961742-v3.exe on Windows XP with SP3 systems prior to VHD conversion.

The client computers on which the new operating system will be installed must meet the following requirements:

· 32-bit or 64-bit Windows 7 Professional or Windows 7 Enterprise

· Software Assurance covers the device in order to provide rights for up to four VM installations per device

· Hardware meets the minimum requirements of Windows 7 with Windows Virtual PC (2 GB of RAM recommended)

Note   Hardware-assisted virtualization is not required with this solution.