Tag: vCenter

VMware on Azure - Azure VMware Solutions

Run your VMware natively on Azure with Azure VMware Solutions

Today the Microsoft Azure team announced the Azure VMware Solutions, which allow you to run VMware natively on Azure. VMware Solution on Azure by CloudSimple is a fully managed service that lets you run the VMware platform in Azure. This solution includes vSphere, vCenter, vSAN, NSX-T, and similar tools. VMware environment runs natively on Azure Bare Metal infrastructure, on Azure cloud locations. The service includes all the features required to consume the VMware platforms efficiently and securely. The solution is delivered by Microsoft, verified by VMware, and run on Azure infrastructure.

This allows you to move or extend your on-premises VMware environment to Microsoft Azure. You can seamlessly move VMware workloads to Azure and integrate with your VMware management environment, using the same and existing management tools. This gives you time to modernize your workloads with native Azure services. This extends the Microsoft hybrid cloud offerings for products like Azure Stack, Azure Stack HCI, and more.

VMware Solution on Azure by CloudSimple

VMware on Azure - Azure VMware Solutions


  • On-demand self-service provisioning of VMware cloud environments. Ability to add and remove capacity on demand
  • VMware platform deployment, upgrade, management plane backup, health/capacity monitoring, alerting, troubleshooting, and remediation.
  • Underlay networking services required to enable VMware, including L2/L3 services and firewall rule management.
  • Edge-type networking services, including VPN, Public IP, and Internet Gateways. These edge services run on Azure and carry the corresponding security and DDoS protection of Azure.
  • Capacity reservation to lower costs.
  • High-speed, low-latency connectivity to Azure and on-premises.
  • Solution architectures for customers to consume Azure services in an integrated fashion, take advantage of this unique “VMware cloud in a public cloud” architecture. These Azure services include Azure AD, storage,
  • application gateways, and others.
  • Infrastructure is fully dedicated to you and is physically isolated from the infrastructure of other customers.
  • Management features such as activity management, usage, billing/metering, and user management.
  • 24×7 customer support.

(Source Microsoft Docs)

This will open a couple of crucial scenarios for our customers.

  • Data Center retirement or migration – If you need to retire your datacenter and you need a fast and straightforward way to move your existing VMware workloads, Azure is a great place to host these workloads without rearchitecting them. This will give you time to modernize your applications in the mid and long term
  • Expansion on demand – If you are running your VMware environment and you need more capacity on demand, you can extend it to Azure.
  • Disaster Recovery – You can use Azure as your recovery site for your on-premises VMware workloads
  • Virtual Desktops – If you are running a VDI solution on top of VMware, you are also able to host the infrastructure in Azure.
  • Hosting High-Performance Applications – The CloudSimple solution provides a hyper-converged architecture designed to run high-performance workloads
  • Hybrid Cloud – It opens up scenarios for companies to run hybrid cloud scenarios, without the need to switch all your tools and to rearchitect your workloads

If you want to know more about VMware Solution on Azure by CloudSimple, you can check out the Microsoft docs.

Integration into Azure

Create VM in the Azure Portal

The VMware solutions on Azure, are not just isolated from the rest of your Azure environment. VMware on Azure by CloudSimple is integrated into Azure, which means it allows you to leverage Azure Express Route and even the Azure Resource Manager to deploy virtual machines on your VMware host running in Azure. This will enable you to create new virtual machines from your VMware administration tools like vCenter, but also within the Azure Portal or using Azure Resource Manager templates.


In terms of pricing, you will be paying per VMware node in Azure, and you will get charged by Microsoft for it. You can use your existing Azure Enterprise Agreement precommitments for it.

We have two different instances available depending on the size you need, the CS28 and the larger CS36 nodes. These include CPU cores, RAM, NVME Cache, and useable all-flash storage. The minimum of nodes you will need is three instances per cluster. You can also make use of the Reserved options for 1 or 3 years to save up to 50%. You can also use the Azure Hybrid Benefit to use your existing Windows Server licenses, and you can also make use of the Extended Security Update options for Windows Server 2008 / 2008 R2 and SQL Server 2008 / 2008 R2.

Azure CloudSimple Pricing

The storage pricing is the useable storage in vSAN. If you want to know more about pricing, check out the Azure pricing page for Azure VMware Solution by CloudSimple.

What are your thoughts about these announcements? Let me know in the comments!

System Center 2012 SP1 – Virtual Machine Manager support for VMware vSphere ESX Hosts

System Center Logo

As System Center 2012 SP1 was released, it officially supported VMware vSphere 4.1 and 5.1, there was no support for vSphere 5.0 in SCVMM 2012 SP1. Now since a lot of customer have requested this feature, Microsoft added VMware vSphere 5.0 to the supported list of vSphere versions. For those who didn’t know that, to manage VMware ESX Hosts you need a version of vCenter. Some months ago I made a blog post about how you can add your VMware infrastructure to Virtual Machine Manager.

Virtual Machine Manager now supports the following versions of VMware vSphere:

vCenter Server:

For System Center 2012 – Virtual Machine Manager:

  • VMware vCenter Server 4.1

For VMM in System Center 2012 SP1:

  • VMware vCenter Server 4.1
  • VMware vCenter Server 5.0
  • VMware vCenter Server 5.1

Virtual machine hosts and host clusters that run any of the following versions of VMware:

For System Center 2012 – Virtual Machine Manager:

  • ESXi 4.1
  • ESX 4.1
  • ESXi 3.5
  • ESX 3.5

For VMM in System Center 2012 SP1:

  • ESXi 5.0
  • ESXi 5.1
  • ESXi 4.1
  • ESX 4.1

Get more information here: System Requirements: VMware ESX Hosts and here: System Requirements for System Center 2012 SP1.


How to add VMware vSphere in SCVMM

System Center Logo

For my diploma thesis about moving virtual machines from VMware vSphere to Microsoft Hyper-V I have tested the virtual-to-virtual converter in System Center 2012 Virtual Machine Manager. First I had to integrate the VMware vSphere infrastructure in Virtual Machine Manager. SCVMM does not only allow you to manage Hyper-V hosts, it is possible to integrate and manage VMware vSphere Hypervisor hosts (also known as ESX or ESXi) and Citrix XEN Server hosts. If you want to manage VMware hosts you have to integrate VMware vCenter before you can add the VMware hosts. You cannot manage standalone VMware hosts which are not integrated in a vCenter environment with SCVMM:

System Center 2012 Virtual Machine Manager does support the following VMware vSphere versions (System Requirements: VMware ESX Hosts):

  • VMware vCenter Server 4.1
  • Virtual machine hosts and host clusters running any of the following versions of VMware:
    • ESX or ESXi 4.1
    • ESX or ESXi 3.5

For my diploma thesis I used System Center 2012 SP1 CTP2 and there is no official information about this, but CTP2 of Service Pack 1 for System Center 2012 Virtual Machine Manager works also with VMware vCenter Server 5.0 and ESXi 5.0 (or VMware vSphere Hypervisor 5.0).

Now to manage or convert the VMware infrastructure with SCVMM you have to do the following steps.

  1. Add VMware vCenter Server to SCVMM
  2. Add VMware vSphere Hypervisor hosts to SCVMM
  3. Connect Management

Add VMware vCenter Server to SCVMM

In the Fabric section, click on Add Resources and choose VMware vCenter Server.

Specify the VMware vCenter Server that you want to add.

Import ant trust the certificate from the vCenter Server

Add VMware vSphere Hypervisor/ESX hosts to SCVMM

After your VMware vCenter hosts is added to your Virtual Machine Manager infrastructure you have to add the VMware vSphere Hypervisor/ESX hosts. For this click on Add Resources and choose VMware ESX Hosts and Clusters.

Choose a Run As account which has access to the ESX hosts.

Choose the ESX hosts from your vCenter infrastructure.

Choose the host group where the VMware ESX hosts will be assigned to.

After you have added the VMware vSphere Hypervisor hosts to your environment you have to import and trust the certificate of the ESX host. To do this open the properties of a ESX host and select the management section. Here click on Retrieve and select Accept the certificate from this host checkbox.

Now you can manage your VMware vSphere infrastructure in System Center Virtual Machine Manager.

VMware VirtualCenter Server service does not start automatically after reboot

We had a problem with our VMware VirtualCenter Server service which did not start automatically after a server reboot. This could be a problem when the VMware VirtualCenter Server service starts before the MSSQL Server.

Now the solution to solve this problem is to add a dependency to the VMware VirtualCenter Server service.

The VirtualCenter Server service is dependent on the following services:

  • SQL Services
  • ADAM Services (when using linked mode in vCenter Server 4.x)

How to create a service dependency:

  1. Open the services.msc
  2. Check out the name of the service you want to add as dependency
  3. open the Registry Editor (regedit)
  4. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd
  5. Double-click the DependOnService key and add the Service name using the name of the Service in our case MSSQLSERVER
  6. In the Services window, open the service properties for the service VMware VirtualCenter Server.
  7. In the Dependencies tab, verify the VMware VirtualCenter service is listed as depending on the service.

In Windows Server 2008 or later you could also set VMware VirtualCenter Server service to startup type Automatic (Delay):

  1. Click Start > Run, type services.msc, and click OK.
  2. Right-click on the VMware VirtualCenter Server service and click Properties.
  3. Change the startup type from Automatic to Automatic (Delay).

More Information on this: VMware KB