Category: ProLiant Server

HPE Azure Stack Innovation Center

Let’s talk about the HPE Azure Stack Innovation Center

Together with HPE, I did some short videos about HPE Azure Stack and the HPE Azure Stack Innovation Center in Geneva. The videos are very short to give you a quick idea about the different scenarios and the benefits of the Innovation Center as well as the HPE solutions. If you want to know more about it, you can check out my blog and look for my articles on Azure Stack and Azure.

About the Azure Stack Innovation Centers

To help you get started on your journey with Microsoft Azure Stack, HPE and Microsoft have built Azure Stack Innovation Centers. Staffed by HPE and Microsoft experts, and leveraging the latest industry-leading Azure Stack hardware and software solutions, the Innovation Centers are designed to help simplify and accelerate your hybrid cloud journey.

In simple words, the Innovation Centers are a place to try out Azure Stack multi-node systems, do a proof of concept and test your real-world workloads. We used the Azure Stack Innovations Centers to work with customers, to try out their workloads directly on a full multi-node system. This helps to better understand the benefits and challenges for the specific customer workloads and get some hands-on experience. It is also a great possibility to test out the Azure Stack Operator capabilities and tasks.

Thomas Maurer about the HPE Azure Stack Innovation Centers

Thomas Maurer talks about how the HPE Innovation Center helps partners and customers on Azure Stack Implementation projects!

PowerShell NetAdpater Advanced Property

Hyper-V Network Virtualization NVGRE: No connection between VMs on different Hyper-V Hosts

I have worked on some project with Hyper-V Network Virtualization and NVGRE, and today I have seen an issue with Encapsulated Task Offloading on some HP Broadcom Network adapters.



I have Hyper-V Hosts running with 10GbE Broadcom Network Adapters (HP Ethernet 10Gb 2-port 530FLR-SFP+ Adapter) with driver version (released in 2014). I have created a new VM Network based on Hyper-V Network Virtualization using NVGRE. VM1 is running on Host1 and VM2 is running on Host2. You can ping VM2 from VM1 but there is no other connection possible like SMB, RDP, HTTP or DNS. If you are using a NVGRE Gateway you can no even resolve DNS inside those VMs. If VM1 and VM2 are running on the same Hyper-V host everything between those VMs works fine.

Advanced Driver Settings

If you are using Server Core, which you should by the way, you can use the following command to check for those settings:

Get-NetAdapterAdvancedProperty -Name <NICNAME>

PowerShell NetAdpater Advanced Property



The Broadcom Network adapters have a feature called Encapsulated Task Offloading which is enabled by default. If you disable Encapsulated Task Offloading everything works fine. You can disable it by using the following PowerShell cmdlet.

Set-NetAdapterEncapsulatedPacketTaskOffload -EncapsulatedPacketTaskOffloadEnabled $false -Name <NICNAME>

After that connection inside the VMs started to work immediately, no reboot needed.

Building a new Hyper-V Private Cloud Lab

Two years ago I created my first real IT Lab with some HP ProLiant ML110 G5. I used this in the past years to test new products and projects. The Lab at this time was very limited, no storage, no cluster, not much RAM and weak CPU performance. Not much help if you work a lot with Hyper-V Clusters and System Center products.

I was looking around for some time now to find a cheap offer for new servers. In the last week I found a offer from Cisco with c200 M2 servers and I couldn’t resist to buy two of the for my Hyper-V Cluster nodes. The offer was a special deal which was even cheaper than building the servers by my own, at this point thanks to my former employer Atlantis Informatik AG.

Now what I will do is creating a new Hyper-V Cluster friendly environment with two Cisco C200 M2 Hyper-V nodes, one HP ML110 G5 as Storage Server and one of my old HP ML110 G5 servers as Hyper-V Server which all my Management servers and Active Directory will run on.

Lab Overview

If you want to know more about Hardware you can use for a Hyper-V Lab I recommend the posts of Carsten Rachfahl on (german).

Hardware Configuration

Hyper-V nodes:

cisco c200 m2

2x Cisco C200 M2 – Intel Xeon 5620 2.4GHz Quad Core, 16GB RAM, Remote Management, IPMI, 6 Networkports

Storage Server:


1x HP ProLiant ML110 G5 – Intel Xeon E3110 3.0 GHz Dual Core, 8GB RAM, 4x 500GB Raid 10, 3 Networkports

Management Hyper-V node:


1x HP ProLiant ML110 G5 – Intel Xeon E3110 3.0 GHz Dual Core, 8GB RAM

HP Microserver N40L Raid Utility and Driver

HP ProLiant MicroServer N40L

Now after setting up my HP Microserver N40L as a Windows Homeserver I had to install the utilities to monitor the Raid and other Hardware. On the HP Support Site you can find a link to the AMD Download page where you can download the Chipset Driver which also includes the Raid Driver and the Raid utility.

Download the AMD Chipset Drivers for the HP Microserver N40L

WHS with HP ProLiant MicroServer N40L

HP ProLiant MicroServer N40L

Two days ago my HP ProLiant MicroServer N40L arrived. Since I need more disk space I was looking for a good NAS solution. My first experiences with some of the common NAS vendors were not that great, most of the time the NAS was very very slow. Now this may has changed in the past years but still I prefer a mini server with a Windows OS.

That is where the HP ProLiant MicroServer and Windows Home Server 2011 meet, so I gave it a try. And guess what, it’s a great solution and it does exactly what I need. It stores files with a good performance, it’s quiet, it does not need a lot of power, let me stream content to my Xbox and enables me remote access to my data.

HP ProLiant MicroServer N40L

  • HP ProLiant MicroServer N40L
  • AMD Turion II NEO N40L 1.5GHz, 15W
  • 2x 2TB WD Caviar Green WD20EARX 5400 rpm, 64 MB Cache, 8,9 ms, SATA3
  • Windows Home Server 2011

Now at the moment I use these two WD 2TB Disks in a RAID 1, and the N40L still offers space for two other drives.

HP Network Interface does not start.

I just installed two new HP ProLiant DL360 G6 with Microsoft Windows Server 2008 R2. Everything worked fine until I installed the HP Support Pack which includes Drivers and Firmware for the HP Server.

This device cannot start. (Code 10)

After I installed the HP ProLiant Support Pack one of my Network Interfaces could not start. I got the following error in the Device Manager:

HP NC382i DP Virtual Bus Device
This device cannot start. (Code 10)

I tried to uninstall the device and rebooted the server but this didn’t work. I had still the same error.

The problem was that just uninstalling the driver does not work, you also have to check the checkbox on “Delete the driver software for this device.”

Delete the driver software for this deviceAfter doing that you can rescan for new hardware and the system will find this adapter again and everything will work fine.

Install HP Support Pack on Hyper-V R2 Core Server

If you are using Microsoft Hyper-V R2 Core Server, installing the HP Support Pack is a little different. This post should show you how this is done.

  1. Download the latest HP Support Pack for Windows Server 2008 R2 and extract that on your Management Server or PC.
  2. Now copy the extracted folder to the Hyper-V Core Server. In my case i copied in the C:\ root of the Core Server via the administrative network share. If you have easy physical access to the server, you could also use a USB stick or something like that.
    Copy HP Support Pack to Core Server
  3. Now connect to the Core Server and use the cmd.exe to navigate to the folder with the HP Support Pack
    Hyper-V Core Server HP Support Pack
  4. Run the “hpsum.exe” to start the HP Smart Update Manager
  5. When the HP Smart Update Manager is started you can use it like on a Full Server installation of Windows Server 2008
    HP Smart Update Manager on Hyper-V Core ServerHP Smart Update Manager on Hyper-V Core ServerHP Smart Update Manager on Hyper-V Core Server

You could also try to run the HP Smart Update Manager on another machine and use the remote connection feature.