SCVMM 2012 – Bare-metal deployment (checklist)

My name’s Thomas Roettinger and I am a private cloud and virtualization Premier Field Engineer at Microsoft.

During my Christmas holidays I had time and also hardware to work on the bare-metal deployment feature of SCVMM 2012.

The result is a nice checklist and some considerations that hopefully help you in your own environment

The hardware I used is DELL PowerEdge M600 blade server. All servers have been updated to the latest Bios 2.4.0 and iDRAC 1.60 A13 firmware.


These are the detailed steps I followed for bare-metal deployment (These steps do not include all prerequisites I configured before but will be in the checklist at the end of this blog post)

1. Open SCVMM 2012 Console

2. Go to Fabric

3. Add Resources  --> Hyper-V Hosts and Clusters

4. Select Physical computers to be provisioned as virtual machine hosts

5. Select Run As account with Remote Management Board credentials and BMC protocol. DELL Servers do IPMI


6. Enter IP-Address of the server remote management board

7. Select the Host group where the server should be placed and your Host Profile

8. Specify a hostname for the server that you pre created in AD

9. Press Finish to start the deployment


This is the whole process in SCVMM 2012 to do bare-metal deployment in a nutshell.

Now let us see what happened at the physical server in the background. I did that via the remote management board.


1. Server does a reboot and start booting from PXE

2. Now I got an error configuring the Disk and the SCVMM job aborted.

Error (21113)

Unable to configure disk on physical machine 4C4C4544-0042-5110-8057-CAC04F424731 as requested in host profile

3. After checking the X:\vmm\vmmAgentPE.exe.log file, saying that my DISK 0 is offline. I launched diskpart.exe and the list disk command showed the result. The log was right, because I had SAN Volumes attached to the server. The only way to fix that was to disconnect any FC ports.

4. Now I had to restart my SCVMM bare-metal deployment job without any FC ports connected and the job finished successfully.

Some additional consideration:

The SCVMM bare-metal deployment process does not enable Remote Desktop so this should be done with a Group Policy linked to the OU where you place your Hyper-V Hosts.

Finally I wrote this checklist that hopefully helps you to sort all show stoppers for a successful bare-metal deployment 

  1. Mount Server into Rack
  2. Connect Network Cables and configure Remote Management Board with IP Address
  3. Do not connect any FC ports !!
  4. Configure Raid Controller to have volume available for VHD placement and BCD
  5. Enable PXE Boot in Bios
  6. Update Remote Management Board to latest available vendor Firmware
  7. Update Server Bios to latest available vendor version
  8. Create Hyper-V Host OU in AD (not a hard requirement)
  9. Create Hyper-V Host Computer Account in AD
  10. Create Group Policy for enabling Remote Desktop (not a hard requirement)
  11. A configured PXE server in SCVMM 2012
  12. Create Run AS Account for Remote Management Board credentials
  13. A running DHCP Server is always required
  14. A sysprep’ed Windows Server 2008 R2 VHD in the Library and make sure the maximum VHD size fits to your physical Disk.
  15. Create Host Profile
  16. Download and place drivers for your server Hardware in the Library
Comments (2)

  1. Thank you. This helped me in identifying that run as account is actually the BMC account. I used the default account of my server and it worked.


  2. Shashikanth says:

    Hi Thomas, I am using bare metal script to deploy OS and add in my VMM, but I am getting an error (21120)
    OS deployment was successful, but DNS name resolution failed for %Name; It’s failing after 50 %, when I checked with DNS Team looks everything good. could you please help me here.

Skip to main content