TechShizz | All posts tagged 'Migration'

Office 365 Migrations

Cut over Staged Hybrid IMAP
Exchange Versions 2003 and later 2003 / 2007 2010 / 2013 2000 Onward
Pros Simple Greater than 2000 users More time (no down time) Migrate legacy mailboxes
Cons Max 2000 Users Coexistence Requires Hybrid Exchange Wizard Only Inbox Migrated
Cons Max 2000 Users Coexistence Requires Hybrid Exchange Wizard

Cut over Migration

A cut over migration is a "all at once" method of migrating.

Outlook anywhere (HTTP over RPC) AKA Auto discover
SSL Certificates
Custom domain added to Office 365 tenant account

Preparing the Cut over Migration

If Outlook anywhere / auto discover is already configured, skip to step 7.

1. Create a Custom certificate request
Template: (No Template) Legacy Key
PKCS #10

Certificate Name: Outlook Anywhere
Common name:
Enter an Alternative DNS: and
Extended Key Language: Server Authentication
Key Type: Exchange
Key Size: 2048
Make Key Exportable

Save CSR as Base64.

2. Submit the CSR to a public CA. Once it's received, import the certificate

3. Export the certificate
Export Private key: yes
PKCS #12
Save the certificate to the exchange server

4. Check firewall for required ports
HTTPS: 443

5. Create DNS Records (CNAMEs)
6. Import the Certificate into Exchange
Open IIS
Locate the OWA Site
Assign the certificate to the https bindings.

7. Test exchange connectivity 

Executing the Migration

1. Ensure the on-premises account has correct permissions

2. Add the domain to Office 365
Only step 1 is required for this process there is no need to add licences yet as there are no accounts in Office 365 to assign them to.

3. On the on-Premises exchange, go to Migration
Select cut over migration
Enter credentials of the administrator
Enter the exchange server: exchange.ADDomain.local
Enter the RPC Proxy:
Name the Migration Batch: Batch 1
The batch will then run.

4. Change the MX Records to point to Office 365

5. Disable Synchronization and delete batch on the local exchange

6. Decommission Server

Guide to continue...

Migrating Server Roles

This guide will demonstrate how to migrate a role from one server to another; for this example we will migrate DHCP but this method can be amended to suit other roles. You should always follow Microsoft's guides and checklists when migrating roles.

On source machine
Create a shared folder on the source machine called "Mig"

On destination machine
Next if not already, intsall Windows Server Migration Tools

Import-Module ServerManager
Add-WindowsFeature Migration

Cd \
cd C:\windows\System32\ServerMigrationTools\

smigdeploy.exe /package /architecture amd64 /os WS08 /path \\sourceserver\Mig

On source machine
cd c:\Mig\<folder-name of your deployment>


Before continuing
Make sure the role being migrated is Installed on the destination server.
Make a note of the source NIC MAC address = getmacgetmac

Stop Service on Destinartion server
Stop-Serve DHCP
Check with that it stopped with:
Get-Service DHCP

Export-SmigServerSetting -FeatureID DHCP -Group -IPConfig -path C:\StorageMig -verbose
Prompted with a password.

Remove DHCP from AD

netsh DHCP delete server.domain.local

On Destination server

We must import the snapin before we can use the Import-SmigServerSetting cmdlet.


Import-Smigserversetting -FeatureID DHCP -IPConfig ALL -SourcePhysicalAddress <M-A-C-A-D-D-R-E-S-S> -TargetPhysicalAddress <M-A-C-A-D-D-R-E-S-S> -Path \\sourceserver\c$\StorageMig -Verbose

Start-Service DHCP
netsh DHCP add server newserver.domain.local