The Migration of Exchange 5.5 to 2003 Server
Electronic messaging services within a company remains a mission critical application and its implementation is a vital part to the conduct of everyday business strategies, needs and goals. Within the organization the business requirements now include the safeguard of electronic content retention best practices. Therefore, it is important to see to it that a migration project is undertaken with a lot of care. Read this document carefully to gain a good understanding of not only the pre-requisites but also the migration path from mixed to native mode.
The delivery of mail is a challenging task which includes the support of thousand of users within the corporation environment. The new infrastructure must set up procedures to respect compliance, corporate governance and internal regulatory policy enforcement. Affirmatively, business guidelines and principles for the preservation of electronic mail within the corporate body must now be taken into consideration. This requires that companies learn how to standardize their projects to meet not only corporate needs but also judicial demands.
The granularity of server management depends upon a business model that will sustain the rationalization of all of the mechanics of the migration project from Exchange 5.5 to Exchange 2003. It is understood that the migration will introduce many changes upon the business model. It is to be undertaken by keeping the infrastructure model and design flexible without the impairment of performance.
SETUP PROCEDURES FOR THE MIGRATION:
MANAGING THE MIGRATION:
o Domain controller location. You’ll need at least one Domain Controller in each office that has an Exchange 2003 server
o Global Catalog server location. Need at least one Global Catalog server in each office that has an Exchange 2003 server. This can also act as the local Domain Controller. The simplest way to accomplish this is to make all branch office DCs into GCs. Microsoft recommends a minimum of one GC server for every four Exchange processors, not servers.
o DNS configuration. Make certain that DNSLint shows no errors, other recommended tool KILLADCGN.EXE to verify chkds Checkdisk and chkdsro (CheckReplicationOrphan objects in AD);
o Active Directory Native Mode. Important Notice: The Active Directory domain containing the Exchange servers must be in Native Mode so that you can use Universal Security Groups for e-mail distribution.
o Replication or authentication problems. Verify Event Viewer to have no errors from directory service replication, KCC topology calculations, or authentication errors originating from domain controller accounts. You can use the EventCombMT utility (download from Microsoft). EventCombMT is part of the Account Lockout and Management and Lockout
o Domain Prerequisites Considerations : Name Resolution, ADC Staging OU, ADC Staging, Verify trusts issues, Replication topology
Verify Current Exchange Organization Roles and Distributions:
O Exchange server version
O Site configuration
O Site connectors and Directory Replication connectors
O Internet connectors
O Unsupported connectors
O Key Management Services
O Compatible backup
O Antivirus and Antispam software
O E-mail dependent applications
O Exchange 2000 instant messaging
Pre-Requisites and Precautions before the installation:
o Security patches (ISDS for Exchange)
o In order to preserve Exchange 5.5 Public Folder Access Control Lists (ACLs) after mailboxes or distribution lists are moved between sites the Administrator will need to install an Exchange 5.5 DS/IS hotfix (http://support.microsoft.com/?kbid=836489) on every Exchange 5.5 Public Folder server prior to moving mailboxes or DLs between sites.
o The Consistency Adjuster must be run for each server in each site.
o Windows service packs (SP4.0 for Exchange 5.5 while Exchange 2003 is on SP2.0 this information must be revised on the website of Microsoft for the latest updates)
Article Source: http://EzineArticles.com/1160278