How to configure dynamic optimization in VMM 2012R2 (UR6)

 

Today I want to introduce you to one of my favorits features in Microsoft System Center Virtual Machine Manager. It is dynamic optimization, which balences virtual machines on Hyper-V hosts and improves utilization of the hosts.

With dynamic virtualization you can balance the utilization to the host optimum and shutdown hosts that are no longer needed.

How can you configure dynamic optimization.

1. Connect to the VMM Console and right click on the hostgroup you want to optimize. Than click on properties.
08-05-_2015_19-23-19

1. In the Properties you navigate on Dynamic Optimization.
08-05-_2015_19-23-45

3. In the menu you now can configure the interval when your cluster will optimize.

08-05-_2015_19-24-31

4. Now you configure the interval when Dynamic Optimization will check your hosts and move virtual Machines around to balance them.

08-05-_2015_19-24-20

 

 

5. Now you set the Thresholds when virtual Machines should be moved. For that you need to do some calculation work.

– Number of hosts
– Number of VMs per host and
– Hardware configuration of your hosts
– In optimal power and performance range of your servers (you normally get the information from your ODM)

08-05-_2015_19-26-09

6. Last but not least “enable power optimization”.

08-05-_2015_19-26-22

That’s a cool option to reduce costs by shutting down unneccessary hosts. First you set the threshold when you want to shutdown hosts. At next you can set the time periode when you want to power optimize. For example you you want to have all your hosts online during business hours and want to shutdown all unneccessary hosts during night time. With these two options you can do so 🙂

08-05-_2015_19-27-52

 

I hope that blog gives you a short overview about that cool feature. Feel free to send me a mail if you have more questions.

How to delete a Hyper-V converged switch with System Center Virtual Machine Manager Update 5

With System Center Virtual Machine Manager Update Rollup 5 there came some real cool features. One of my favorit is to deleted and manage Windows Server Hyper-V converged switch or how it is called in VMM standards switch.

Before you can see and work with the VM Switch your VMM environment musst be on Update Rollup 5 and VMM need a network connect to the Hyper-V Host for the whole time. So it might be neccessary to connect one NIC of the host to you management network.

VMMSW01

 

First put the Mode in Maintance Mode

VMMSW06

The easiest way to delete the converged switch is to open the Hyper-V Host properties.

VMMSW02

Go to Virtual Switches

VMMSW03

 

 

 

Now select the switch you want to delete and press delete

VMMSW04

 

If all went well, the task in VMM should be green and your vNIC on the host should be removed.

VMMSW05

 

Free ebook: Microsoft System Center Deploying Hyper-V with Software-Defined Storage & Networking

Microsoft recently published a new ebook about Deploying Hyper-V with Software-Defined Storage & Networking. You can find it here.

Error /Faile Hyper-V Host has an unsupported VMM Agent installed

When you update your System Center Virtual Machine Environment, you maybe face the issue that your Agent version is outdated and you are not able to update it.

VMM01

The easiest way is to logon to the host and uninstall the old agent.

VMM02

After you uninstalled it, run the task in VMM again.

VMM03

 

Afterwards it should be fine.

 

Error “Could not udpate managed code add-in pipeline” when starting system center virtual machine manager

Some of you maybe face the issue below when installing the VMM management console on a client.

VMM-Log-Error01

The reason for that issue is, that you user has no read/write permission on the folder.

First step to fix the issue navigate to the folder. In my case C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin but it depends on where you installed the VMM.

VMM-Log-Error02

Than you need to change the permission to full controll for your your user or user group (I use my VMM Admins Group). That fixes the issue.

VMM-Log-Error03 VMM-Log-Error04