2 . You must have a sysprep’d VHDX file containing Windows Server 2012 R2. This
could be the same VHDX file you use to deploy virtual machines, but it must
match the type of system. For example, if the server is BIOS based, the VHDX
should be from a generation 1 type VM.
3 . A physical computer profile is created in SCVMM that SCVMM 2012 R2 allows you
to configure if it will be used for a Hyper-V host or a Windows file server. In this
profile, the VHDX file to be used is configured along with items such as domain
membership, naming, product key, specific actions, and configurations. This
profile will be used when deploying the physical host.
4 . The physical server to be deployed is added to SCVMM via the Fabric workspace.
The physical server must support one of the SCVMM-supported out-of-band
management protocols such as IPMI or SMASH. You must have the address and
credentials for the connection. Add the server to SCVMM (as shown in Figure
5.10), which will then deploy the new server by copying the VHDX file to the target
server and configuring the host to boot from the VHDX file.Figure 5.10 Selecting the protocol to be used for the new server to be provisioned
If you run into problems using the SCVMM host deployment, a troubleshooting
flowchart, which is a great resource for helping to identify problems, is available at the
following location:
[http://blogs.technet.com/b/scvmm/archive/2011/04/20/ troubleshooting-os-](http://blogs.technet.com/b/scvmm/archive/2011/04/20/ troubleshooting-os-)
deployment-of-hyper-v-through-sc-vmm-2012.aspx