Re: Need Recommendations on NT4 > WS2003 Migration

From: Frances [MSFT] (v-franhe_at_microsoft.com)
Date: 02/14/05 

Date: Mon, 14 Feb 2005 09:21:18 GMT

Hello,

Good to hear from you.

According to your message, I understand that you want to have a win2k3
domain. Both the migration and the upgrade as Jeff has suggested are OK.
You can choose one method regarding your real situation.

Since the ERP plays an important role in your scenario, I suggest that you
run the command "winnt32 /checkupgradeonly" on your PDC to check the
compatibility of the software with win2k3.

More details can be found in the following article.
244632 How to Test Programs for Compatibility with Windows
http://support.microsoft.com/?id=244632

Meanwhile, I strongly recommend you consult with the ERP's vendor to make
sure that the ERP is compatible with win2k3 and it is possible to migrate
ERP data to the new box. Regardless you choose to upgrade or migrate to
win2k3 domain, the key point is to remain the existing ERP data.

In addition, I notice you have a Novell4.1 print and file server. It would
be better to allow other win2k3 computer to hold the print and file
services. Please refer to the white paper in the following link, and pay
attention to the snippets "Migration Process" in Part 1 and "Printer
Migration" in Part2.
 
Solution for Migrating File, Print, and Directory Services from Novell
NetWare to Windows Server 2003
http://www.microsoft.com/windowsserver2003/migrate/novell/novellmg.mspx

The key difference between upgrade and migration is listed as follows:

Upgrade:
Upgrade will retain the original domain name and the network
infrastructure. Comparatively speaking, upgrade provides the easiest and
lowest-risk migration path.

Migration:
Migration needs a new domain name. You need to design your new network
topology. It is best to be used in some complex networks with account and
resource domains or other external trust relationships.
Although you can rename domain name to the original name with some tools,
it is very complicated.

Please choose according to your real environment.

I will discuss the two choices in detail.

Migrating to the win2k3 domain:
=====================

Please use ADMT to migrate from NT to win2k3 domain.

1. Create the trust relationship between the two domains.

2. Use the ADMT to migrate data from the old domain to the new domain.Run
win2k3 for a period of time to make sure the network can be functional.

3. Remove the NT domain.

Before you migrate, I strongly suggest that you download and read the
following document.
Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp

You can download ADMT from the link below:
Windows 2000 Active Directory Migration Tool
http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp

Upgrading to the win2k3 domain:
=====================
In this way, you have to install BDC on the box, and upgrade it to win2k3.
Please make sure the win2k3 (OEM) can be upgraded from NT. The steps are as
follows:

1.Install NT 4.0 BDC on the new box.

2.Promote the BDC to the PDC, upgrade the new PDC to Windows Server 2003.

Refer to the following articles for more information.

Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx

Windows NT Server 4.0 Upgrade Guide
http://www.microsoft.com/windowsserver2003/partners/isvs/ntmigrate.mspx

As for obtaining WinSrv2003 Web Edition for the old NT box, it is
impossible according to the article below. You can refer to it.

Windows Server 2003 Supported Upgrade Paths
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/supportedpa
ths.mspx

Hope this helps. If you have any further questions, don't hesitate to get
in touch!

Best regards,

Frances He

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.

Relevant Pages

  • RE: Upgrading Windows 2000 Domain to Windows 2003
    ... your main concern is Exchange. ... As for the upgrade, it is easy to upgrade from win2k domain to win2k3 ... domain controllers to Windows Server 2003", ...
    (microsoft.public.windows.server.migration)
  • RE: NDS for NT Migration
    ... It is hard to say which is the easiest way to do the migration. ... I believe you can upgrade NT to win2k3 first and then use ... MSDSS to migrate files from Novell. ...
    (microsoft.public.windows.server.migration)
  • RE: NT4 --> 2003 , lmhosts?
    ... it is not difficult to perform an in-place upgrade ... if you have PDC and several BDCs ... please upgrade PDC to win2k3 first. ... 325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade ...
    (microsoft.public.windows.server.migration)
  • RE: Merging three domains
    ... I understand that you want to upgrade DomainB and DomainC from Win NT 4.0 ... Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active ... suggest you prefer to consider migration. ...
    (microsoft.public.windows.server.migration)
  • RE: Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC
    ... You need to change the domain name since win2k3 will detect the ... Windows Server 2003 DC and has the same domain name? ... find a server which is now running NT BDC and it can be upgrade to Win2k3. ... example, if one of the Citrix MetaFrame 1.8 can be upgrade to win2k3, you ...
    (microsoft.public.windows.server.migration)