antony said:
Dear peter
Thanks for your reply.I did a pilot test like,installed
nt 4.0 bdc on a new server and join to the existing
PDC.Once synchronise user and computer acoounts,Isolate
the BDC and upgrade to PDC.Then Upgrade the PDC agin to
windows 2003 server DC. And change the DC name by using
Rendom tool(our exiting domain name is company_nt our
feuture Domain name must be ug.company.com.
Now I am trying to pilot migration of the exchange.I am
trying to impliment as like u said A root dc+dc+member
e2003
Please letme know any other precuation I have to take
before going for acctual migration
Thank you
Your wellcome. You need to consider a few issues before proceding in this
manner. The first involves the domain name based on "ug.company.com"
strategy. This is why i suggested looking more closely into DNS.
http://www.microsoft.com/windows2000/techinfo/howitworks/communications/name
adrmgmt/w2kdns.asp
This dns name says: the internet root recognizes that the second-level
domain called "com" knows about a zone "company.com" which is authoritative
for a child domain called "ug.company.com". This may (or may not) have
implications as far as name resolution in a namespace if no parent domain
"company.com" exists.
The next problem lies with disecting a BDC from an NT4 domain and then
isolating and promoting it. In the NT4 or W2K world, names mean nothing. Its
the SIDs that matter. This is critical for nt-based clients which rely on
SIDs, not domain names to be authenticated. So if you attempt to join a
different domain that has the same SID as another, guess what?
The recommended approach is to disable a BDC (for a recovery plan) and then
to upgrade the PDC of your existing NT4 domain. Needless to say, a thorough
compatibility check (software and hardware) is part of the upgrade procedure
(run winnt32 /checkupgradeonly).