You have a Windows Server 2012 R2 Hyper-V environment that includes System Center 2012 R2 Virtual Machine Manager (VMM). The environment includes five physical servers. The servers are configured as f

Question

Options

• ANYC-WEB
• BNYC-PR
• CNYC-DEV
• DNYC-FS
• ENYC-EX

• A
  75% (48)
• D
  17% (11)
• E
  8% (5)

Explanation

The source computer cannot have any volumes larger than 2040 GB. This disqualifies NYCFS( not D) and NYC-EX (not E). - 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 2040 GB. - 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 - The source computer should not have encrypted volumes. --> If the source computer has encrypted volumes, an offline P2V conversion may render the computer unbootable. Answer: So based on the prerequisites, NYC-FS, NYC-EX and NYC-PR needs to be reconfigured As of System Center 2012 R2, you can no longer perform P2V conversions in VMM. For information about how to use an earlier version of Virtual Machine Manager to mitigate this change, see the: "How to perform a P2V in a SCVMM 2012 R2 environment blog" - environment.aspx

No community discussion yet for this question.