In this blog post I will cover the steps to create a key file to sign a MP for SCSM. You will need an install of Visual Studio. If you don’t have a license for the full version of visual studio you can down an express version Once you have Visual Studio installed you need to open the Developer Command Prompt.

Type “sn –k <Filename.snk>”

Save this key file for future use with the SCSM Authoring tool.

Incase anyone runs into the issue there is a bug in VMM SP 1 Beta that doesn’t support Hyper V Virtual Switches to be bound to  teamed NICs in Server 2012.

symptoms I experienced were: Logical networks did not populate in VMM correctly, Virtual switches didn’t show up in VMM, when you could get the virtual switches to show up in VMM  and removed them to rebuild them they destroy the NIC team in addition to the virtual switches.

The solution to this is to bind the virtual switches to a single NIC then everything works.

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.