{"id":10187,"date":"2009-12-09T16:02:03","date_gmt":"2009-12-09T16:02:03","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=10187"},"modified":"2009-12-09T16:02:03","modified_gmt":"2009-12-09T16:02:03","slug":"vmm-p2v-migration","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=10187","title":{"rendered":"VMM P2V Migration"},"content":{"rendered":"

Microsoft System Virtual Machine Manager (VMM) 2008 R2 includes the ability to do a P2V (physical-to-virtual) migration of Windows computers.  This is usually the last critical step in a normal virtualisation project \u2013 take those physical servers that an audit identified as being candidates to be converted into virtual machines.  The process scans the contents of the hard disk and converts them into VHD\u2019s.  The machine specification is converted into a virtual machine configuration.<\/p>\n

The first step in all of this begins really when you are doing a feasibility study or sizing your virtualisation hosts and storage.  You\u2019ll run something like Microsoft\u2019s MAP (Microsoft Assessment and Planning) toolkit.  Alternatively if you have already got Operations Manager 2007 deployed then you can install VMM 2008 R2 and wait a while before running the Virtualisation Candidates report<\/a>.  That takes information from the continuous performance monitoring provided by OpsMgr.  Or you can just run individual performance reports from OpsMgr \u2013 but you need to be careful about seeing both the details and the big picture when it comes to a manual interpretation of the statistics.  And be careful about the process OpsMgr uses to store long term data.  Spikes or sudden drops may not be apparent by the data aggregation.<\/p>\n

Once you have your Hyper-V 2008 R2 platform and VMM 2008 R2 tested, documented and in production then you can start your P2V process.<\/p>\n

Here\u2019s a list of the supported operating systems:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Operating System <\/u><\/strong><\/p>\n<\/td>\n

\n

VMM 2008 <\/u><\/strong><\/p>\n<\/td>\n

\n

VMM 2008 R2<\/u><\/strong> <\/p>\n<\/td>\n<\/tr>\n

\n

Microsoft Windows 2000 Server with Service Pack 4 (SP4) or later (offline P2V only)<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Microsoft Windows 2000 Advanced Server SP4 or later (offline P2V only)<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows XP Professional with Service Pack 2 (SP2) or later<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows XP 64-Bit Edition SP2 or later<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 Standard Edition (32-bit x86)<\/p>\n<\/td>\n

\n

Yes (Requires SP1 or later.)<\/p>\n<\/td>\n

\n

Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 Enterprise Edition (32-bit x86)<\/p>\n<\/td>\n

\n

Yes (Requires SP1 or later.)<\/p>\n<\/td>\n

\n

Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 Datacenter Edition (32-bit x86)<\/p>\n<\/td>\n

\n

Yes (Requires SP1 or later.)<\/p>\n<\/td>\n

\n

Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 x64 Standard Edition<\/p>\n<\/td>\n

\n

Yes (Requires SP1 or later.)<\/p>\n<\/td>\n

\n

Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 Enterprise x64 Edition<\/p>\n<\/td>\n

\n

Yes (Requires SP1 or later.)<\/p>\n<\/td>\n

\n

Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 Datacenter x64 Edition<\/p>\n<\/td>\n

\n

Yes (Requires SP1 or later.)<\/p>\n<\/td>\n

\n

Yes (Requires SP2 or later.)<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2003 Web Edition<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Small Business Server 2003<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Vista with Service Pack 1 (SP1)<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Vista with Service Pack 1 (SP1)<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2008 Standard 32-Bit<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2008 Enterprise 32-Bit<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Server 2008 Datacenter 32-Bit<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Server 2008 Standard<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Server 2008 Enterprise<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Server 2008 Datacenter<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Web Server 2008<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows 7<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows 7<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Server 2008 R2 Standard<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Server 2008 R2 Enterprise<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

64-bit edition of Windows Server 2008 R2 Datacenter<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n

\n

Windows Web Server 2008 R2<\/p>\n<\/td>\n

\n

No<\/p>\n<\/td>\n

\n

Yes<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

You can use the Microsoft Virtual Server 2005 Migration Toolkit (VSMT) or third-party solutions (cloning, e.g. s\/w from Acronis is said to be a successful approach) for converting computers running Windows NT Server 4.0.<\/p>\n

As if that isn\u2019t complicate enough then you have to consider how you are going to do the P2V process.  There are two approaches:<\/p>\n