Flylib.com

Books Software

 
 
 

PREPARING THE NETWORK ENVIRONMENT FOR EXCHANGE

 < Day Day Up > 

PREPARING THE NETWORK ENVIRONMENT FOR EXCHANGE

  1. DCs must be running Windows 2000 SP3 (or higher) or Windows Server 2003. GC servers should be placed in all sites/domains that host Exchange Server 2003. DNS servers must be configured correctly.

  2. Run ForestPrep in the domain that hosts the forest's Schema Master. The account that runs ForestPrep must be a member of the Schema Admins and Enterprise Admins groups. Run DomainPrep in each domain that will utilize Exchange, even if no Exchange servers will actually be installed. The account that runs DomainPrep must be a member of the Domain Admins group . ForestPrep only needs to be run once. You must run both utilities at least once before installing Exchange Server 2003. When you run ForestPrep, specify a user account that will receive the Exchange Full Administrator permission.

 < Day Day Up > 
 < Day Day Up > 

PREPARING THE SERVER ENVIRONMENT FOR EXCHANGE

  1. Before installation (or upgrade), Windows 2000 Server must be patched to at least SP3. The following services must be installed and running: WWW Publishing Service, SMTP Service, ASP.NET, .NET Framework, and NNTP Service.

  2. Exchange Server 2003 requires at least a Pentium 133MHz (733MHz is recommended) compatible computer with 256MB RAM (512 recommended), 500MB on the volume where Exchange is installed, and 200MB on the system volume. Disk partitions must be formatted with NTFS.

 < Day Day Up > 
 < Day Day Up > 

INSTALLING EXCHANGE

  1. The first Exchange installation must be performed by the account specified with ForestPrep, which must have local admin permissions on the server on which Exchange will be installed.

  2. Exchange Server Deployment Tools is a set of checklists to assist with the installation of Exchange.

 < Day Day Up > 
 < Day Day Up > 

PREPARING TO UPGRADE TO EXCHANGE SERVER 2003 FROM EXCHANGE 2000

  1. Run the new versions of ForestPrep and DomainPrep when upgrading from Exchange 2000 to Exchange Server 2003.

  2. Exchange 2000 Server cannot run on Windows Server 2003.

  3. Remove the following Exchange 2000 Server components before upgrade: instant messaging, Exchange Chat, Exchange 2000 Conferencing Server, Key Management, cc: Mail connector, and MS Mail connector.

  4. Upgrade front-end servers before back-end servers.

  5. To migrate from an old Exchange 2000 Server organization to a new Exchange Server 2003 organization, use the ADMT in conjunction with the Exchange Server Migration Wizard.

 < Day Day Up > 
 < Day Day Up > 

UPGRADING/COEXISTING WITH EXCHANGE SERVER 5.5

  1. Install ADC to synchronize the Exchange Server 5.5 directory with AD.

  2. Coexistence allows Exchange Server 5.5 and Exchange Server 2003 to be part of the same organization. Coexistence allows you to move users from Exchange 5.5 to Exchange Server 2003 with the Move Mailbox tool.

  3. To migrate from an old Exchange Server 5.5 organization to a new Exchange Server 2003 organization, use the Exchange Server Migration Wizard.

 < Day Day Up > 
 < Day Day Up > 

MIGRATING FROM AND COEXISTING WITH OTHER MESSAGING SYSTEMS

  1. The Exchange Server 2003 Migration Wizard can be used to migrate users from MS Mail for PC Networks, Lotus cc:Mail, Lotus Notes, Novell GroupWise 4.x and 5.x, Internet Directory (LDAP via ADSI), and Internet Mail (IMAP4).

  2. Exchange Server 2003 can share calendars and address lists with Lotus Notes R4/R5 via Lotus Notes Connector. Connector requires that a special account be configured on the Notes server and the Notes Client be installed on the Exchange server on which the connector is implemented.

  3. Exchange Server 2003 can share calendar/address lists with Novell GroupWise via a connector. Configure a NetWare user on the GroupWise server with read/write permissions to API gateway directories. The user account must be a member of the GroupWise NTGateway group .

 < Day Day Up >