Home
> Virtualization > P2V Migration for Software Assurance : Beta released
P2V Migration for Software Assurance : Beta released
Microsoft launched the public beta of a new physical to virtual (P2V) migration tool for client operating systmes:P2V Migration for Software Assurance.
P2V Migration for Software Assurance uses automation from the Microsoft Deployment Toolkit (MDT) 2010 and P2V disk conversion from Sysinternals Disk2vhd. The Windows Installer Package for P2V Migration contains a collection of scripts and MDT 2010 task sequence templates that convert an existing operating system installation to a VHD file during a Windows 7 deployment. Then, the process creates a VM using the VHD file and publishes the applications it contains to the Windows 7 Start menu.
P2V Migration supports creating VHD files based on Windows 7, Windows Vista, and Windows XP with Service Pack 3 (SP3) operating systems. Although you can use P2V Migration when deploying the x86 or x64 versions of Windows 7, it can only create VHD files based on x86 versions of the operating system. P2V Migration is language agnostic.
For Lite Touch Installation 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 for Software Assurance installation.
· An Internet connection or downloadable components listed in the previous section, available in C:Program Files (x86)P2V Migration for Software AssuranceTools.
For Zero Touch Installation deployments using Microsoft System Center Configuration Manager 2007, P2V Migration for Software Assurance 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 AssuranceTools.
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 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.
· 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 or is configured with multiple partitions and a Windows volume smaller than 127 GB, P2V Migration will not work in either configuration.
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
Categories: Virtualization
Comments (0)
Trackbacks (0)
Leave a comment
Trackback
Recommended Books
System Center 2012 R2 Virtual Machine
System Center Virtual Machine Manager 2012 Cookbook
Cloudtidings.com 