RE: Win NT4.0 PDC -> Win 2003

Tech-Archive recommends: Speed Up your PC by fixing your registry


Hi Alex,

Thanks for posting!

Based on the description, I would like to provide you with some information
for your reference:

---So what are the best tools to Export settings from NT4.0 LAN (as much as
possible) and import them to Win2003 LAN, without touching NT4.0 LAN.

I strongly recommend that you use this tool to migrate the user profiles in
this case, because it can move all the local user profiles on a computer,
as long as it finds that the users have been migrated before. So it should
be the most efficient method to move a large number of user profiles on a
certain client computer.

More information for ADMT:

Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp

Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25-
8de0-19544062a6e6&DisplayLang=en

Download Active Directory Migration Tool v.2.0
http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-
9817-8c9773c25c6c&DisplayLang=%20en

832221 How to configure the Active Directory Migration Tool to migrate user
passwords from a Windows NT 4.0 domain to a Windows Server 2003 domain
http://support.microsoft.com/?id=832221

Note: To be familiar with the migration processing, we highly recommend you
test the migration processing in lab environment.

Since you want to keep the original domain name and do not want touch the
NT domain LAN, I would suggest you the following information:

1. Build a new Window server 2003 box and DCPROMO it to DC (DC2) with a
different domain name temporarily.

2. Create Trust relationship between Windows NT domain and Windows 2003
domain.

3. Use ADMT migrate objects from Windows NT PDC (DC1) to Windows 2003
domain.

The Recommended Migration Order is listed below for your reference:
==============================================================
1. Service account migration
2. Domain Global Group
3. Domain Local Group
4. User migration
5. Computer migration
6. Security translation
7. Report
==============================================================
4. Build another Windows server 2003 DC (DC3) with the same domain name of
Windows NT domain and use ADMT migrate objects from DC2 to DC3.

5. Build others Windows 2003 server as additional server or member server
and move services as well as data from NT. I would like to provide you with
the following article for your reference:

325473 How to move a DHCP database from a computer that is running Windows
NT
http://support.microsoft.com/?id=325473

280061 How to move Windows 2000 DNS zones to another Windows 2000-based
server
http://support.microsoft.com/?id=280061

328810 Moving mailboxes between servers
http://support.microsoft.com/?id=328810

276485 HOW TO: Use Exchange Server 5.5 Mailbox Manager with Exchange 2000 in
http://support.microsoft.com/?id=276485

Regarding file migration, please refer to the following article:
Overview of the Microsoft File Server Migration Toolkit
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx

I hope my information helps. If there is anything that is unclear, please
feel free to let me know.

Thanks & Regards,

Jason Tan

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: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: SwingIt Pain and Suffering
    ... BTW - I did purchase the Advanced Windows Small Business Server 2003 Best Practices book and consumed large parts of it before starting this project. ... That being said, I do feel like his documentation could greatly benefit by having some more detailed check points for verifying the health of AD at various steps along the way, and what steps to take or resources to consult if the replication doesn't seem to be going according to plan. ... BTW, even after discovering this constraint and disabling the firewalls on my destination server as part of the base OS install, replication still initially failed and I was dumb founded to find the firewall reenabled. ... I did complete the AD replication from the migration computer to the destination computer as planned. ...
    (microsoft.public.windows.server.sbs)
  • Re: NT4 to 2003 with Dell2650
    ... PDC for good; ie Will the accounts stay on the PDC to allow me a testing ... The Recommended Migration Order is listed below for your reference: ... Yes, after completion of ADMT, you may logon to the new Windows Server 2003 ...
    (microsoft.public.windows.server.migration)
  • RE: SMTP IIS6.0 -problem to send out external email
    ... Windows 2003 server. ... > on IIS service after migrating from Win2k to Win2k3. ... > migration, how do you migrate the application, does the application have ...
    (microsoft.public.windows.server.migration)