In this blog post I am going to cover the install of the HP Proliant Virtual Machine Manager integration Kit, I will follow up with a second post that will cover how to update you WinPE images.

You can find the download here the current version is 7.2 it was released in March 2013.

Run the hpscvvm2012kit-2013.02.07.exe on the VMM Server, make sure that you have closed the VMM console other wise the install will generate an error during the verify step.

Continue reading


Today I figured out an issue that has been holding up moving forward with my deployment of Hyper V. I didn’t find much on the web when I first ran into this issue so I hope this helps someone else in the future.


Building a 5 node Windows 2012 Hyper V with a CSV the storage is presented from a HP EVA 6000. Initially the build was fine until I started testing failover testing. On one of the node reboots storage failed to come back online. This led me to do some additional testing on the Cluster Shared Volume, found that I could not change the owner of the volume.

[ Name] Microsoft-Windows-FailoverClustering
[ Guid] {BAF908EA-3421-4CA9-9B84-6689B8C6F85F}
EventID 1069
Version 2
Level 2
Task 3
Opcode 0
Keywords 0x8000000000000000
[ SystemTime] 2013-03-05T06:02:22.956203200Z


EventRecordID 30959
[ ProcessID] 6876
[ ThreadID] 6252
Channel System
Computer HV04.domain.local
[ UserID] S-1-5-18


ResourceName Cluster Disk 1
ResourceGroup ff5467c6-38dd-42f0-b7a3-6cbcde5d0d32
ResTypeDll Physical Disk
ApplicationErrorCode Element not found.
ErrorCause 0x490

After a lot of double checking everything and updating the firmware on the EVA and all of the drivers on the server. The problem still persisted but I was able to verify at this point everything was running with drivers for Windows 2012. So this either had to be a bug or a setting that was incorrect. It turned out to be a host persona setting in the EVA.

The Operating system type was set on windows on some of the host in the cluster, after changing the setting to Microsoft Windows 2008, I was able to change the owner of the CSV without any problems.

Update April 2013, if you are using VMM setup your networks in VMM and allow VMM to the teaming.

This blog post is a follow up to my previous post about identifying and naming NICs on HP BL460c Servers with Virtual Connect Flex 10 to build my HyperV Server. I have modified that script a little to keep more of the configuration items at the top of the script and I have added Nic teaming to the script. Once the OS is installed (the script could be integrated into a MDT/OSD task sequence) you can run this script and then you are ready to assign IP addresses to the Teams and adjust any advance NIC settings.

Remember don’t team your iSCSI NICs, you want to setup MPIO for your iSCSI connections.

My first blog post! In this post I wanted to share a script that will be very helpful for me going forward working with HP Virtual Connect Flex 10 and HP BL460c that run a Microsoft OS. In the past we have always spent a lot of time figuring out what NIC maps back to the network we configured in virtual connect.


You can configure 8 NICs/networks with Virtual Connect Flex 10


(Image is of an old ESX Profile in virtual connect)

Using the above Virtual connect Profile we now need to rename our NICs in windows. You need to ether install Powershell v3 or run this on Server 2012.


Set-ExecutionPolicy -ExecutionPolicy Unrestricted

#Get all of the Physical NICs Hardware Info

# the function value ties back to the order of the port number in Virtual Connect

$NICS = Get-NetAdapterHardwareInfo

foreach($nic in $NICS)


#Get the function number for each nic as we loop through them

$NicID = $nic.Function

Switch ($NicID)


  #Name Each NIC so you can easily identify what network each is plugged into.


                           0{ Rename-NetAdapter -Name $nic.Name HyperV_Mgmt_Bay_1 }

                            1{ Rename-NetAdapter -Name $nic.Name HyperV_Mgmt_Bay_2 }

                            2{ Rename-NetAdapter -Name $nic.Name VM_Networks_Bay_1 }

                            3{ Rename-NetAdapter -Name $nic.Name VM_Networks_Bay_2 }

                            4{ Rename-NetAdapter -Name $nic.Name Live_Migration_Bay_1 }

                            5{ Rename-NetAdapter -Name $nic.Name Live_Migration_Bay_2 }

                            6{ Rename-NetAdapter -Name $nic.Name iSCSI_Bay_1 }

                             7{ Rename-NetAdapter -Name $nic.Name iSCSI_Bay_2 }




You can now team your NICs, I encourage you to do this also with powershell script  That will most likely be my next Blog post.