Exchange to ne Hardware :: essays research papers

If you simply want to do an in-place upgrade of Exchange 2000 to Exchange 2003 using the same server, you’ve got it made – Microsoft has explained the process of upgrading and made it pretty simple. Even if you’re still using Exchange v5.5, Microsoft has you covered with a wealth of documentation to peruse. But what if you’re an Exchange 2000 organization that wants to bring in a new Exchange 2003 system alongside your existing machine, move all your content over to it, and decommission the original box? Then you’re left scratching your head. At the time of this writing, there is no guide I’ve been able to find that explains the process with any detail. This document will explain the process, combining information from numerous sources as well as my own experience. It’s very easy to bring Exchange Server 2003 into your Exchange 2000 organization, with minimal disruption to your existing server or your users. This document assumes you have an Exchange 2000 organization running in native mode. Henceforth, the Exchange 2000 system will be referred to as the â€Å"old† server, and the Exchange 2003 system will be referred to as the â€Å"new† server. I. Prepare your Network for Windows Server 2003 Regardless of how you intend to get to Exchange 2003, there are some basic steps that must be done. 1.  Ã‚  Ã‚  Ã‚  Ã‚  Begin by reviewing Microsoft’s 314649 – â€Å"Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers† This article explains that if you have Exchange 2000 installed in your organization, and you proceed with installing your first Windows Server 2003 system (and its accompanying schema modifications), you may end up with some mangled attributes in AD. Preventing this from happening is simple enough: a script called Inetorgpersonfix.ldf will do the trick. 2.  Ã‚  Ã‚  Ã‚  Ã‚  Run adprep /forestprep from Windows Server 2003 CD on your Windows 2000 server that holds the Schema master FSMO role. (Of course you’ll need to be a member of Schema Admins). Be sure to replicate the changes throughout the forest before proceeding. 3.  Ã‚  Ã‚  Ã‚  Ã‚  Run adprep /domainprep from Windows Server 2003 CD on your Windows 2000 server. I ran it on the system holding the PDC Emulator FSMO role. 4.  Ã‚  Ã‚  Ã‚  Ã‚  Before bringing a new Windows Server 2003 system online, it’s a good idea to review your third-party server utilities and upgrade them to the latest versions to ensure compatibility. In my installation, this included the latest versions of BackupExec, Symantec Antivirus Corp. Exchange to ne Hardware :: essays research papers If you simply want to do an in-place upgrade of Exchange 2000 to Exchange 2003 using the same server, you’ve got it made – Microsoft has explained the process of upgrading and made it pretty simple. Even if you’re still using Exchange v5.5, Microsoft has you covered with a wealth of documentation to peruse. But what if you’re an Exchange 2000 organization that wants to bring in a new Exchange 2003 system alongside your existing machine, move all your content over to it, and decommission the original box? Then you’re left scratching your head. At the time of this writing, there is no guide I’ve been able to find that explains the process with any detail. This document will explain the process, combining information from numerous sources as well as my own experience. It’s very easy to bring Exchange Server 2003 into your Exchange 2000 organization, with minimal disruption to your existing server or your users. This document assumes you have an Exchange 2000 organization running in native mode. Henceforth, the Exchange 2000 system will be referred to as the â€Å"old† server, and the Exchange 2003 system will be referred to as the â€Å"new† server. I. Prepare your Network for Windows Server 2003 Regardless of how you intend to get to Exchange 2003, there are some basic steps that must be done. 1.  Ã‚  Ã‚  Ã‚  Ã‚  Begin by reviewing Microsoft’s 314649 – â€Å"Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers† This article explains that if you have Exchange 2000 installed in your organization, and you proceed with installing your first Windows Server 2003 system (and its accompanying schema modifications), you may end up with some mangled attributes in AD. Preventing this from happening is simple enough: a script called Inetorgpersonfix.ldf will do the trick. 2.  Ã‚  Ã‚  Ã‚  Ã‚  Run adprep /forestprep from Windows Server 2003 CD on your Windows 2000 server that holds the Schema master FSMO role. (Of course you’ll need to be a member of Schema Admins). Be sure to replicate the changes throughout the forest before proceeding. 3.  Ã‚  Ã‚  Ã‚  Ã‚  Run adprep /domainprep from Windows Server 2003 CD on your Windows 2000 server. I ran it on the system holding the PDC Emulator FSMO role. 4.  Ã‚  Ã‚  Ã‚  Ã‚  Before bringing a new Windows Server 2003 system online, it’s a good idea to review your third-party server utilities and upgrade them to the latest versions to ensure compatibility. In my installation, this included the latest versions of BackupExec, Symantec Antivirus Corp.