< Day Day Up > |
As previously mentioned, the in-place upgrade method is the most straightforward approach toward migration. Existing server architecture and database structure is maintained . In many ways, this type of upgrade simply involves throwing in the Exchange Server 2003 CD and performing the upgrade. An upgrade to Exchange Server 2003 is a two-step process. The first step involves upgrading the Exchange application component to Exchange Server 2003. The second step involves upgrading the operating system from Windows 2000 to Windows Server 2003. Exchange Server 2003 supports upgrading only Exchange first, because Exchange 2000 cannot function on a Windows Server 2003 operating system. The OS does not require upgrading, but it is recommended to do so to take advantage of all the new Exchange Server 2003 features that tie into the new OS. Making Use of the Exchange Server 2003 Deployment ToolsMicrosoft has streamlined its Exchange deployment process by creating a set of deployment tools to assist with the Exchange installation process. With Exchange 2000, Microsoft found that the complexity of the upgrade process created confusion among the uninitiated, and led to some rather serious support calls. The Exchange deployment tools provide step-by-step checklists to ensure that the upgrade process is uneventful. Using the Exchange Server 2003 Deployment tools is a straightforward process and is the first step toward upgrading an existing Exchange 2000 Server in place. To initiate the upgrade process, perform the following steps:
The prerequisite tasks listed should be performed in any situation, and can help ensure that everything is in place before beginning intrusive tasks, such as upgrading the AD schema. Microsoft included these tasks in the deployment tools to proactively identify potential issues with the Exchange server setup before they become major production incidents. Upgrading the Active Directory Schema with Exchange ForestPrepExchange Server 2003 requires that the Active Directory schema be modified to support the new enhancements in the product. The schema of Active Directory contains a list of all attributes and objects that can exist in the directory, and is the core framework around which Active Directory operates. It is a critical piece of an enterprise directory, and great care should be taken when examining changes to its structure, such as those enacted during Exchange Server setup. After the initial steps have been followed with the Exchange deployment tools, Exchange ForestPrep can be run on a domain controller in the schema root domain. It can be run manually or from the command line, or it can be invoked from the Exchange deployment tools, as follows :
NOTE The changes made to the AD schema can be viewed via low-level LDAP tools, such as ADSI Edit. This particular tool can be installed as part of the Windows Server 2003 Support Tools pack, which is located on the Windows Server 2003 CD in the \Support\Tools directory. Preparing Each Domain for Exchange Server 2003 with DomainPrepAfter the AD schema has been upgraded and the changes have propagated throughout the AD forest, each domain in the forest must be prepared for Exchange Server 2003 via the DomainPrep procedure. Although DomainPrep can be run via the command prompt ( setup /domainprep ), it can also be launched via the deployment tools as follows:
NOTE DomainPrep must be run on each domain in a forest, even though it might have been run during the setup of Exchange 2000, because Exchange Server 2003 DomainPrep performs additional required tasks. The DomainPrep procedure creates groups necessary for Exchange and sets appropriate permissions for the accounts required. The groups that it creates (Exchange Domain Servers and Exchange Enterprise Servers) must be kept in the default Users container in AD and must not be renamed to ensure functionality. Running the In-Place Upgrade of an Exchange 2000 System to Exchange Server 2003After all the prerequisites have been satisfied, ForestPrep has been run and replicated, and DomainPrep has created the appropriate groups and permissions in each domain, the actual upgrade procedure for Exchange Server 2003 can commence. The upgrade process should be run from the server that is to be upgraded, and can be manually initiated or invoked via the Deployment Tools, as follows:
At this point, Exchange is updated from Exchange 2000 to Exchange Server 2003. The new Exchange System Manager tool is installed, and the bulk of Exchange Server 2003 functionality is present for all mailboxes on the server. Upgrading the Operating System from Windows 2000 to Windows Server 2003The final piece of the puzzle, which makes an Exchange 2003 system complete, is the upgrade of the base operating system to Windows Server 2003. Certain functionality, especially regarding security, cannot be achieved until the base OS for Exchange Server 2003 is running the new OS. Fortunately, the upgrade from Windows 2000 to Windows Server 2003 is straightforward, and can be accomplished via the following steps:
Upon the successful completion of the steps outlined in this section, an Exchange 2000 system will be upgraded to Exchange Server 2003, using the in-place upgrade method. At this point, any additional servers that have been marked for upgrade can use this procedure. Upgrading Additional Exchange 2000 Servers to Exchange Server 2003Each additional server that is running Exchange 2000 can be upgraded using the same technique described in the previous sections. The prerequisite steps, ForestPrep and DomainPrep do not need to be repeated for each additional server, however. Unlike with Exchange 5.5, there is no functional difference between an allExchange 2003 or mixed Exchange 2000/2003 environment, so there is no Exchange Server 2003 Native Mode. Most of the differences will be noticeable at the client level, however, in the form of improvements to the client experience, such as OMA, ActiveSync, RPC over HTTP, and improved security. |
< Day Day Up > |