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.



First put the Mode in Maintance Mode


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


Go to Virtual Switches





Now select the switch you want to delete and press delete



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



Altaro Webinar Upcoming features in Hyper-V vNext with @JoeElway & @RicksterCDN

Hi Guy’s,

Altaro will host a webinar about Upcoming features in Hyper-V vNext with my personal superheros Mr. Aidan Finn  (@JoeElway) and Rick Claus.

Join us on Thursday, 26th March 2015 at 4PM CET


Original Blogpost

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.


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


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



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.


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.


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


Now Part of the Microsoft Azure Community Germany blogger crew

Hi everybody,

I’m happy to say the Oliver Michalski invited me to join the crew of Microsoft Azure Community Germany. :)

I will to give my best to show that I’m worthy.

My Microsoft Azure Community Profil

How to setup Azure Backup with Synology Storage

Hello everybody,

today I want to show you how to setup a disk to cloud backup with the new cloud backup feature from synology storage. In my environment I use Azure as backup target.

Why do I use Azure?

I backup some of my important VMs to Azure as desaster recovery. So if my local systems fail I fire up the VMs in Azure.


1. You need to create a new Azure Storage were you store your data. From a security standpoint I would not suggest to use a storage shared with other Azure services you have.




2. After you created one you need to create a new management access key. We will need it later.


3. Now the needed preparations on Azure are done. Next Logon to your Synology and select the Backup & Replication Plugin.


4. Now you click create and select the backup typ you want.

File Backup – You can select Files and Folder you want to backup.

LUN Backup – Backups a complette LUN on Synology LUN on Azure



5. Now you select “Public Cloud Backup Destination”


6.  Now you select Backup to Azure


7. Now you enter your Azure Storage account data and create a new storage container


8. Now enter your container name you want to use



9. When everything went well it should look like on the picture below




10. In the next step you need to select the volume and share or LUN you want to backup




11. Here you can also select applications to backup. I won’t do that in my szenario.




12. In the last step you need to do transfer, backup and shedule settings.









My first official pre press book review – Learning System Center App Controller

I’m happy to tell you that the first book I was part of the reviewer team is public now. :)

8538EN_B04004_Learning System Center App Controller


Nasir Naeem wrote about implementing appcontroller and gives you a good start with the product. I’m happy to get the chance to help him with the book and want to thank packt for the offer.

You can buy it here.



Synology configuration for max. IOPS with Hyper-V

Hello everybody,

as most of you know I’m using a Synology DS1813+ as storage for my testlab. Last week I took some time to change my configuration to improve the IOPS for my Hyper-V Systems.

My old configuration with RAID 10 and Block based iSCSI LUNs only brought about 6000 IOPS, so I needed to improve to get more VMs up.


Let us start with the Hardwareconfiguration. I’m using a DS1813+ with 8 Disk splitted as followed.

Disktyp Count Capacity HD Vendor & Typ Disk Role
SSD 2 120 GB Kingston SV300S37A120G Cache
HDD SATA 7.200 RPM 6 1000 TB 2x Seagate ST1000DM003-1ER162
3x Seagate ST1000DM003-1CH162
1x Seagate ST31000524AS

I connected three 1 Gbit/s ports in LACP to my SAN network. So there should be enough bandwidth.


My disk are configured as followed:

The SSDs are configured as Cache Volume for our later Hyper-V VM Volume. When you configure the SSC Chache choose “Read-Write”.



Now back to the harddrives. You should configure RAID 10 for the disks. You can use RAID 5 too if you need the capacity but you will lose at least 1/3 of the final performance.




Now you need to create the volume for you VMs. Here comes the point were I lose some performance because I need to create milti volumes on one RAID. For more performance you should choose single volume on RAID but you cannot use the disk any longer for more volumes.



The volume must be configured with LUN allocation unit size 4KB for Windows ODX.



Now you create the iSCSI Volume and Target. Here you choose regular files and advanced LUN features. If do not use thin provisioning, you will get some more IOPS too but that does not matter.




So that’s all you need to do on the storage. Next you need fomat the drive. Here I would suggest to format the driver with NTFS and 4KB unit size.




As a resulte I got a max. from nearly 12.000 IOPS out of my Synology DS1813+ :)  Not bad for are SOHO Diskarray ;)