You use Microsoft System Center Virtual Machine Manager (VMM) 2008 R2 to manage your
Hyper-V environment.
The finance department uses a legacy application that is not supported on Windows Server
2008 R2. The application runs on a server that has the following configuration:
Windows 2000 Server operating system
One 10GB hard disk, FAT formatted
512 MB of RAM
You need to ensure that you can perform a physical-to-virtual (P2V) conversion of the
server. What should you do?
A.
Run the convert c: /FS: NTFS command on the server.
B.
Use offline P2V.
C.
Increase the server’s RAM to at least 1024 MB.
D.
Use online P2V.
Explanation:
The following table lists some of the differences between the online and offline P2V
conversions. Requirements on the Source Machine To perform a P2V conversion, your
source computer:
Must have at least 512 MB of RAM.
Cannot have any volumes larger than 2040GB.
Must have an Advanced Configuration and Power Interface (ACPI) BIOS – Vista WinPE will
not install on a non-ACPI BIOS.
Must be accessible by VMM and by the host computer.
Cannot be in a perimeter network. A perimeter network, which is also known as a screened
subnet, is a collection of devices and subnets placed between an intranet and the Internet to
help protect the intranet from unauthorized Internet users. The source computer for a P2V
conversion can be in any other network topology in which the VMM server can connect to
the source machine to temporarily install an agent and can make Windows Management
Instrumentation (WMI) calls to the source computer.
The following table lists the Windows operating systems for which P2V conversions are
supported in VMM2008 and in VMM2008R2.
Supported Operating Systems for P2V Conversions in VMM2008 and VMM2008R2