With Exchange 2010 available on MSDN I decided to take the risk and jump straight into a migration as the only thing as fun as a well planned migration is shooting from the hip on full auto.




Exchange 2010 cannot co-exist with Exchange 2007 unless it is SP2. The Exchange 2007 SP2 install was exceptionally pain free (It was so easy I may not sleep properly tonight) and with that done it was time to start preparing my new Exchange 2010 server.

A base copy of Windows Server 2008 (non R2) will have the following pre-requisites;

.Net 3.5 (SP1)
PowerShell 2.0
Office 2007 System Converter Filter Pack

Once these are installed you will need to wield ServerManagerCmd and get some other things installed;

ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i Web-Net-Ext
ServerManagerCmd -i NET-WIN-CFAC

This went exceptionally smoothly and then it was time to run the Exchange 2010 setup.

Unfortunately it threw an error regarding the Net.Tcp Port Sharing service needing to be set to automatic;



















To fix this just set the service to auto start;
sc config NetTcpPortSharing start= auto

A quick retry of the Readiness checks came back with a clean bill of health and we are good to go!

Just over half an hour later Exchange 2010 is installed and ready to go!



















Since my last post regarding Exchange I’ve been using the Active Directory Certification Services to handle all my SSL stuff which worked lovely with IIS7 and Exchange 2010 so there was no need to do any of the crazy private key recovery stuff as we did with Exchange 2007.

A full install and even a test mailbox migration in just over an hour, not bad.