RE: Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC
From: Rebecca Chen [MSFT] (v-rebc_at_online.microsoft.com)
Date: 09/29/04
- Next message: Rebecca Chen [MSFT]: "Re: NT4 Print Server ---> Windows Server 2003 Clustered Print Server"
- Previous message: Rebecca Chen [MSFT]: "Re: FSMO roles placement"
- In reply to: John: "Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC"
- Next in thread: John: "RE: Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC"
- Reply: John: "RE: Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 08:02:42 GMT
Hi John,
Please my inline:
1. When I build the new server and I give the name for the FOREST is it ok
to give the name of the forest as PDC’s name?
A: No. You need to change the domain name since win2k3 will detect the
original NT domain name and refuse the use the same name.
2. How will the existing Windows NT 4.0 PDC react when it sees the new
Windows Server 2003 DC and has the same domain name?
3. Will the Windows NT 4.0 PDC starts replicating all user accounts, groups
and others to the new DC
4. Now, can I remove the existing PDC from the network after testing that
the authentication is taking place through the new Windows Server 2003
domain controller?
A: They cannot have the same domain name. After you join win2k3 in the
original NT domain and use Dcpromo to promote it to be a forest root
domain, you cannot use the original NT domain name since the domain name
has existed. I have tested and confirmed this point.
They will be totally different domain. Therefore, you need to use ADMT to
migrate the user accounts etc.
5. How will the affect Citrix server farm?
6. There is no DNS involved in this Citrix Server Farm. So, will it be ok?
As we need DNS to for AD.
7. Should I upgrade the Citrix Server farm first?
A: According to my understanding, if you have not cluster, it does not
affect to Citrix server farm. You may consult Citrix support to confirm
this point.
Atucally, if you need to retain the original NT domain name, you need to
find a server which is now running NT BDC and it can be upgrade to Win2k3.
Otherwise, you need use different domain name for win2k3 domain. For
example, if one of the Citrix MetaFrame 1.8 can be upgrade to win2k3, you
can upgrade Citrix MetaFrame 1.8 BDC to PDC and use the upgrade process
described in the article below to upgrade to win2k3:
Why Upgrade from Windows NT 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4town
et.mspx
Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx
Further questions, let us get in touch!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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: Rebecca Chen [MSFT]: "Re: NT4 Print Server ---> Windows Server 2003 Clustered Print Server"
- Previous message: Rebecca Chen [MSFT]: "Re: FSMO roles placement"
- In reply to: John: "Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC"
- Next in thread: John: "RE: Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC"
- Reply: John: "RE: Upgrade of Windows NT 4.0 PDC to Windows Server 2003 DC"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|