Apologies for not having posted for quiet some time but I have been transitioning a new client into the company that I work for’s managed service offering.
Documenting and auditing an infrastructure of 100 odd physical server ranging in age from 3-6 years covering 12 locations and 2 AD forests took a little bit of my time for a couple of months.
So now that is over I am back to my regular job and on to my first few Exchange 2010 migrations.
I am going to run you through how to get Exchange 2010 installed in your environment and migrate your mailboxes from an Exchange 2007 server to an Exchange 2010 environment today. Please note this will not cover DAG’s (Database Availability Groups) I will be covering that is great detail in a future post.
So lets get started.
On the source server we need to make sure the following prerequisites are completed before installing Exchange 2010 into the environment.
1) Exchange 2007 SP2 must be installed on source server.
If you have more than 1 Exchange 2007 server you must have SP2 installed on all CAS servers in Organisation and installed on all Exchange 2007 servers in the same AD site as the one that you are planning on placing your Exchange 2010 server.
2) Other than all the current Windows Updates, you need to install Windows Installer 4.5 (found
here)
If installing Exchange 2010 on Windows 2008 you also need to install SP2 and the following
- Install Microsoft .NET Framework 3.5 Service Pack 1 (SP1). For details, see Microsoft .NET Framework 3.5 SP1.
- Install the Microsoft .NET Framework 3.5 Family Update for Windows Vista x64, and Windows Server 2008 x64 updates. For details, see Microsoft .NET Framework 3.5 Family Update for Windows Vista x64, and Windows Server 2008 x64. See also Microsoft Knowledge Base article 959209, An update for the .NET Framework 3.5 Service Pack 1 is available.
- Install Windows Remote Management (WinRM) 2.0 and Windows PowerShell V2 (Windows6.0-KB968930.msu). For details, see Windows Management Framework.
- On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.
To install all the OS pre-requisites follow the technet guide
here. Just a note: when using the built in Exchange XML files for Server Manager you need to add the path to the files; so your command will look something like this
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip z:\scripts\Exchange-Typical.xml –Restart
Where Z is the location of the source files.
After all the OS pre-requisites are done installing and the server has finished its reboot. you can either proceed with the GUI install or the command line install.
My personal preference is to use the command line.
So from the command prompt (it will need to be run as Administrator)
Start with the AD modifications
setup.com /preparead
After this completes you will need to actually install Exchange.
For a server holding CAS, Mailbox and Hub Transport roles issue the following command
setup.com /m:Install /r:M,H,C
If you have update rollups and wish to incorporate that into your installation and the following switch
/UpdatesDir:“c:\ExchangeUpdates“
The contents of the update folder must be a .msp or update.exe.
The GUI installation is pretty much a next, next finish affair with the one exception of being asked if the CAS role will be Internet facing and if so what the external address will be.
If you are installing Exchange 2010 into an environment comprised of Exchange 2003 you will need to specify the server that you wish to create a Routing Group connector with.
On the Exchange 2003 server if you use a smart host for outbound mail make sure that the smart host is set on the SMTP connector NOT the Default SMTP Virtual Server as this will cause mail flow problems.
That wraps it up for this part.
I’ll go through moving mailboxes next
Posts
