The Migration of Exchange 5.5 to 2003 Server

OBJECTIVE:

Electronic messaging services within a business enterprise remains a undertaking important software and its implementation is a vital part to the behavior of normal business techniques, desires and goals. Within the organisation the business necessities now include the protect of digital content material retention satisfactory practices. Therefore, it’s miles vital to peer to it that a migration task is undertaken with a number of care. Read this document cautiously to advantage a good understanding of not simplest the pre-standards but also the migration course from blended to native mode.

The shipping of mail is a hard challenge which incorporates the guide of thousand of users inside the organisation environment. The new infrastructure should installation procedures to admire compliance, corporate governance and internal regulatory coverage enforcement. Affirmatively, enterprise hints and concepts for the renovation of email in the company body have to now be taken into consideration. This requires that groups discover ways to standardize their initiatives to fulfill no longer simplest company wishes however additionally judicial demands.

The granularity of server management relies upon upon a business model with the intention to preserve the explanation of all of the mechanics of the migration mission from Exchange 5.Five to Exchange 2003. It is known that the migration will introduce many modifications upon the enterprise version. It is to be undertaken via maintaining the infrastructure version and design bendy with out the impairment of performance.

SETUP PROCEDURES FOR THE MIGRATION:

MANAGING THE MIGRATION:

o Domain controller vicinity. You’ll need at the least one Domain Controller in every workplace that has an Exchange 2003 server

o Global Catalog server region. Need at least one Global Catalog server in every office that has an Exchange 2003 server. This also can act as the nearby Domain Controller. The simplest way to accomplish this is to make all department office DCs into GCs. Microsoft recommends no less than one GC server for each four Exchange processors, now not servers.

O DNS configuration. Make certain that DNSLint suggests no mistakes, other endorsed device KILLADCGN.EXE to affirm chkds Checkdisk and chkdsro (CheckReplicationOrphan gadgets in AD);

o Active Directory Native Mode. Important Notice: The Active Directory domain containing the Exchange servers have to be in Native Mode so that you can use Universal Security Groups for email distribution.

O Replication or authentication troubles. Verify Event Viewer to have no mistakes from directory carrier replication, KCC topology calculations, or authentication errors originating from domain controller accounts. You can use the EventCombMT application (download from Microsoft). EventCombMT is a part of the Account Lockout and Management and Lockout

o Domain Prerequisites Considerations : Name Resolution, ADC Staging OU, ADC Staging, Verify trusts problems, 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 Patches

O E-mail structured programs

O Exchange 2000 on the spot messaging

Pre-Requisites and Precautions before the installation:

o Security patches (ISDS for Exchange)

o In order to maintain Exchange five.5 Public Folder Access Control Lists (ACLs) after mailboxes or distribution lists are moved between web sites the Administrator will want to put in an Exchange five.5 DS/IS hotfix (http://assist.Microsoft.Com/?Kbid=836489) on every Exchange 5.5 Public Folder server previous to transferring mailboxes or DLs among sites.

O The Consistency Adjuster ought to be run for every server in every website.

O Windows carrier packs (SP4.0 for Exchange five.5 at the same time as Exchange 2003 is on SP2.Zero this facts must be revised at the internet site of Microsoft for the brand new updates)

o Considerations – Mobile Information Server (MIS) –To hold functionality for present cellular users throughout the Exchange 2003 deployment, maintain at the least one MIS five.Five servers jogging as you migrate to Exchange 2003.

O Instant Messaging (IM) and Chat –This capability has been changed by way of Live Communication Server (LCS) in Exchange 2003.

O CcMail connector — If you are walking ccMail (in particular for Lotus Mail Agents) in the agency along side Exchange, it’s time for a final transition upon the migration course to Exchange 2003.

O Backup, Antivirus, and Antispam software program compatibility troubles and third party software troubles

o ADC upgrades considerations – You need to upgrade the ADC servers to Exchange 2003 ADC previous to introducing any Exchange 2003 servers into the agency. The ADC upgrade modifies the schema, so make sure that the Schema Master is to be had.

O Front-give up/returned-stop improvements. – If you have got an existing deployment which include for instance, Exchange 2000 that uses a distributed structure, improve the the front-cease servers first and then upgrade the backend servers.

Leave a Reply

Your email address will not be published. Required fields are marked *