RE: NT4 PDC Exchange 5.5 to Server 2003 and Exchange 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Alan Sun [MSFT] (v-asun_at_online.microsoft.com)
Date: 10/18/04 

Date: Mon, 18 Oct 2004 06:56:03 GMT

Hi Chris,

Thanks for your posting here.

As Exchange 5.5 cannot running on a Windows 2003 computer and Exchange 2003
should be installing a native-mode Windows 2000/2003 Domain, we cannot
inplace upgrade NT 4/Exchange 5.5 to Windows 2003/Exchange 2003. You can
use the method you metioned: upgrade to Windows 2000/Exchange 2000, and
then upgrade to Windows 2003/Exchange 2003. However, this is quite
inconvenience.

I suggest you intruduce a new Windows 2003 domain with setup a new Windows
Server 2003 DC, migrate NT accounts, Exchange 5.5 and other data to the new
domain, and remove the original NT4 domain at last:

1. Setup a new Windows Server 2003 DC in the new domain.

2. Create the trust relationship between the two domains.

3. Use the ADMT to migrate data from the old domain to the new domain.

4. Build a Windows 2003 member server. Install Exchange 2003 and join to
the original Exchange 5.5 orgnization, migrate data from Exchange 5.5 to
Exchange 2003.

5. When you confirm everything is working fine, you can remove the original
NT domain.

For more information, refer to the following articles:

Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx
Exchange Server 2003 Deployment Guide
http://www.microsoft.com/technet/prodtechnol/exchange/exchange2003/proddocs/
library/depguide.asp

Here is a thorough example of Exchange server migration from Exchange 5.5
to Exchange 2003:
http://www.microsoft.com/exchange/evaluation/landamerica.asp

These articles are also be heplful:

Q810591:XGEN: Exchange 2000 Server and Exchange Server 5.5 Compatibility
with Windows 2003
http://support.microsoft.com/?id=810591

Q321648:XADM: You Cannot Install Exchange 2000 on a Computer That Is
Running Windows 2003
http://support.microsoft.com/?id=321648

Hope this helps! Thanks and have a nice day!

Thanks & Regards
Alan Sun
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
     From: cwhite@caw.me.uk (Chris White)
     Newsgroups: microsoft.public.windows.server.migration
     Subject: NT4 PDC Exchange 5.5 to Server 2003 and Exchange 2003
     Date: 17 Oct 2004 09:40:45 -0700
     Organization: http://groups.google.com
     Lines: 31
     Message-ID: <81d08e3d.0410170840.95b9e@posting.google.com>
     NNTP-Posting-Host: 62.7.166.227
     Content-Type: text/plain; charset=ISO-8859-1
     Content-Transfer-Encoding: 8bit
     X-Trace: posting.google.com 1098031245 23974 127.0.0.1 (17 Oct 2004
16:40:45 GMT)
     X-Complaints-To: groups-abuse@google.com
     NNTP-Posting-Date: Sun, 17 Oct 2004 16:40:45 +0000 (UTC)
     Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.co
m!news.maxwell.syr.edu!postnews1.google.com!not-for-mail
     Xref: cpmsftngxa06.phx.gbl
microsoft.public.windows.server.migration:14721
     X-Tomcat-NG: microsoft.public.windows.server.migration
     
     Hi All,
     
     I have been given the job of upgrading our existing NT4 domain to 2003
     and whilst in the process Exchange 5.5 to 2003.
     
     Here is my situation.
     
     I have a single NT domain with a PDC and 3 BDC's and approx 200 users.
     The PDC runs DNS, WINS, DHCP and Exchange 5.5. We have purchased a new
     server which will replace the existing PC. We want as little downtime
     as possible so want to keep the new PDC's name the same as the old.
     
     I have setup a test enviroment with the BDC removed from the main
     network and the new server. I have promoted the BDC to a PDC,
     installed NT4 on the new server and set as a BDC, updated from the
     promoted PDC, then promoted to PDC and demoted old PDC.
     
     I have read many comments on the ways of migrating to 2003 and from
     what I have seen the best method for us is to do an in place upgrade
     on the new server by now installing Exchange 5.5 and restoring data
     from original server backup then upgrading NT to 2000, Exchange to
     2000, Exchange to 2003 then Windows to 2003 but I am a bit worried
     about the time this will take.
     
     If anybody has been through this process and has a guidline on times
     or whether there is a problem with my method and there's a better way,
     I would be gratefull for any advice.
     
     Thanks in advance
     
     Chris
     

Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)