Tag: Hyper-v r2

TechNet Wiki: Hyper-V Tool Collection

Hyper-V R2 SP1

Microsoft and the community are really starting to work with the TechNet Wiki platform. Now thanks to James van den Berg I found a great wiki page with a collection of Hyper-V tools.

The collection includes a list of the following content:

  • Supported Microsoft Tools (Solution Accelerators, Product Downloads, etc.)
  • Microsoft Products and Solutions that are Built upon Hyper-V Technology
  • Remote Management from Client Versions of Windows
  • Unsupported Microsoft Tools (Sysinternals, MSDN/ScriptCenter Code Galleries, TechNet/MSDN Blogs)
  • Community Tools (CodePlex and blogs)
  • Third-party Free Tools
  • Hardware-Specific Tools from OEMs and Vendors
  • Partner Solutions (Commercially Available)
  • Application-specific Performance Planning/Testing/Analysis tools

You can find also a lot of other interessting content on the TechNet Wiki. For example for Exchange, PowerShell and SQL.

Install SNMP on Hyper-V R2 Core Server


If your running Microsoft Hyper-V R2 or any Windows Server 2008 R2 Core Server you can install the SNMP Feature on the command line with the command line tool dism.

First you can list all Windows Features

Dism /online /get-features /format:table  

Now you can install for the SNMP Service:

Dism /online /enable-feature /featurename:SNMP-SC

SNMP Feature Core Server

After you have done this you and you have enabled Remote Management you can mange and configure smtp via remote MMC.

SNMP Service

Important: If you need to configure the SNMP Service on a remote machine you have to install the SNMP feature on the local administrative computer. Otherwise you will not see the SNMP specific tabs.

SNMP Service

More Information on installing Windows Features on a server running a Server Core installation of Windows Server 2008 R2: http://technet.microsoft.com/en-us/library/ee441253(WS.10).aspx

Extending a Microsoft Hyper-V R2 Cluster Shared Volume


This quick blog post shows you how you can simply extend a Hyper-V R2 or Windows Server 2008 R2 Cluster Shared Volume without any downtime. First you expand your LUN in your OEM SAN management software. This is mostly of the time nothing special. But after that you have to expand the Cluster Shared Volume.

  • In your OEM SAN Management Software expand the size of the LUN or disk
  • Open the Microsoft Failover Cluster Manager and check the CSV coordinator for the disk or LUN you have expanded. The CSV coordinator is the disk owner in the cluster
  • Login to the CSV coordinator machine
  • If you are using the GUI version you can use the Disk Management under Storage in the Server Manager. You can now rescan for disks and then expand the Disk or LUN.
  • If you are using Hyper-V or Windows Server Core you can use diskpart
  • First start the cmd and open diskpart
  • type rescan
  • now type list volume, to list all volumes
  • Use select volume IDNumber, the IDNumber is the number you could see with list volume in the previous step.
  • now you can type extend
  • with list volume you can see the results

In some environments sometimes if you need to expand a Cluster Shared volume it makes more sense to create a new one and move the Virtual Machines with Storage Migration but this cannot be done without downtime.

How Microsoft Hyper-V and the Cisco UCS changed our lives

Cisco UCS Hardware

At the end of last year we had our Cisco UCS ordered and in your datacenter. In January we started the testing and made the Clusters ready for the production environment. In February we started the migration of our existing environment, mostly P2V and also some V2V migrations.

Here some interessting facts about our Cisco UCS and Hyper-V project.

  • We use 12 Cisco UCS Blades this is like 10 HE of rackspace
  • We migrated 45 Windows Servers and 47 Unix Servers in just one week
  • We replace 2 racks of server with a half rack of two Cisco UCS Bladecenters
  • We think we can replace 2-3 racks more with our two Bladecenters.
  • At the end of this year we think we could replace 4-5 racks with 1/2 rack
  • We still have a lot of physical and virtual server which will be needed to be migrated to the Bladecenter.
  • We will get even more out of our Blade Servers by activting Hyper-V Dynamic Memory as a new feature of Hyper-V R2 ServicePack 1

This migration had a lot of positive influence on other things in the datacenter.

Datacenter Power

  • we need now 4% less energie overall
  • we need now 6% less cooling overall
  • we need less space (1 and 1/2 racks at the moment)
  • now our system administrator travel 50% less to the datacenter, because of hardware defects or other administrative tasks.
  • We can deploy new servers in minutes instead of hours

I think all of this numbers (except the time we need to deploy new servers )will increase after the next migrations.

Now I started to write a series of blog posts about installing Microsoft Hyper-V R2 on the Cisco UCS system:

Microsoft Hyper-V and the Cisco UCS Bladecenter are a powerful team. The UCS Virtual Hardware takes alot of complexety from the hypervisor in your case Hyper-V. You don’t need NIC teaming and stuff like that. Thats is making it very easy to deploy Hyper-V Clusters. And with the Microsoft System Center Virtual Machine Manager you can save a lot of time in managing your clusters, hosts, virtual machine and also in P2V and V2V migrations. Since Microsoft SCVMM supports Windows Powershell you can also do a lot of scripting automation. And with the release of the new Version of SCVMM (System Center Virtual Machine Manager 2012) this will even get better for deploying new virtual machines, services and even public and private clouds.

Hyper-V R2 SP1

We started with Microsoft Hyper-V R2 Servers before the release of Service Pack 1. We think we can even get a lot more out of your systems with the new Dynamic Memory feature for Hyper-V which comes in Service Pack 1.

At the end we think choosing the Cisco UCS, Microsoft Hyper-V and Microsoft System Center Virtual Machine Manager for our datacenter was the best choice we have made, in terms of costs and technology.

Hyper-V Hotfix for Intel Sandy Bridge and Westmere

If you are using Microsoft Hyper-V with new Intel Sandy Bridge or Intel Westmere processors and our server has over 48GB of physical RAM you may get a performance decrease. Microsoft released a hotfix (KB2517329) for this problem.

This could also be a problem with a lot of Hyper-V installations on Cisco UCS, because the most of them will use more than 48GB of memory.

The performance decrease could show its self in the the following issues:

  • The CPU usage is high and the server responds slowly when you copy large files on the computer. For example, you copy a 10-GB file
  • The disk I/O performance of the virtual machines (VMs) is slow
  • Windows takes a long time to start

The hotfix is not include in Service Pack 1 for Hpyer-V R2 or Windows Server 2008 R2.

For more information about this you can check KB2517329

Cisco UCS Hyper-V Cluster – Create Hyper-V Image for Blade Servers – Part 2

We use Microsoft Hyper-V Server 2008 R2 as Operating System for our Cisco Blade Notes. The Cisco UCS does need some special drivers which are not included in Hyper-V Server Image (Network and HBA). So I created a Hyper-V Server 2008 R2 ISO file which includes the Drivers from the Cisco UCS.

I made a blog post about adding Drivers to a Windows ISO, this is pretty much the same.

  1. First Download the Hyper-V Server 2008 R2 ISO from microsoft.com
  2. Download the Drivers from Cicso.com, you can download the Bundle File which also includes firmware.
  3. Download and install the Windows Automated Installation Kit
  4. Extract the Hyper-V ISO to C:\temp\hypervr2
  5. Extract the Windows Driver folder in the Cisco Driver ISO (In my case ucs-b2xx-drivers-1.3.1g.iso) to C:\temp\Drivers\Windows
  6. Create a folder for the WIM mount point C:\temp\WIM
  7. Start Windows AIK Deployment Tools Command Prompt from Start menu
    Windows AIK Deployment Tools Command Prompt
  8. Now mount the install.wim file form the original Hyper-V Image (C:\temp\hypervr2\SOURCES) to C:\temp\WIM
    imagex /mountrw C:\temp\hypervr2\SOURCES\install.wim 1 C:\temp\wim
  9. Add Drivers with dism
    CD C:\temp\Drivers\Windows\Network\Emulex\M72KR\W2K8R2\x64
    dism /image:C:\temp\WIM /add-driver /driver:. /recurse
  10. After adding all drivers to the Image you can unmout the WIM Image
    imagex /unmount /commit C:\temp\wim
  11. Now create the new ISO file
    oscdimg -n -m -bc:\temp\hypervr2\boot\etfsboot.com C:\temp\hypervr2 C:\temp\hypervr2drivers.iso

Now you can use this new Image to deploy the Hyper-V Hosts on your Cisco UCS Blades.

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.

Remote Disk Management with “RPC server is unavailable” Error

If you have a Windows Server 2008 R2 Core Server or a Hyper-V R2 Server, which is also managed like a Core Server, you are really happy if you can use the Server Manager for this Remote Machine. Basiclly I had the the Remote Setup done. I could connect to the remote Machine with the Server Manager but when I tried to use the Disk Management on a remote Server and I got the following error “RPC server is unavailable”. After checking it I found the solution. The Problem is that the Firewall blocks the remote communication to virtual disk service. So you have to open the Firewall on the Management Machine

  1. First make sure you activated all the Remote Management options on the Remote Machine. I had all done this but its good to check that.
  2. Now you can run the following Command in cmd on the Management Machine to add the a new firewall rule
    netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes


Cisco UCS and Microsoft Hyper-V R2

Last week we run our first tests with the Cisco UCS Bladecenter, VMware ESXi and Microsoft Hyper-V R2.

I am really excited about the performance and the easy management of the Cisco Bladecenter. Maybe I get some more information about Hyper-V and the UCS out there for next week.

There is also a Microsoft TechNet event next Tuesday:

Cisco Unified Computing System + Microsoft Hyper-V/System Center = die Komplettlösung für Virtual IT und Private Cloud

Cheatsheet: How to install HP Support Pack on a Server Core installation #3

This is a HowTo step-by-step guide to install the HP Support Pack on a Windows Server 2008 R2 Core installation or Hyper-v Core installation.

  1. Download the latest HP ProLiant Support Pack for Windows Server 2008 R2
  2. Eable SNMP on Windows Server 2008 R2 Core by typing start /w ocsetup SNMP-SC
  3. Extract the HP ProLiant Support Pack on a Management Machine to C:\Supportpack
    Extract HP ProLiant Support Pack
  4. Connect to the Remote Windows Server Core for example \\hyperv01\c$
    Connect to Core Server
  5. Create the folder C:\hp on the Remote Core Server
  6. Copy the files from C:\supportpack to \\hyperv01\c$\hp
    Copy HP ProLiant Support Pack
  7. On the Core Server execute C:\hp\hpsum.exe
    execute hpsum.exe
  8. Install the HP Supportpack as usual
    HP Smart Update ManagerHP Smart Update ManagerHP Smart Update ManagerHP Smart Update Manager
  9. Reboot the Server