Ranj B Technical Blog

Transition from Exchange 2007 to 2010 Enterprise

Home  >>  Microsoft Exchange  >>  Transition from Exchange 2007 to 2010 Enterprise

Transition from Exchange 2007 to 2010 Enterprise

On August 14, 2014, Posted by , In Microsoft Exchange, With No Comments

I have used Windows 2008 R2 Enterprise 64-bit.

Install Windows

Join Machine to Domain and setup Static Networking

Ensure machine can ping rest of the network, check AD to ensure server is in the directory.

Open up Powershell:

Type following:

1. import-module servermanager – this will import a module for the rest of the Powershell commands to run.

2. Login to Technet website which will show you pre-requisites to install.Website: http://technet.microsoft.com/en-us/library/bb691354.aspx

3. Choose pre-requisites depending on Server version. I chose 2008 R2 so went to that section.

4. Install Microsoft Office Filter Pack

5. The next step is based on 1 exchange server which will house all the main roles. Choose the Powershell script depending on if you want the VOIP and unified messenging capabilities:

Typical installation of the Client Access, Hub Transport, and Mailbox server roles:-

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,
Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,
Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,
Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,
RPC-Over-HTTP-Proxy -Restart
For installation with the Client Access, Hub Transport, Unified messenging and
Mailbox server roles:-

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,
Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,
WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,
Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy,
Desktop-Experience -Restart

6. Next there is a service which needs to be started up automatically from now on.
Its called the NetTCPPortSharing Service. You can either go to services.msc to
do this or even better do it in Powershell. The command is:

Set-Service NetTcpPortSharing -StartupType Automatic

7. Now we need to prep up AD and the rest of the domain. We need to update the

AD Schema. This will add extra objects into AD. Again we can use CLI for this.

Setup /PrepareAD or setup /p. Need to wait depending on how big the AD

infrastructure is for replication purposes. Best to Perform on Primary AD and

FSMO role server especially in small environment. Need to ensure Powershell V2

is installed.

Then need to prepare the domain, so again on the DC run the following command

after AD is prepared. Run setup /pad or setup /PrepareALLDomains

8. Run the exchange setup on the new Exchange 2010 server, if its a co-existence

with an Exchange 2007 Server you need to ensure first that at least SP2 is

installed otherwise the setup will fail.

Leave a Reply

Your email address will not be published. Required fields are marked *