Last updated by at .

  • Microsoft Azure
  • Virtual Machine Manager

Tag: Private Cloud

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. Normally this works fine but if you have newer hardware, your Windows Server Image does 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 fails, since the WinPE image has not network drivers included it won’t 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.

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.






Microsoft Cloud OS

Free Microsoft Cloud OS webinar series in March and April

In March and April I will present together with Microsoft and itnetx in webinars about the Microsoft Cloud OS. The webinars will be free and will cover an overview about the Microsoft Cloud OS. The Microsoft Cloud OS is the story behind the latest releases of Windows Server 2012 R2, Hyper-V System Center, Windows Azure Pack and Windows Azure. The webinar series will be split in three different sessions and will cover how you can plan, build and operate a Microsoft Cloud and how you can bring the Private & Public Cloud together to make use of a Hybrid Cloud model.

Webinar 1 - Microsoft Cloud OS: Overview

Presenter: Markus Erlacher, Marcel Zehner

Webinar 2 - Microsoft Cloud OS: Planning & Architecture

25.März 2014, 09:00-10:00
Presenter: Thomas Maurer

Webinar 1 - Microsoft Cloud OS: Operation

02.April 2014, 09:00-10:00
Presenter: Thomas Maurer, Philipp Witschi

All three webinars will be free and will held in German.

Windows Server 2012 R2 Private CLoud Storage and Virtualization

Windows Server 2012 R2 Private Cloud Virtualization and Storage Poster and Mini-Posters

Yesterday Microsoft released the Windows Server 2012 R2 Private Cloud Virtualization and Storage Poster and Mini-Posters. This includes overviews over Hyper-V, Failover Clustering, Scale-Out File Server, Storage Spaces and much more. These posters provide a visual reference for understanding key private cloud storage and virtualization technologies in Windows Server 2012 R2. They focus on understanding storage architecture, virtual hard disks, cluster shared volumes, scale-out file servers, storage spaces, data deduplication, Hyper-V, Failover Clustering, and virtual hard disk sharing.

Bedsides the overview poster, Microsoft Includes the following Mini-Posters:

  • Virtual Hard Disk and Cluster Shared Volumes Mini Poster
  • Virtual Hard Disk Sharing Mini Poster
  • Understanding Storage Architecture Mini Poster
  • Storage Spaces and Deduplication Mini Poster
  • Scale-Out and SMB Mini Poster
  • Hyper-V and Failover Clustering Mini Poster

You can get the posters from the Microsoft download page.

Microsoft TechNet Conference 2013 am 12. & 13. November 2013 in Berlin

TechNet Conference 2013 – Fabric Management with Virtual Machine Manager Session Online

From 11. to 12. November the first Microsoft Germany TechNet Conference 2013 took place in Berlin, Germany. I had the chance to present a session about Virtualization Fabric Management with System Center 2012 R2 Virtual Machine Manager and Hyper-V. There were also some other great session from other Microsoft MVPs like Carsten Rachfahl, Aidan Finn, Maarten Goet, Daniel Neumann, Damian Flynn, Benedict Berger and many more. At this time thanks to Microsoft Germany for this great event and the opportunity to talk at this event.

Last week Microsoft published the sessions (German) online:

TechNet Conference 2013: Virtualisierungsinfrastruktur verwalten – Fabric Management mit Virtual Machine Manager 2012 R2

TechNet Conference Session

have fun and a good start into the week.

Hyper-V over SMB Multichannel

Hyper-V over SMB: SMB Multichannel

As already mentioned in my first post, SMB 3.0 comes with a lot of different supporting features which are increasing the functionality in terms of performance, security, availability and backup. Here are some quick notes about some of the features which make the whole Hyper-V over SMB scenario work, this time SMB Multichannel.

SMB Multichannel was designed to solve two problems, first make the path from the Hyper-V host (SMB Client) to the File Server or Scale-Out File Server (SMB Server) redundant and get more performance by using multiple network paths. If you are using iSCSI or Fiber Channel you use MPIO (Multipath-IO) to use multiple available paths to the storage. For normal SMB traffic you may be used NIC Teaming to achieve that. SMB Multichannel is a much easier solution which offers great performance. SMB Multichannel will automatically make use of different network adapters which are configured with different IP subnets.

In my tests and the environment I have build for customers, I have seen great performance with SMB Mutlichannel. It works “better” as NIC Teaming because most of the time you just get one active network interface except you use LACP and stuff like which requires the configuration of network switches with cheap switches you may lose redundancy. The same with MPIO, MPIO most of the time works great but you can sometimes not get the performance you should get in an active/active configuration. With SMB Multichannel I can simply bundle two or even more NICs together and Multichannel will make use of all of them.

Hyper-V over SMB Multichannel

Btw. SMB Mutlichannel is also a must have if you are using RDMA NICs, because of the redundancy you only get with SMB Multichannel.

SMB Mutlichannel and NIC Teaming

SMB Mutlichannel does also work in combination with Windows Server NIC Teaming. But the feature SMB Direct (RDMA) does not allow you to use NIC Teaming or the Hyper-V Virtual Switch, because you would loose the RDMA functionality.

How do you setup SMB Multichannel?

Well the setup of SMB Multichannel is quite easy because it’s enabled by default, but there are some things you should now about SMB Multichannel for designing your environment or just to troubleshoot an installation.

Verify SMB Multichannel

Verify that SMB Multichannel is active on the client

Verify that SMB Multichannel is active on the server

You can also disable or enable Mutlichannel if you need to.

To see if all the right connections are used you can use the following commands on the client to see all the SMB connections and verifiy that all SMB Mutlichannel connections are open and using the write protocol version.

SMB Mutlichannel Constraint

Another thing you have to know about SMB Mutlichannel is how you limit the SMB connection to specific network interfaces. For example, you have a Hyper-V hosts which has an 1 gigabit network adapter for management and stuff and you have two 10Gbit (or greater) RDMA interfaces which should be used for the connection to the storage, you want to make sure that the Hyper-V hosts only uses the RDMA network interface to connected to the storage. With a simple PowerShell cmdlet you can limit the Hyper-V host to only access a file shares with the RDMA interfaces.

  • Fileshare where the Virtual Machines are stored: \\SMB01\VMs01
  • Name of the 1 GBit network interface for Management and stuff: Management
  • Name of the RDMA interfaces: RDMA01 and RDMA02

Make sure you run this on every Hyper-V host, not on the SMB file server.

Well there is a little bit more behind SMB Multichannel but  this should give you a great jumpstart into this feature. If you want to know more about SMB Multichannel checkout Jose Barretos (Microsoft Corp.) blog post on The basics of SMB Multichannel.

System Center Advisor now adds Monitoring for Virtual Machine Manager

System Center Logo

Daniele Muscetta posted a blog article on the System Center Operations Manager Engineering Blog some days ago that System Center Advisor now supports System Center 2012 SP1 Virtual Machine Manager.

If you have Virtual Machine Manager servers in your environment, look for new alerts about their configuration – and that of their agents.
This represents the first step towards providing proactive guidance and configuration best practices for all System Center components that power your private cloud infrastructure

It’s great to see that the integration between the different parts of the System Center product family gets even better connected.

Where can I learn more about Advisor?

If you are not familiar with System Center Advisor – what it is, what it does and how it works, please refer to:

  • This couple of blog post

  • This TechED presentation (Joseph starts speaking about Advisor at about 41:25)
  • The official System Center Advisor website

System Center 2012 SP1 Virtual Machine Manager Update Rollup 3 available

System Center Logo

Microsoft just releaed Update Rollup 3 for System Center 2012 SP1 which includes updates and fixes for Virtual Machine Manager, Data Protection Manager, Operations Manager and App Controller.

Virtual Machine Manager Update Rollup 3

The Update Rollup 3 for Virtual Machine Manager includes fixes for 25 issues. The Update Rollup includes fixes for the Virtual Machine Manager Server, Console and Agent.

  • Virtual Machine Manager Administration Console Update (KB2858509)
  • Virtual Machine Manager Server Update (KB2858510)
  • Virtual Machine Manager Guest Agent Update (KB2858511)

Which fix the following issues: