Adding more external IP´s to your WAP NVGRE VM´s

So I have been during these two last days been in deep waters to find out a customers demands and the possibility to add more than one external IP to the same NVGRE enabled VM network within WAP and VMM and the Hyper-V Network Virtualization Gateway this as the ports from the external application the customer has cannot be altered and they need to access several different VM´s simultaneously.

Described in this visio diagram the customer wish is:



As you maybe know, within the VMM when you have configured the HNV there is no possibility to add more external addresses in the GUI and configure port forwarding.


So how to do this then, well there is a way and that is called PowerShell on the HNV Gateway and first you add the external address and then add the NAT rules

Here is a screendump of an addition of a port rule:


To get the NatName I added the first external IP and Port rules through VMM and then I could use that information when creating the rest config from within the HNV gateway.

The following cmdlets are available on the HNV GW

Screen Shot 2014-06-03 at 19.01.09

Observe though that when adding these things directly in the HNV GW you cannot manage these rules and IP addresses in Windows Azure Pack portal or VMM!


Channel 9 videos available from TechEd US 2014

Some Serious new features in Microsoft Azure!

I am at the Microsoft TechEd in Houston and yesterday VP Brad Anderson announced several new features in Azure. I am going to highlight some of the ones that I think is really cool!

  • Multiple Site-to-Site VPN connections
  • VNET-to-VNET connectivity
  • compute-intensive virtual machine instances
  • Azure Files
  • Azure RemoteApp
  • Azure Site Recovery (Hyper-V Replica to Azure!!)
  • Client Developer VM´s for MSDN

The coolest feature I think that was presented is the Azure Site Recovery with the possibility to actually set up Hyper-V replika and that to an Azure Datacenter, how cool isn’t that? Now It became quite easy to migrate those VM´s to Azure with little downtime at no extra third-party license cost..


Another Cool new feature is the networking parts with the multiple Site-to-Site VPN and VNet-to-VNet that have been on a wishlist for some time. Being able to add several different branch offices or datacenters to your Azure Network gives new possibilities to design a good hybrid infrastructure!

Screen Shot 2014-05-13 at 13.43.57


Screen Shot 2014-05-13 at 13.44.07

For those of you that have an MSDN subscription and also activated the included Azure benefit, there was an addition of several gallery items for development and testing, VM´s with Windows 8.1 and Windows 7 has been published

Screen Shot 2014-05-12 at 15.23.27


The Azure RemoteApp gives companies the possibility to set up your applications in Azure and having them available for all different devices and not having to manage and setup an RDS on premise anymore.

Read more about the new features on Azure blog and also look at the sessions on Channel 9 when they become available

Wooohoo Delete button in Azure Active Directory

So when I was exploring the Azure Active directory some months ago I created some AD´s and then when I had done the labs I could not find the delete button, I read on a blog post that it was not possible at that time.

But now as of yesterdays releases of the new features on Azure the “Delete” button has appeared!

Screen Shot 2014-05-13 at 05.55.32

Sweet stuff isn’t it? So what happens when I press that precious button?

Screen Shot 2014-05-13 at 05.55.55


Thats kind of good that you actively have to go in and remove all users before being able to delete so that would make an extra safety barrier for accidentally removing a AAD

Screen Shot 2014-05-13 at 05.56.24


When that is done I can go ahead and delete the actual AAD :-)

Screen Shot 2014-05-13 at 05.56.55


I will add more posts during the week about my findings so stay tuned :-)


After MVMC 2.0 VM time for license activation in Azure IaaS

Maybe you read my post about migrating a VM to Azure with the MVMC 2.0 and after successfully migrated my VHD to Azure IaaS I wanted to set my VM to the right key and in Azure that is Microsoft KMS..

I do not know if it is supported to do this but here is how it is done,

The VM I used MVMC to move was a EVAL version,



So the first step was to use Dism to set the version and a KMS license Key


And then after reboot I first got this message


 but after that I checked slmgr and it reported correctly KMS and activation


Good luck in your migration to the Cloud


Regional Settings on your VMM 2012 R2 VM Templates

When you created VM templates out-of-the-box in System Center Virtual Machine Manager they get the en-US regional settings for all rolled-out VM´s and that in Sweden is not always standard for the IT departments and the IT techi-guy has to configure that manually afterward. This can be altered with either PowerShell or with an unattend.xml file.

If there happens to be some templates that you have not configured with the right regional settings and keyboard layout I have a small PowerShell script that will configure this for all templates in the VMM library.

Screen Shot 2014-04-14 at 18.53.39

Check out this KB2709539 article for more information and also your specific regional codes for your country :-)

Using MVMC 2.0 to migrate a VMware VM to Azure IaaS

This evening (in my timezone) Microsoft released the new version of the Microsoft Virtual Machine Converter 2.0 that has the functionality to also migrate VM´s to Azure in the wizard. I wanted to take that path for a spinn to test and see how that worked.

There are still some things to think about when using the tool,

  • it still uses ovf export
  • the VM in VMware is offline during the copy of the vmdk data (it creates a VHD for Azure, but if you choose a Hyper-V host you can set it to create a VHDX instead), this can with large amounts of data take some time and will consume space on the converter server.
  • The VM´s Windows OS has to be joined in a Active Directory domain, and the account being used has administrative rights in the VM to successfully uninstall VMware tools during conversion.
  • No EFI support, meaning that the VM´s in your vSphere has to be setup with BIOS to be able to convert (Windows 2012 and later is from a best practice in VMware configured with EFI), but UEFI support is only on VM´s i generation 2 and Azure does not have that, at least not yet..
  • Notice also that now with version 2.0 there is no support for migrating those Win 2003 VM´s

So how does it work in a migration from a VMware VM to Azure, well first of all in the wizard I select to migrate to Azure

Screen Shot 2014-04-08 at 22.10.53

Then I will add some information for the connection to my Azure subscription (yes I have done some editing in the image so not the whole world reading my blog would se my cert thumbprint and sub id)

Screen Shot 2014-04-08 at 22.11.02

After that I select what storage account I want the VHD to be transferred to (smart to think twice to select the storage account in the region where you have the network configured if you are using site 2 site vpn and such 😛 ).

Screen Shot 2014-04-08 at 22.11.50

Then I connect to either vCenter or an ESXi and select what VM I want to convert

Screen Shot 2014-04-08 at 22.12.40

After that I either use the already entered credentials or other and the state of the source VM for a successful VMware tools uninstall and as it is being migrated to Azure I do not get the option to select state of the destination VM (that can of course if used with the Azure PowerShell module and MVMC module be automated)

Screen Shot 2014-04-08 at 22.15.28

For the MVMC to succeed in its task to move the VM to Azure it has to store the VHD somewhere before moving it up to the cloud, the little caveat here is that it will create a fixed size vhd so bare that in mind when selecting the drive so you have space!

Screen Shot 2014-04-08 at 22.15.36

Then it´s time to kickoff the conversion

Screen Shot 2014-04-08 at 22.15.50

And as you can see in my vCenter the conversion is under its way

Screen Shot 2014-04-08 at 22.24.21

And then after some waiting the conversion and the upload to azure has completed,

Screen Shot 2014-04-08 at 23.10.40

Now I can enter the Azure management portal and create a VM and from the gallery select this disk disk_testmigrate_00_os.vhd , as the MVMC creates a disk pointer from the storage blob (the VHD) I do not need to do that part.

Screen Shot 2014-04-08 at 23.28.34

And then I can connect to the VM

Screen Shot 2014-04-08 at 23.36.13

Apparently I had some issues creating the VM as a Basic but using standard it worked nicely and as you can see I managed to get an RDP session to it.. So it was not lost in the cloud as in this Dilbert cartoon 😛


New version of the Microsoft Virtual Machine Converter 2.0 and MAT

Today Microsoft released the long awaited new version of the Virtual Machine Converter (the 1.0 version could be integrated with MAT but had limits in both VMware and Hyper-V latest releases). Microsoft has also released a new version of the MAT (migration automation toolkit) that supports the MVMC 2.0 to automate the migration!

Screen Shot 2014-04-08 at 19.20.57

New Features in MVMC 2.0

MVMC 2.0 release of MVMC includes the following new features:

    • Converts virtual disks that are attached to a VMware virtual machine to virtual hard disks (VHDs) that can be uploaded to Windows Azure.
    • Provides native Windows PowerShell capability that enables scripting and integration into IT automation workflows.
      Note The command-line interface (CLI) in MVMC 1.0 has been replaced by Windows PowerShell in MVMC 2.0.
    • Supports conversion and provisioning of Linux-based guest operating systems from VMware hosts to Hyper-V hosts.
    • Supports conversion of offline virtual machines.
    • Supports the new virtual hard disk format (VHDX) when converting and provisioning in Hyper-V in Windows Server® 2012 R2 and Windows Server 2012.
    • Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1, and VMware vSphere 4.1 hosts Hyper-V virtual machines.
    • Supports Windows Server® 2012 R2, Windows Server® 2012, and Windows® 8 as guest operating systems that you can select for conversion

in the link you can read more about the MVMC functionality

As you can see in the wizard the option to upload the converted VM to Azure directly has been added

Screen Shot 2014-04-08 at 19.21.50

And now in this version we have native PowerShell with the MVMC PS module as described above:

Screen Shot 2014-04-08 at 20.05.11

I will show more in a later post how it can be used and how it works with both migrations to Hyper-V and also directly to Azure :-)

both MVMC and MAT can be read about and downloaded here

testing the new Microsoft Azure Portal

Well as I am a techy nerd I have been checking out and following the Build keynote on Channel 9 and found that they now release the Microsoft Azure Portal, it is in Preview but it looks good! Just hope that this also soon comes to the Windows Azure Pack to the hosters

I have signed in at the and as you can see I get a good overview regarding my subscriptions and how the Azure current status is right now

Screen Shot 2014-04-03 at 19.33.29

right now in the preview I cannot handle my IaaS VM´s and networks yet :-(  but that will probably be updated soon I can think …

Automated PowerShell to keep your template vhd(x) IC updated

For the Veeam Seminar I did some digging in how to check and also apply updated integrational components on virtual disks in the System Center VMM library and found Ben´s script which I altered to fit my goal. This is quite convenient based on that you can schedule it and always have updated IC´s on those VHDX in the library.

I check and get the current IC´s from one Hyper-V host and thus based on that if it has been updated I also get that update instead of using a copied IC version locally in the VMM server. The script runs on the VMM server and that is why I use the Mount-DiskImage cmdlet instead of the Mount-VHD as that does not work on a non-hyper-V enabled windows server.

Screen Shot 2014-03-30 at 10.42.33