Migration from VMware to Azure / Azure Local – Generex

Question

Can an existing RCCMD VMware Appliance be migrated from VMware/ESXi to Azure or Azure Local?

Short answer

Yes and no.

A direct migration of the existing RCCMD VMware Appliance to Azure or Azure Local is not possible. However, RCCMD itself can be used with Azure or Azure Local. To do this, RCCMD must be installed on a new Windows VM. Use the RCCMD Windows Installer and not the VMware Appliance.

Background

The existing RCCMD VM was provided for a VMware/ESXi environment. This is why VMware-specific options are also visible in the existing interface, such as settings for ESXi hosts, VMware VM management, or the behavior of virtual machines.

This VMware Appliance cannot simply be transferred 1:1 to Azure because Azure and Azure Local use a different VM management model. Therefore, the Appliance itself is not the correct installation method for Azure.

Important: This does not mean that RCCMD cannot be used with Azure. It only means that RCCMD is not operated in Azure as a VMware Appliance, but as a Windows installation on a newly created Windows VM.

No new license is required to switch RCCMD from VMware to Azure.

Azure VMs are managed via Azure or Microsoft management tools. For System Center Virtual Machine Manager, Microsoft describes that Azure VMs can be displayed via an Azure profile and managed with basic actions such as starting, stopping, shutting down, restarting, and connecting via RDP. (Manage Azure VMs)

Solution

1. Check the existing VMware Appliance

Document the current RCCMD configuration before switching:

existing RCCMD jobs
target systems
shutdown settings
network and notification settings
credentials and permissions
VMware/ESXi-specific settings

The VMware-specific settings cannot simply be transferred unchanged to Azure.

2. Create a new Windows VM in Azure / Azure Local

Create a new Windows VM in the Azure or Azure Local environment.

Make sure that the VM:

is permanently reachable,
has network access to the relevant target systems,
is not accidentally shut down too early in a shutdown sequence,
has appropriate firewall and network settings.

VM management is then performed via Azure, Azure Local, or System Center Virtual Machine Manager. In VMM, Azure VMs can be managed with basic actions such as starting, stopping, shutting down, restarting, and RDP. (Manage Azure VMs)

3. Use the RCCMD Windows Installer

Install RCCMD on the new Windows VM using the RCCMD Windows Installer.

4. Reconfigure RCCMD

Set up RCCMD again on the Windows VM.

Only transfer the functionally required settings from the old environment. VMware-specific settings that refer to ESXi hosts or VMware VM management must be adapted or replaced accordingly for Azure.

5. Test the function

After installation, check the following:

RCCMD service is running
RCCMD web interface is reachable
target systems are reachable
firewall and network rules are correct
configured jobs work
shutdown or notification processes have been tested

The old VMware Appliance should only be taken out of service after a successful test.

Summary

A direct migration of the existing RCCMD VMware Appliance to Azure or Azure Local is not possible.

However, RCCMD can still be used in Azure or Azure Local. To do this, a new Windows VM must be created and RCCMD must be installed there using the RCCMD Windows Installer. The Azure VM itself is then managed via Azure, Azure Local, or System Center Virtual Machine Manager.