but it worked in the staging environment...

Win2008 – Exchange 2007 move to new hardware – Part 3

PDT IT Services Blog Posts


In this “Part 3” of a 5-Series post, We will explain how to install an additional Exchange 2007 in an Exchange 2003 Organization, what settings/parameters you need to configure, how to move mailboxes,…

The following phases will be gone through:

a) Prerequisite steps before installing Exchange 2007

b) Exchange 2007 basic setup routine

c) How to move your mailbox objects between the old and new Exchange server

d) Take-over send/receive connector properties

Phase 1 : Prerequisite steps before installing Exchange 2007

Before Exchange 2007 can be installed on the server, the following components should be installed as a prerequisite:

1) IIS 7.0

2) .Net framework 3.0

3) Windows Powershell

The following screenshots detail the installation steps for all 3 components:

a) Add the Application Server Role from the Add Roles Wizard (Server Manager)


b) Make sure the .NET Framework3.0 components are also selected for installation


c) Select the “HTTP Activation” from the Windows Process Activation Service Support, as well as the Web Server Support


d) Make sure you select the IIS 6 Management Compatibility options as shown in below screenshot


e) Although it is not a requirement forl Exchange installation, I’ve created a good habit of installing the Telnet Client & Telnet Server components as well. These allow you to run telnet commands from within a command prompt. Always useful for troubleshooting SMTP connections between servers…


f) Finalize the installation by clicking Install; although it is not always mentioned, after the installation is completed, it is a good advise to reboot your server.

Phase 2 : Basic Exchange 2007 Installation Steps

In phase 2, the Exchange 2007 Server will be installed on the Windows 2008 server machine. This should be a quite easy step, as all Exchange Organization related information is already present in Active Directory (from the Exchange 2003 setup). If – during the first steps of the Exchange 2007 setup – a question should come up, asking for the Exchange 2007 Organization name, this means your ADPREP is not run correctly, or information is not yet replicated completely to all network segments.

a) Start the Exchange Setup from the installation files (setup.exe), or the autorun will show below startup window:


b) Select Step 4, after which the following introduction form will be shown:


c) Depending on your specific case, make appropriate selections; in our (and most default situations) a Typical Exchange Installation should be adequate.


d) Wait for the readiness checks to complete; if any error or warning message should be shown, solve those before continuing the installation procedure (eg. Hotfix update, servicepack, missing Windows components,…)


e) Click install to activate the installation of all different Exchange components. After about 20-30 minutes (depending on the hardware specs), your component installation should be completed with all green marks, as shown below


f) A final prompt is thrown to ask for a reboot:


g) After the reboot, start the Exchange System Manager Console; as long as your Exchange license key is not entered into the system, the following popup will appear everytime when you launch the ESM:


h) As you can see from the Exchange console, we are now running 2 Exchange 2007 Servers in our setup.


i) We can also manage the mailboxes in our organization. As a matter of fact, we will go through the necessary steps in moving those mailboxes from the “old” server to the fresh installed EX2007 in the next steps:


j) Select the individual mailboxes (you can also use shift for list selection or control for multi selection), and chose “Move Mailbox” from the Actions Pane or context menu


k) Click Browse... to select the target mailbox database store


l) Under normal situations, just Next would do the trick;


m) Select the timing for the move operation to execute, being immediately or on a scheduled time.


n) A summary screen is shown...


o) And the move operation will start as requested; During the move, the Outlook clients cannot connect to the individual mailbox, as it will be blocked for access. Once the move is complete, Outlook will automatically modify the profile to find its way to the new Exchange server.


p) Once completed, a Powershell script is shown for each mailbox; this can be handy when you want to learn how to bulk move mailboxes using Powershell.


q) The next step of configuration will be the Outgoing SMTP connector; from within the Exchange Manager / Organization Configuration / Hub transport / Send Connectors, there should already be a connector present (linked to our initial Exchange 2007 server). Using the properties settings / Source Server, we will specify the new setup machine.



r) Another step is needed to make sure our ESM will still work once the previous Exchange/Domain Controller machine is taken out of the network; we will modify the configuration domain controller; this is the DC which will be queried by Exchange 2007 to get all its configuration parameters. If this should not be modified, it might happen we can’t open the ESM anymore.

Under normal situations, restarting the Exchange 2007 Active Directory Topology Service or rebooting the server will make sure Exchange allocates the correct DC as well. But with the mentioned step, a service restart or full server reboot can be avoided. Nice for the availability statistics J




s) One of the last configuration steps to perform consists of modifying the “Receive Connector”, to make sure our Exchange Server is able to receive mail as well.

Go to Server Configuration / Hub Transport / Select new server / Default Receive Connector / Properties / Permission Groups



Add anonymous users – this will make sure foreign SMTP servers (which communicate as anonymous by default) can establish communication with each other.

Posted feb 14 2009, 03:30 by Peter De Tender


subject: exchange wrote Weekend reading
on 02-20-2009 20:33

Outlook Live screenshots: upon first glances Microsoft's Exchange 14 adds cross-browser support and

All content (c) its respective blog author.
Powered by Community Server (Commercial Edition), by Telligent Systems