Transitioning Exchange 2007 environment to Exchange 2010
Exchange Server administration forum

ManU
Founder
Founder
Posts: 98
Joined: Sat Sep 26, 2009 9:57 am
Location: India

Transitioning Exchange 2007 environment to Exchange 2010

by ManU » Thu Jan 13, 2011 11:36 pm

images.jpg
images.jpg (6.24 KiB) Viewed 9057 times

I am hereby presented a working model of Transitioning of an Exchange 2007 environment to Exchange 2010
Hope this will help everybody for a rush in upgrading your current email system to the new EX2010.

Note:It is not supported to transition an internal Active Directory site before all your Internet-accessible sites have been transitioned. That is you must transition the "Internet Facing AD Site" associated with your external Autodiscover record, then regional Internet facing AD Sites, and then transition your internal Active Directory sites.

Introduction of Exchange 2010 into the environment:

1. Certificate Consideration: At first you will need a new commercial certificate. Microsoft recommends a certificate that supports Subject Alternative Names. You may also use a wildcard certificate.

There should be at least a minimum of three SAN values like

a. mail.yourdoamin.com (Primary OWA/EAS/OA URL)
b. autodiscover. yourdoamin.com
c. legacy.yourdoamin.com (your OWA/EAS namespace for legacy mailbox access)

Prior to Windows Vista SP1, the Windows RPC/HTTP client-side component required that the Subject Name (aka Common Name) on the certificate match the "Certificate Principal Name" configured for the Outlook Anywhere connection in the Outlook profile. Therefore, as a best practice, you should ensure that your mail.yourdomain.com is listed as the Subject Name in your certificate.

2. Service Pack Requirements: All Exchange 2007 CAS within the organization should be at Service Pack 2, all Exchange 2003 servers should be at Service Pack 2, all Exchange 2007 Mailbox, Hub Transport, and Unified Messaging servers are at Service Pack 2. Also be sure to meet all the forest/domain pre-requisites.

3. Installation and configuration of of CAS2010:

• During the installation of CAS2010 you have the option to enter the external namespace that will be used for the virtual directories. At this point enter the domain name of mail.mydomain.com
• Install the RPC over HTTP proxy component by
ServerManagerCmd tool: ServerManagerCmd.exe -i RPC-over-HTTP-proxy
• Configure your OWA settings (Authentication type: forms based authentication, basic authentication).
• Configure EAS authentication settings appropriately (Basic, certificate authentication).
• Enable Outlook Anywhere by :
Enable-OutlookAnywhere cmdlet

4. Ensure to enable the ExternalURLs for Autodiscover function:

•Offline Address Book: Set-OABVirtualDirectory cmdlet
•Web Services: Set-WebServicesVirtualDirectory cmdlet
•ActiveSync: Set-ActiveSyncVirtualDirectory cmdlet



5. Outlook Web Access functions URLs:

• Outlook Web Access: Set-OWAVirtualDirectory cmdlet
Set it separately for environments without Exchange 2003 mailbox servers and for environments with Exchange 2003 mailbox servers
Exchange Control Panel:
Set-ECPVirtualDirectory
cmdlet

6. "Non-Internet Facing AD Sites": If the Exchange 2007 is deployed in "Non-Internet Facing AD Sites" you must copy the Exchange 2007 OWA binaries to CAS2010:
• Navigate to \Client Access\OWA directory of CAS2007 server's
• Copy the highest version folder from the CAS2007 to CAS2010 Exchange binaries \Client Access\OWA directory
• Execute IISReset on CAS2010 machine.

7. Outlook Client Considerations: For your Outlook clients, configure CAS2010 to participate in an RPC Client Access Service array:

• Create a load balancing array for CAS2010
• Create a DNS entry in your internal DNS infrastructure that resolves to the Virtual IP Address of the CAS load balancing array for example outlook.mydomain.com.
• Configure your load balancing array to load balance the MAPI RPC ports:

o TCP 135
o UDP/TCP 1024-65535

• Run the following cmdlet to create the Client Access Service array:
New-ClientAccessArray -Name outlook.mydomain.com -FQDN outlook.mydomain.com -Site "Internet Facing AD Site"

8. HT2010 & MBX2010: Install the HT2010 and MBX2010 server roles into the "Internet Facing AD Site" and configure:
• You can change the Offline Address Book generation server and enable web distribution on CAS2010 by performing the following steps:

o To move the Offline Address Book: Move-OfflineAddressBook "Default Offline Address List" -Server
o To add CAS2010 as a web distribution point:
$OABVDir=Get-OABVirtualDirectory -Server
$OAB=Get-OfflineAddressBook "Default Offline Address List"
$OAB.VirtualDirectories += $OABVdir.DistinguishedName
Set-OfflineAddressBook "Default Offline Address List" -VirtualDirectories $OAB.VirtualDirectories


9. Legacy Host Record: Create legacy host record (legacy.contoso.com) in your external DNS infrastructure and associate it either with the CAS2007 infrastructure or your proxy infrastructure.

10. CAS 2007 URLs Re-configuring: Re-configure the following CAS2007 URLs in the "Internet Facing AD Site".:

o Outlook Web Access: Set-OWAVirtualDirecotry cmdlet
o Offline Address Book: Set-OABVirtualDirectory cmdlet
o Unified Messaging: Set-UMVirtualDirectory
o Web Services: Set-WebServicesVirtualDirectory
o ActiveSync: Set-ActiveSyncVirtualDirectory

•Disable Outlook Anywhere on your Exchange 2007 CAS infrastructure in the "Internet Facing AD Site" by utilizing the cmdlet, Disable-OutlookAnywhere

11. External Connectivity Re-configuring: Reconfigure External DNS and/or your reverse proxy infrastructure's publishing rules to have the autodiscover.mydomain.com and mail.mydomain.com namespaces point to CAS2010.

12. Testing: Test all client scenarios and ensure they function correctly.

"Configure and Migrate"

1. Public folder database replication:
Exchange Management console> Organisation Configuration > Mailbox > Database Management > New Public Folder Database > Give the database a name> Next > New > Finish.
The attachment 1.jpg is no longer available

Make it as the default mailbox database by right click on the mailbox database and select Properties > Client Settings > Browse > Select the new one > OK > and Apply.
The next step is to set up a replica of your public folders in the new database, to do this use the Toolbox > Public Folder Management console.
1.jpg
1.jpg (134.67 KiB) Viewed 9105 times

New Exchange 2010 has its own public folder database connects as default.
Right click "Public Folders" > Select "Connect to Server" > Browse to the Exchange 2007 server.
Select the Default Public Folders. Right click the first one and select Properties > Replication tab > Add > Add in the new server > OK > Uncheck "Use public folder data store replication schedule" and change the drop down to "Always run" > Apply > OK.

Note: If you have any Outlook 2003 clients you need to replicate the "SCHEDULE+ FREE BUSY" public folder.

Replication will be completed within few hours. Additionally we may try the following cmdlet too:
Update-PublicFolderHierarchy -Server

2. Change the SMTP feed
Change the SMTP feed from the old Exchange 2007 box to the new Exchange 2010 Server. For example,

i. Change the SMTP (TCP Port 25) Port redirect on your router/firewall address
ii. Swap IP addresses.
iii. Change the translation from public to private IP to point to the new IP.

3. Configure Send Connector:
Exchange Management Console > Organisation Configuration > Hub Transport > Send Connectors > Right click your send connector and select Properties > Source Server > Add > Add in the new server > Apply.

4. Moving Mailboxes:
I suggest testing it by moving one mailbox. Then test outbound/inbound mail flow, test mail flow internally from the mailbox to a mailbox that's still on the old server. Once found this works fine you may move the rest of the mailboxes.

EMC > "Recipient Configuration" > Mailbox > Right click the mailbox you want to move and Select "New Local Move Request".
3.jpg
3.jpg (133.5 KiB) Viewed 9105 times

At the introduction screen click the browse button and select your new servers data store > Next > Next > New > Finish

Once you have moved one and tested, it you can move the rest of the mailboxes.
Note: Outlook 2003 cannot connect to Exchange 2010, you need to turn on encryption before it will work. In Outlook Tools >Email Accounts > View or Change > Select the Exchange account > Change > More Settings > Security >check "Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server” > Apply > Restart Outlook.

5. Configure Offline Address Book
EMC>"Organization Configuration" > Mailbox > Select "Offline Address Book" tab > Right click the Default Offline address book and select "Move" > Browse > Select the new server > OK > Move > Finish.
4.jpg
4.jpg (146.82 KiB) Viewed 9105 times


6. Decommission and remove Exchange 2007
1.First check your Public folders are in sync. Remove replicas of public folder from 2007 server.
2.Delete the mailbox database(s) and Public folder from the old server.
3.Remove the old server from the source server list on the organization send connector
4.Control panel >Add remove programs>Select Exchange Server 2007 and uninstall all the roles including Management Tools
5.jpg
5.jpg (214.85 KiB) Viewed 9105 times


And wait for the complete successful removal as shown in the screen shot:
6.jpg
6.jpg (112.73 KiB) Viewed 9105 times
Thanks
MANU PHILIP
Microsoft MVP(Exchange Server)
| MCITP | MCTS | MCSA | ITIL V3 |
TechNet Forums Profile: ManU

jerry321
Rank1
Rank1
Posts: 2
Joined: Wed Aug 01, 2012 1:58 pm

Re: Transitioning Exchange 2007 environment to Exchange 2010

by jerry321 » Wed Aug 01, 2012 4:13 pm

Migration from one forest to another forest is really very time consuming process and require technical knowledge about complete process. You have simplifies the process of migration from Exchange 2007 to Exchange 2010 Server. Thanks for sharing !!

Users browsing this forum: No registered users and 1 guest

It is currently Mon Dec 11, 2017 11:24 am