Software

Tech Tip: Create a realistic migration lab environment

Major migration projects make a test lab practically mandatory. A test environment allows you to try new things without risk; it also helps you write and test your migration plan.

It's best to build a lab that mimics your production environment as closely as possible. Seeing your company's directory structure in Active Directory (AD), for example, gives you a "been there, done that" confidence that no canned environment can duplicate.

Here's how to build a system that serves as the cornerstone of a lab network. You can use this lab for planning and practicing migrations from Exchange 5.5 to Exchange 2000 and/or from Windows NT 4.0 to Windows 2000.

Your test server should have the capacity to run Windows 2000 AD and Exchange 2000. It also needs enough disk space to restore your Exchange directory and information store and a tape drive to perform the restore.

Follow these steps:

  1. Build the test server as a backup domain controller (BDC) in your Windows NT 4.0 domain.
  2. Create the logical drives you need to accommodate Exchange 2000.
  3. Apply the same Windows NT service pack that the production mail server has.
  4. Remove the test server from the production network, and rename it with the same name your mail server has.
  5. Promote the test server to a primary domain controller (PDC).
  6. Install Exchange 5.5, and apply the same Exchange service pack that the production server uses.
  7. On the server, create a new site with the same organization and site names as the production Exchange server.
  8. Configure circular logging in the same way as the production server.
  9. Restore the production directory and information stores from tape.

You now have a test server with your company's production Windows NT 4.0 and Exchange 5.5 directories. Now that you've built the main server as a PDC, you can add other systems into the environment as required to simulate your production network.

Editor's Picks

Free Newsletters, In your Inbox