Since Microsoft announced HMC was being retired, we have had an increasing number of questions around migration, the most common one being, I use HMC, How can we move from our HMC Control Panel to Cortex?
Migration is never straightforward, however the good news about HMC is that it automated provisioning - which makes migration somewhat easier. At Cortex we've been migrating users onto the platform for some time, and in a number of cases we've had to deal with a beast uglier and more complex than HMC.... yes, the "Manomatic" provisioning system - a home made system that has typically been through several unpleasant and painful levels of evolution. Often, by the time we're involved we're fighting to tame a three headed monster.
The problem with manual provisioning is:
(a) Humans aren't very good at repetitive tasks, they forget things and don't follow instructions well.
(b) After the first couple of times, manual provisioning gets kind of boring, so corners get cut.
(c) Smart engineers delegate the task to a trainee - who gets lost and makes more mistakes.
So in conclusion - automagic provisioning is the way to go, and if you've already been using HMC the migration process once proven, can be easily repeated across all of your hosted customers. (we've also done lots of them, which makes it easier)
HMC Control Panel Migration Process
HMC stores it's user and service information in Active Directory and in a small SQL database. In order to ensure best accuracy of data, Cortex tries to base the core migration from the Active Directory.
1. Extract user data from AD
We use LDIFDE to make a quick extract of the directory into a text file. This separation means that we can use the same process for moving users from one directory to another.
2. Import data into the Cortex migration tool
The file is loaded into the migration tool - this can then be used to identify resellers, customers and users.
3. Determine services provisioned to users
As the file is parsed, much information about the user and their HMC services can be gathered from the AD data. This is used to determine the appropriate Cortex plan for each user.
4. Determine services provisioned to customers
By determining which services a user has consumed, we can determine which services and plans a customer should have... and similar for the reseller.
5. Provision
Provisioning sends requests to the Cortex API, the customers, users and services are provisioned into Cortex, the end result is users that can be managed with Cortex.
Minimising impact on the end-user
Provided migration tools are configured correctly and good sample tests are completed, the migration should not affect the end-users consumed service in any way. The biggest impact is in the change of control panel and in communicating this well to your end users.
Labels: HMC, HMC Control Panel, Hosted Exchange