Re: can NT4 servers and 2003 server play nicely together?
From: Frances [MSFT] (v-franhe_at_microsoft.com)
Date: 03/01/05
- Next message: Jason Tan: "RE: ADMT Usage"
- Previous message: Mugen: "Re: Hwo to setup DNS Subdomain (Child) as UNIX DNS"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 01 Mar 2005 03:14:44 GMT
Hello,
Good to hear from you.
According to your message, I understand that your main concern is whether
NT servers and win2k3 servers can both be on the wire at the same time. The
answer is yes.
>From your description, I understand that you plan to migrate from NT to
win2k3 domain, and then rename the win2k3 domain to the original name of
the NT domain. The process is practical; however, it is complicated to
rename the domain name. If your main goal is to get a win2k3 domain from
NT, it is best to upgrade you NT domain, as Jim has suggested. Since
upgrade provides the easiest and lowest-risk migration path. On the other
hand, if your network is very complex with account and resource domains or
other external trust relationships, you'd better consider migration.
I will provide you the two methods to get a win2k3 domain from NT and keep
the domain name at the same time. You can choose the method according to
your real environment.
In addition, if you have installed Exchange, you may consult in the
Exchange newsgroup before you take any action.
I assume you have a NT4 domain, not NT4 SBS domain.
Performing a "not in place" upgrade
============================
1.Install NT 4.0 BDC on the new box.
2.Promote the BDC to the PDC, which demotes the PDC to a BDC.
3.Do a full backup of the former PDC and remove it from the network.
4.Upgrade the new PDC to Windows Server 2003.
If you want to expand the boot partition, please refer to the following KB:
325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade
http://support.microsoft.com/?id=325857
5.Promote the win2k3 server to be a DC.
The Active Directory service imports the existing user accounts, groups,
and other settings from the PDC.
6.Run for a test period.
7.If desired you can do a clean installation of Windows Server 2003 on the
former PDC, and bring it online as an Active Directory domain controller.
8.Transfer all Flexible Single-Master Operation (FSMO) roles to the new
Windows Server 2003 domain controller.
9.Verify all directory information has replicated.
10.Demote the first domain controller to a member server, and remove from
the domain
As a kind reminder, please backup the whole system before you take any
action. Also, it is best if you perform the upgrade process during a
non-business time such as the weekend. :)
Upgrade will automatically import the existing user accounts, groups, and
other settings from the PDC. This way you do not need to rename your domain.
Method 2: Migration
===============
1. Set up two-way trusts between NT and win2k3 domain.
2. Use ADMT to migrate from NT to win2k3 domain.
You may refer to the following article.
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.
3. Rename the win2k3 domain to the name you desire.
The process is very complicated. The requirements are as follows:
1) All domain controllers must be running Windows 2003.
2) The Windows 2003 forest functionality level must be raised to Windows
Server 2003.
3) Rename cannot be used to drop domains from the forest or add domains to
the forest. The number of domains in the forest before and after the
rename/restructure operation must remain the same.
4) Domain rename operations are not supported in an Active Directory forest
that includes an Exchange deployment. The domain rename tool will detect
this fact and refuse to proceed.
The following are some additional items needed to be considered when
planning a domain rename operation:
1) The forest will be out of service for a short period of time. Forest
service is interrupted during the time it takes for each domain controller
to perform the directory database updates necessary for the domain rename
and then reboot.
2) All domain controllers must either successfully complete the rename
operation or be eliminated from the forest.
3) Each member computer joined to a renamed domain must be rebooted twice
after all domain controllers have been updated. Machines running Windows NT
4.0 will need to disjoin and then rejoin the renamed domain instead of
rebooting.
Please refer to the following documents:
Windows Server 2003 Active Directory Domain Rename Tools
<http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx>
Step-by-Step Guide to Implementing Domain Rename
<http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90
a2a2e2/Domain-Rename-Procedure.doc>
So, sometimes we choose to have a new temporary AD domain to avoid the
renaming process. For clarify, let us name the temporary domain TemD, the
NT domain NTD and the win2k3 domain WinD. We can use ADMT to migrate
everything from NTD to TemD and then migrate from TemD to WinD. This way,
we can avoid renaming a domain name.
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.
- Next message: Jason Tan: "RE: ADMT Usage"
- Previous message: Mugen: "Re: Hwo to setup DNS Subdomain (Child) as UNIX DNS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
