Tag: WDS

SCVMM Bare-Metal Fails

Add drivers to SCVMM Bare-Metal WinPE Image

A long time ago, I wrote a blog post on how you can use System Center Virtual Machine Manager Bare-Metal Deployment to deploy new Hyper-V hosts. Usually, this works fine, but if you have more modern hardware, your Windows Server Image may not include the network adapter drivers. Now, this isn’t a huge problem since you can mount and insert the drivers in the VHD or VHDX file for the Windows Server Hyper-V image. But if you forget to update the WinPE file from Virtual Machine Manager your deployment will fail, since the WinPE image has not network drivers included it won’t be able to connect to the VMM Library or any other server.

You will end up in the following error and your deployment will timeout on the following screen:

“Synchronizing Time with Server”

SCVMM Bare-Metal Fails

If you check the IP configuration with ipconfig, you will see that there are no network adapters available. This means you have to update your SCVMM WinPE image.

First of all, you have to copy the SCVMM WinPE image. You can find this wim file on your WDS (Windows Deployment) PXE Server in the following location E:\RemoteInstall\DCMgr\Boot\WIndows\Images (Probably your setup has another drive letter.


I copied this file to the C:\temp folder on my System Center Virtual Machine Manager server. I also copied the extracted drivers to the C:\Drivers folder.

After you have done this, you can use Greg Casanza’s (Microsoft) SCVMM Windows PE driver injection script, which will add the drivers to the WinPE Image (Boot.wim) and will publish this new boot.wim to all your WDS servers. I also rewrote the script I got from using drivers in the VMM Library to use drivers from a folder.

$mountdir = "c:\mount"
$winpeimage = "c:\temp\boot.wim"
$winpeimagetemp = $winpeimage + ".tmp"
$path = "C:\Drivers"
mkdir "c:\mount"
copy $winpeimage $winpeimagetemp
dism /mount-wim /wimfile:$winpeimagetemp /index:1 /mountdir:$mountdir
dism /image:$mountdir /add-driver /driver:$path
Dism /Unmount-Wim /MountDir:$mountdir /Commit
publish-scwindowspe -path $winpeimagetemp
del $winpeimagetemp

Update SCVMM WinPE

This will add the drivers to the Boot.wim file and publish it to the WDS servers.

Update WDS Server

After this is done, the Boot.wim will work with your new drivers.

Hyper-V vs. VMware vSphere – Host Deployment

Windows Server 2012 RC Logo

VMware vSphere Enterprise Plus offers  a solution for centralized deployment of VMware Hypervisor hosts on physical hardware.

How does the deployment of Microsoft Hyper-V Server work? Microsoft Hyper-V can be deployed as Windows Server role or as Microsoft Hyper-V Server. Both setups are based on the normal Windows setups and you can use the same deployment processes.

  • DVD
  • USB
  • Windows Deployment Services (WDS)
  • Microsoft Deployment Toolkit (MDT)
  • System Center Configurations Manager

or my favorite deployment method: Bare-Metal Deployment with System Center Virtual Machine Manager. Blogger and Microsoft Consultant Michel Lüscher wrote a great blog post about how you can use the bare-metal deployment feature in SCVMM.

Create an OS Image in Windows Deployment Services (Capture Image)

Here I will show you how you can simply create a new Image in WDS (Windows Deployment Services). You can use this to create own Images for your Servers or PCs or update existing Images.

  1. Add Capture Images to your WDS
    Windows Deployment Services
  2. Update your Computer or VM with the latest Software.
    Windows Deployment Services
  3. Use Sysprep to generalize the Machine. You can find sysprep.exe in C:\Windows\System32\sysprep
  4. After the Reboot boot into PXE and boot the Windows Capture Image
    Capture Image
  5. Now you can use the Image Capture Wizard
    Capture Image Wizard
  6. Choose which volume you want to capture if you have just one partion in your installed Image the Volume would be D:\ (C: is the booted Windows PE from the Windows Deployment Service)
    Capture Volume
  7. Now you have to choose the name of the WIM file and the location, before you can upload it to the WDS Server you have to save it on a local partion. After that you can choose your WDS Server and the Image Group you want to upload the image after the Volume is captured.
  8. Now the capturing process will start
  9. After the capturing process is finished and the image is uploaded you can find the Image in the Image group on your WDS Server
    Capture ImageWDS
  10. Now you can Rollout this new Image