Today (and yesterday) I was troubleshooting a Hyper-V bare metal deployment of a Windows Server 2012 R2 Hyper-V host from out System Center Virtual Machine Manager 2012 R2 environment.
All preparations were done (like: Marcs blog). PXE boot went well, deep discovery went well, image was succesfully deployed but then the process stuck on step 1.2.12 (Wait for physical machine to reboot and customization to be finished 0%).
When we manually join the host to the domain the step resume to 50% and stops then again. So computer name or IP address is not yet set. An IP address is already claimed from the IP pool but as I said not configured on an interface. Communication with the host is still possible.
After a lot of trial-and-error (manually register the host in DNS/ prestage computer account in AD/ use DHCP instead of IP from a pool and so on…) we replaced the Windows Server 2012 R2 OS image (stored in the SCVMM library) with a new fresh image (All Windows updates applied and firewall on all profiles disabled). Retried the operation and this time the bare metal deployment runs succesfull. We could not find a specific problem with the old OS image (we could succesfully use it for VM deployment) however when we use the image for bare metal deployment the process stuck on step 1.2.12.
So if you encounter this problem, replace your OS image in the SCVMM library with a new fresh image and retry the operation.