What are perquisites?

 The Schema Master has to be Windows Server 2003 SP2 or later;

 The Global Catalog Servers need to be Windows Server 2003 SP2 or later;
 Active Directory needs to be running in at least “Windows Server 2003 Native mode” and it needs to be
in at least “Windows 2003 Forest Functional Level”.
 Exchange server 2007 SP2

The upgrade path

The upgrade path for the Inframan scenario is as follows:

1. Upgrade the Active Directory Schema;

2. Upgrade the Active Directory Forest Configuration;
3. Upgrade the Active Directory Domain(s) Configuration;
4. Install the combined Exchange 2010 CAS/HUB Servers;
5. Export certificate form HUB\CAS of exchange server 2007 and install on server
6. Install the new Exchange 2010 Mailbox Server;Move the access methods from Exchange 2007 CAS to
Exchange 2010 CAS;
7. Change the message flow from the Internet to the Exchange 2010 Hub Server;
i. Add SMTP route in MTA of exchange server 2010 Hub server
8. Move all resources from Exchange 2007 to Exchange 2010;
9. Install the Exchange 2010 Edge Transport Server;
10. Decommission Exchange Server 2007 from the Exchange organization

Active Directory Upgrades

1. setup.com /PrepareSchema:-
a. This command connect to DC schema master and update the schema according exchange server
2010 specific attributes
2. setup.com /PrepareAD
a. This command configure global Exchange objects in Active Directory such as.
b. It create the Exchange Universal Security Groups (USGs) in the root domain as well as prepare the
current domain.
c. This command creates the Exchange 2007 Administrative Group such as (FYDIBOHF23SPDLT)
3. setup.com /PrepareDomain (or /PrepareAllDomains
a. This command set permissions on the Domain container of Exchange Servers such as Exchange
Organization Administrators, Authenticated Users, and Exchange Mailbox Administrators
b. It create the Microsoft Exchange System Objects container if it does not exist

Changing the External Client Access

 If you’ve done this correctly, then when clients access the Exchange 2010 CAS Server
usinghttps://webmail.inframan.nl/owa, and their mailbox is still on Exchange Server 2007, they are silently
redirected tohttps://legacy.inframan.nl/owa, which is actually the Exchange 2007 CAS Server. This therefore
means that the current publishing rules on the TMG Server need to be changed as well for this upgrade to work:

1. The Unified Communications certificate has to include the legacy.inframan.nl FQDN. Instead of using a
new Unified Communications Certificate it is also possible to use a wildcard certificate, which is fully
supported in Exchange Server 2010.
2. The webmail.inframan.nl publishing rule needs to be changed to point to the new Exchange 2010 Client
Access Server;
3. The legacy.inframan.nl FQDN needs to be created, and it has to point to the Exchange 2007 Client
Access Server;
4. The autodiscover.inframan.nl publishing rule needs to be changed, and it has to be pointing to the
Exchange 2010 Client Access Server.

Change the External Client Access

In a coexistence scenario there are three Fully Qualified Domain Names (FQDN):

 Webmail.inframan.nl – this points to the external-facing Client Access Server, which is used for all
services (OWA, ActiveSync, Outlook Anywhere etc.). This is the current Exchange 2007 CAS Server,
but will soon be changed to the new Exchange 2010 CAS Server;
 Autodiscover.inframan.nl – this points to the external-facing Exchange 2007 CAS Server and, after the
change, it will point to the new Exchange 2010 CAS Server. Outlook 2007 (and higher) clients are able
to retrieve autodiscover information, even when their mailbox is still on Exchange 2007;
 Legacy.inframan.nl – this points to the old Exchange 2007 CAS Server after the switch to the
Exchange 2010 CAS Server. It is used for when OWA clients are redirected to the Exchange 2007 CAS
server because the user’s mailbox is still on Exchange 2007.

To prepare for the upcoming changes, we have to follow these steps, which we’ll cover in more detail in a
moment:

 Request a new SSL Certificate for the Exchange 2010 Client Access Server;
 Create a new rule on the TMG Server called “Legacy Inframan”, and publish OWA for Exchange 2007
using this publishing rule;
 Enable Outlook Anywhere on the Exchange 2010 Client Access Server;
 Move the Offline Address Book (OAB) and enable web-based distribution;
 Disable Outlook Anywhere on your Exchange 2007 Client Access Server;
 Reconfigure external DNS, and update the Publishing Rules on TMG.

Move offline address book

While the Exchange Management Console is still open, we can get started with moving the Offline Address Book
and enabling web-based distribution on the Exchange 2010 Client Access Server:
 4. Navigate to the Organization Configuration and click on Mailbox. In the results pane, select the Offline
Address Book tab;
5. Right–click on the Default Offline Address Book and select Move, using the Browse button to select
theExchange 2010 Mailbox Server. Click on Move again to continue. A warning message is displayed,
informing you that the files are copied to the new target server, at which point you can click on Finish to
end the wizard.
6. Right-click on the Default Offline Address Book again; select the property sheet, and then select
theDistribution tab, where the 2007 Client Access Server is still listed. Remove the old server, and
then clickAdd to add the Exchange 2010 Client Access Server as a distribution point. Finally, click
on OK to apply the changes and close the wizard.

The Offline Address Book is only generated once a day, by default at 4:00 am. So, when you are creating new
mailboxes, you have to be careful as they might not show up in this OAB until the next day! On the other hand,
the Client Access Server polls the Mailbox Server for updates on the OAB once every 480 minutes (8 hours). Be
aware of these issues when troubleshooting OAB issues.