Some clarifications first...
During my previous (staged) migration, I had performed several crucial tasks:
Created an Office 365 tenant with Microsoft.
Added my domain mitserv.net to the tenant.
Created the DNS record that validates my ownership of the domain.
Important note: in my case, DirSync was already activated in Office 365 (for the previous migration) and I will leave it in that state. However, in a hybrid migration we install and configure ADFS first and then (and only then) DirSync. If you have no existing Office 365 tenant, or have just created one, you can leave DirSync unactivated for the time being.
Here is a partial list of tasks that I will perform in my next blog posts:
- Install server (Windows 2012 R2 - this has been completed - I will not demonstrate, step by step, how to install Windows 2012).
- Install certificate
- Install the ADFS role. Note: with Windows 2012 R2, the version of ADFS is 3.0.
- Convert domain to federated domain
Load balancing for ADFS
- Download a template for ADFS from the KEMP Technologies website.
- Configure the VLM-200 for ADFS
- Build a server for DirSync (this has been completed - I will not show how to install Windows server)
- Install DirSync
- Activate DirSync in the Office 365 tenant (this has been completed - I will show the reader where this is configured this however.