Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.
X
Aside

Announcing the Release Candidate of Configuration Manager Physical to Virtual Migration Toolkit | Microsoft Connect

Announcing the Release Candidate of Configuration Manager Physical to Virtual Migration Toolkit | Microsoft Connect

The Configuration Manager team is pleased to announce the Release Candidate (RC) of the Configuration Manager Physical-to-Virtual Migration Toolkit!

The Configuration Manager P2V Migration Toolkit was designed to assist in situations where there are remote Configuration Manager 2007 site servers that need to be retained during the side-by-side migration process to Configuration Manager 2012.

The Configuration Manager P2V Migration Toolkit facilitates the re-utilization of existing x64 server hardware using virtualization technologies, Windows Server 2008 R2 and Hyper-V

Configuration Manager P2V Migration Toolkit key features:

· Task sequence\standalone media driven. Utilizes Configuration Manager 2007’s task sequences to provide the ability to automate the majority of the end-to-end P2V process, including:

o Offline virtualization of physical disks.

o Preparing the VHDs to leverage virtual storage drivers and align to virtual disk layout.

o Compressing of the VHD’s to reduce size on disk.

o Installation of Windows 2008 R2 (including enabling the Hyper-V role).

o Automating the creation of a Hyper-V virtual machine.

o Attaching the captured VHDs as a Hyper-V virtual machine.

· User interface to create customized task sequences and standalone media. Wizard driven user interface assists in the creation of a customized Configuration Manager 2007 task sequence and standalone media specifically targeted to the P2V conversion of the remote site server.

· Offline physical-to-virtual conversion. Offline P2V conversion is the most reliable way to ensure data consistency between the physical hard disks and the virtual copies.

· Capture only option. Wizard driven solution to assist in the creation of bootable media, which in turn can be used to capture selected physical disk drives into Virtual Hard Disks (VHDs).

Release Candidate Improvements:

· Accessibility. Added support for high contrast, keyboard shortcuts and keyboard navigation.

· Increased critical boot driver coverage. Added additional support for critical boot drivers to enhance IDE disk driver support in the virtual instance.

Aside

P2V Solution Accelerator Known Issues Beta 2

The known issues in P2V Migration for Software Assurance beta are categorized as follows:

· On Windows XP operating systems, Disk2vhd.exe is hidden during the Capture VHD phase, but it is minimized to the task bar in Windows Vista. Clicking Help/Cancel in the Disk2vhd.exe tool while the Capture VHD task is running is not supported.

· If a non-administrative user has to run the Add Old Apps to Windows 7.hta script to add old operating system applications to the Windows 7 Start menu, that user would need Administrator credentials.

· In all System Center Configuration Manager scenarios and LTI Domain Join scenarios, the Add Old Apps to Windows 7.hta script does not run automatically: You must run it manually.

Aside

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.

Aside

P2V Migration Beta 2 Is Now on Microsoft Connect: ConfigMgr Support Now Documented

Microsoft Connect: P2V Migration Beta 2

The Microsoft Deployment Toolkit team is working on a new solution incorporating Sysinternals Disk2VHD into the desktop migration process. Participation in the Beta Program for P2V Migration for Software Assurance is happening now, and we’d like your help!

If you are not already a member of the MDT beta program, click here to join.

Aside

Installing the P2V Solution Accelerator

First, be sure to read the Prerequisites in the Release Notes provided with the installation files.  Also, please make sure to read the Known Issues list in the Release Notes as well.

Also I highly recommend you watch the video below by Jeremy Chapman, this is a quick overview and video walkthrough on the product and a demo of it in action.

P2V Migration with Jeremy Chapman

Installing the P2V Solution Accelerator

Open up the P2VMigration.msi.

image

Accept the license agreement and click “Next”.

image

Clickt “Next”.

image

Click on “Install”.

image

You will be prompted in the middle of the installation to download additional files, these are noted in the Release Notes. If you don’t have access to download these at this time, you will have to download them later.

image

Lets click on “Yes” and have it download the files for me.

image

You will also be prompted to copy files into your MDT Deployment Share during the install process. Click “Yes” on this prompt.

image

Click “Finish” to exit the installation.

image

Post-Install Changes – Lite Touch

After installing, the installer will have downloaded the required files into your DeploymentShare\Tools folder.  If you choose to download these manually, make sure to put the files in the \Tools folder as you see below. 

image

If you open up the Deployment Workbench and create a new Task Sequence, you will see 3 new templates available.

  • Standard Client Task Sequence with P2V Migration
  • Standard Client Replace Task Sequence with P2V Migration
  • Custom Task Sequence with P2V Migration

image

Post Install Changes – ConfigMgr Integration

There is no documentation provided for ConfigMgr setup. That should be in the next Beta according to Jeremy Chapman in the video I linked above. Here are just some examples of changes you might see, this may not include all changes.

Looking at the Task Sequence Wizard for ConfigMgr (with MDT Integration), we will also see the 3 new templates.

  • Client Replace Task Sequence for P2V Migration
  • P2V Restore only Template
  • Client Task Sequence for P2V Migration

image

You will have to no doubt have to update your ConfigMgr MDT Toolkit package to include the new scripts and Tools that have been added to the DeploymentShare with the P2V installer.  Either use the wizard to create another Toolkit package for you, or manually copy over the new files as I’ve identified as “new” below.

image

A quick compare of our old Toolkit package versus the new Toolkit P2V package, shows us these are the differences, if you prefer to manually update, then copy the updated files into your existing Toolkit package.

image

That’s it for the install.  I’ll post a few more entries once I get further into my testing with the Beta.  Enjoy!

Aside

P2V Solution Accelerator Prerequisites

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 Assurance\Tools.

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 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 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.

Aside

P2V Solution Accelerator Known Issues

The known issues in P2V Migration for Software Assurance beta are categorized as follows:

· Uninstalling the P2VMigration.msi does not remove the Tools folder created in %InstallDir%\P2V Migration for Software Assurance.

One workaround is to manually delete the P2V Migration for Software Assurance instance created in the Installation directory.

· Clicking Cancel during P2V Migration installation does not cancel the process.

· On Windows XP operating systems, Disk2vhd.exe is hidden during the Capture VHD phase, but it is minimized to the task bar in Windows Vista. Clicking Help/Cancel in the Disk2vhd.exe tool while the Capture VHD task is running is not supported.

· Capturing multiple disks/partitions is currently not implemented; thus, if you are trying to run Windows Vista Dual partition (with one BitLocker® Drive Encryption partition) to Windows 7, restoring VHD to Windows Virtual PC will fail with a Missing Operating System error.

· If a non-administrative user has to run the Add Old Apps to Windows 7.hta script to add old operating system applications to the Windows 7 Start menu, that user would need administrator credentials.

· In Domain Join scenarios, the Add Old Apps to Windows 7.hta script is not run automatically: You must run it manually.

Aside

P2V Migration for Software Assurance Explained

Stephen Rose has a nice post over his blog that discusses the history of the the P2V Solution Accelerator and goes into a little more detail about the product. 

“By now the announcements have gone out for the Beta, been blogged about and seen in other social networking channels, so I thought I would do something a bit more in depth on this for the Springboard Blog.
A little (recent) history…

In Fall of 2009 there was a perfect storm of tools and automation to enable something I have wanted to do for some time, automate local physical-to-virtual migration of a Windows client machine and redeliver and integrate that old environment within a new Windows build using full automation. The pieces we had in November 2009 were:

  1. Sysinternals Disk2VHD
  2. Virtual PC with shell integration
  3. RemoteApp hotfixes for Windows XP SP3 and newer clients
  4. Microsoft Deployment Toolkit 2010

At that point, the ingredients were fundamentally there to get everything working. In the Spring another valuable component came online to enable Virtual PC on machines without Hardware Assisted Virtualization. With all of these components in place, it was time to glue everything together and get it working end-to-end. Being a deployment guy, I’ve always been a fan of task sequencing engines and I knew that MDT could do everything I needed to configure the right things at the right times and drop the right components needed in the process.”

Read more here.

Aside

Announcing the new P2V Migration Tool for Software Assurance

The Nexus SC blog has posted some great info on migrating users to Windows 7 while keeping the users previous Windows XP (or newer) environment available to them in the new OS.  It’s like having your cake and eating it too:

Hey everyone, if you are considering any type of client migration on you way to Windows 7 , and you have thought about how to manage the end user experience through the process, you may want to check this out.

P2V Migration for Software Assurance uses the Microsoft Deployment Toolkit and Sysinternals Disk2VHD to convert a user’s existing Windows XP or newer client environment to a virtual hard disk then automates the delivery of an updated and personalized Windows 7 operating system containing virtual machine with the user’s previous Windows environment, applications and Web browser. The user’s previous virtual desktop retains its existing management components, domain membership and policies. The process also publishes applications and the browser for the user to access them seamlessly within Windows 7’s start menu.

To continue reading and to get all the details on how this works see Announcing the P2V Migration Tool for Software Assurance.