:: infotechGuyz.com ::
> For the IT community by the IT community

• BlackBerry Server (BES)
• Excel Macro/VBA
• Exchange 2007
• Exchange 2010
• Lync 2010
• Scripting/Command-line
• SQL Server 2008
• SQL Server 2012
• Team Foundation Server
• VMware
• Windows 7
• Windows 8
• Windows Server 2008
• Windows Server 2012

Exchange 2003 to Exchange 2010

Below is an overview of Exchange 2003 to Exchange 2010 migration. When you're upgrading your current MS Exchange 2003 company to Exchange 2010, re's a age of time when both Exchange 2003 and Exchange 2010 will coexist within your company. This section discusses key points about both upgrade process and coexistence as y apply to Client Access, Transport, and Mailbox server roles.

High Level Overview
0. Ensure Exchange 2003 is running in Native mode.
1. Install CAS role
2. Add digital certificates on CAS
3. Enable Outlook Anywhere (optional)
4. Configure OAB and Web Services virtual directories
5. Install HUB role
6. Configure a legacy host name
7. Configure Exchange ActiveSync
8. Install UM server role (optional)
9. Install Mailbox server role
10. Change offline address book (OAB) generation server
11. Install Edge Transport server role (optional)
12. Move Internet mail flow from Exchange 2003 to Exchange 2010
13. Move Internet Mail Flow from Exchange 2003 to Exchange 2010
14. Move mailboxes from Exchange 2003 to Exchange 2010
15. Move public folder data from Exchange 2003 to Exchange 2010

Installing Exchange 2010 CAS in Exchange 2003 environment.

1. Install Exchange 2010 CASrole.
2. During Setup, you may enter primary external namespace for your virtual directories. This value should be primary host name that your users use to connect to Exchange services from Internet, for example: mail.companyA.com.
• If you're upgrading through graphical user interface Setup experience, you'll be prompted to configure an external Client Access domain.
• If you're upgrading from a command prompt, use setup property /ExternalCASServerDomain and specify your domain, for example: mail.companyA.com.
3. If your organization requires Outlook Anywhere access, enable Outlook Anywhere.
• This may be done using following command: Enable-OutlookAnywhere -Server:<CAS2010> -ExternalHostName:mail.companyA.com -SSLOffloading $false
4. If you didn't configure a primary external namespace during setup, you'll have to run following commands to configure virtual directories for Offline Address Book, EWS, Exchange ActiveSync, Outlook Web App, and Exchange Control Panel. You may do that with following commands:
a. Offline Address Book: Set-OABVirtualDirectory <CAS2010>\OAB* -ExternalURL https://mail.companyA.com/OAB
b. Web Services: Set-WebServicesVirtualDirectory <CAS2010>\EWS* -ExternalURL https://mail.companyA.com/ews/exchange.asmx
c. Exchange ActiveSync: Set-ActiveSyncVirtualDirectory -Identity <CAS2010>\Microsoft-Server-ActiveSync -ExternalURL https://mail.companyA.com
d. Outlook Web App:Set-OWAVirtualDirectory <CAS2010>\OWA* -ExternalURL https://mail.companyA.com/OWA
e. Exchange Control Panel: Set-ECPVirtualDirectory <CAS2010>\ECP* -ExternalURL https://mail.companyA.com/ECP
5. Configure Exchange 2003 URL property on /owa virtual directory. This is necessary for Exchange 2003 and Exchange 2010 to coexist. To configure this property, use following command.
• Set-OWAVirtualDirectory <CAS2010>\OWA* -Exchange2003URL https://legacy.companyA.com/exchange
6. Change Offline Address Book generation server and enable web distribution on Exchange 2010 CASusing following steps:
. Move Offline Address Book using following command: Move-OfflineAddressBook "Default Offline Address List" -Server <MBX2010>
a. Add Exchange 2010 CASas a web distribution point using following commands:
• $OABVDir=Get-OABVirtualDirectory -Server <CAS2010>
• $OAB=Get-OfflineAddressBook "Default Offline Address List"
• $OAB.VirtualDirectories += $OABVdir.DistinguishedName
• Set-OfflineAddressBook "Default Offline Address List" -VirtualDirectories $OAB.VirtualDirectories
7. Enable Integrated Windows auntication on Microsoft-Server-ActiveSync virtual directory on Exchange 2003 back-end server. This allows Exchange 2010 CASand Exchange 2003 back-end server to communicate using Kerberos auntication.

Email routing from Exchange 2003 to Exchange 2010

Typically, routing groups are used to specify a set of well-connected Exchanges. Servers in same routing group can communicate with each or without use of connectors. Ideally, routing groups defined in your existing environment are based on IP subnets and closely mirror AD site configuration.
When more than one routing group is defined in an Exchange 2003 organization, you must manually create routing group connectors to enable mail flow between Exchange 2003 servers in different routing groups. routing group connector must specify a source server and a target server as connector endpoints. A routing group connector defines a one-way connection, and a reciprocal connector must be created to establish mail flow in both directions. source and target servers are bridgehead servers for routing group. bridgehead servers relay e-mail to or routing groups on behalf of or servers in ir routing group and receive e-mail from or routing groups for delivery to or servers in ir routing group.
In Exchange 2010, you don't have to define an Exchange-specific routing configuration. Exchange 2010 uses existing AD site topology to define its routing topology. However, you can make Exchange-specific configuration changes to AD sites and IP site link costs to control mail flow. E-mail routed to Exchanges located in different sites must be relayed by Hub Transport servers. Hub Transport servers send e-mail to Hub Transport servers in remote sites by using intra-organization Send connector. intra-organization Send connector is an implicit connector computed by using AD site and IP site link information

Move Mailboxes from Exchange 2003 to Exchange 2010

Moving mailboxes from Microsoft Exchange 2003 Service Pack 2 (SP2) or later to Exchange 2010? Please keep following in mind:
• move process is performed offline, and end-users won't be able to access ir mailboxes during move.
• Perform move from a server running Exchange 2010 by using move request cmdlets in Exchange Management Shell. You can't use Exchange System Manager on an Exchange 2003 server to move mailboxes.
• You can't move mailboxes from Exchange 2003 Service Pack 1 (SP1) or earlier.
• Exchange 2003 doesn't have resource mailboxes. Instead, you must use shared mailboxes to represent resources. If you move a shared mailbox from Exchange 2003 to Exchange 2010, move request creates mailbox as a shared Exchange 2010 mailbox. After you move mailbox to Exchange 2010, you can convert it to a resource mailbox.