RE: windows NT to Win2K3 with Exchange 5.5 to Exchang 2K3

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


Date: Mon, 28 Feb 2005 03:57:04 GMT

Hello Fshguo,

Good to hear from you.

According to your message, I understand that you now have a NT domain and a
win2k domain. You goal is to migrate the NT domain to a win2kd domain. Is
this correct?

I notice you have Exchange 5.5 on your BDC, and you plan to migrate
Exchange 5.5 to Exchange 2k3. Regarding this part, pease post it in the
microsoft.public.exchange.setup newsgroup since they are the experts in
Exchange and will provide the most accurate information on this issue.

As for migrating NT to win2k3 domain, I suggest you follow the two steps
below to achieve your goal.

1. Upgrade your win2k domain to win2k3 domain.

2. Migrate from NT to win2k3 using ADMT.

Upgrading to win2k3 domain
===================
1. Backup your win2k DC before you take any action.

2. Run "adprep" to extend the schema.
Run "ADPREP /FORESTPREP" and "ADPREP /DOMAINPREP") to upgrade the existing
Windows 2000 forest and domain to ensure that they contain the additional
objects, attributes and permissions necessary to support the Windows Server
2003 Active Directory environment.

Refer to the following articles for more information.

Please pay more attention in the part "Overview: Upgrading Windows 2000
domain controllers to Windows Server 2003", which contains the information
about "adprep":
325379 How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

Upgrading Windows 2000 Domains to Windows Server 2003 Domains
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/windowsserver2003/proddocs/deployguide/dssbf_upwn_overview.asp

3. Decide whether to directly upgrade a win2k DC depending on the hardware.
(Optional)

3.1 If the hardware supports win2k3, upgrade the win2k DC to win2k3 DC by
using Winnt32.exe.

3.2 If the hardware doesn't support win2k3, promote a win2k3 member server
to DC by dcpromo.

Step 3 is optional because after step 2, you have already had a win2k3
domain. You can upgrade your win2k DC to win2k3 DC as you like.

Migrating from NT domain to win2k3 domain:
================================
1. Set up trusts between NT and win2k3 domain.
In your scenario, you have already had dual trusts established with NT and
win2k. When win2k domain is upgraded, the trusts will remain. You may
verify the trusts and then go on.

Use NetDom or Active Directory Domains and Trusts to verify the trusts.

Please refer to the articles below.

NetDom Examples
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techre
f/en-us/NetDom_examples.asp

Pay extra attention to the snippet "verify a trust":
How to establish trusts with a Windows NT-based domain in Windows Server
2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;325874

2. Use ADMT to migrate from NT to win2k3.

I would like to suggest that you migrate the groups and users separately
(do not migrate the associated members when migrating groups).

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

More information:

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

Migrating Windows NT to Windows Server 2003 using the Active Directory
Migration Tool

http://techupdate.zdnet.com/techupdate/stories/main/Migrating_Windows_NT_to_
Windows_Server_2003.html

This response contains a reference to a third-party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.

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: Migration from a mixed enviroment Netware 5.1 and NT towards AD Windows Server 2003
    ... environment (NT and NDS) to win2k3 domain. ... I assume you prefer to upgrade your original NT domain to win2k3 domain, ... Novell NetWare to Windows NT Migration ...
    (microsoft.public.windows.server.migration)
  • Re: User Profile Migration From NT Domain To AD domain
    ... upgrade the NT 4 domain to Windows 2000 since you wish to maintain the same ... Windows 2000 Directory Services ... > Win2K but a pure Win2K installation. ... > The problem I have is when a users logon to AD domain with the same> ABCdomain, the user profile in thier PC is set to default. ...
    (microsoft.public.win2000.active_directory)
  • Re: Upgrading to Windows XP Pro from W2K Pro
    ... A clean install is seldom a bad idea, especially if you haven't done one in ... because it was "inherited" from Win2K when I upgraded. ... Microsoft Windows MVP ... > The upgrade option is attractive because it retains all of my systems and ...
    (microsoft.public.windowsxp.newusers)
  • Re: Upgrade from Windows ME?
    ... structure and Win2K doesn't know anything about System Restore. ... Windows Me to Windows 2000 Upgrade Is Not Supported ... It's not technically possible to perform an upgrade from WinMe to ...
    (microsoft.public.win2000.general)
  • Re: Add Server 2003 and Logon scripts deleted from profiles
    ... I understand this issue occurs after you upgrade win2k to win2k3 domain. ... process has been smoothly performand and this issue also appear if you turn ...
    (microsoft.public.windows.server.migration)