Introducing 2003 server into Win2000 Domain

[Mark]

Hi
I'm looking for some information on what I need to do to introduce Win2003
servers as BDC's
in a Win2000 AD Domain. If someone could point me to some information it
would be great.
Thanks
Mark

 

[Jordan]

325379 How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

More information is available in
http://www.microsoft.com/windowsserver2003/upgrading/default.mspx

In 2000/2003, there's no PDC/BDC kind of concept. All DCs are master (except
for those FSMOs).
There is no issue in 2000/2003 co-existence but if you have custom
applications, it's better to perform some test before upgrading. And
remember to perform a complete backup before you jump into it.

 

[Eric Fleischman [MSFT]]

Jordan is on the money. I'd also add that we often recommend moving the PDCe
and domain naming roles to 2k03 once they are in the environment. Reason
being, PDCe being 2k03 will add the new well known security principals when
it picks up the role, and the domain naming being 2k03 will allow the
creation of app partitions.

~Eric

 

[Andrew Holmes]

I thought we dropped the PDC model when we moved away from the NT4.0 domain
model ... a FSMO --- Collabrative mode...

 

[Cary Shultz [A.D. MVP]]

Andrew,

In Active Directory there are the five FSMO Roles. There are two
forest-wide roles and three domain-wide roles.

The two forest-wide roles are the Schema Master and the Domain Naming
Master. There is only one DC in the entire forest that can hold each of
these roles ( naturally, one DC can hold all five of them - but that is for
another question ).

The three domain-wide roles are the PDC Emulator, the RID Master and the
Infrastructure Master. You will have each of these three in each domain in
the forest. So, if you have three domains you would have the three roles
for domain1, the three roles for domain2 and the three roles for domain3.

The role of the PDC Emulator is somewhat special and very important. The
key word in that role is "Emulator". Should you be in Mixed Mode and have
any WINNT 4.0 Backup Domain Controllers it is the WIN2000 Domain Controller
that holds the FSMO Role of PDC Emulator that 'speaks' to the BDCs. There
are several other functions that the DC with the role of PDC Emulator plays.

HTH,

Cary

 

[ptwilliams]

Further to Cary's excellent information, here's an article that describes
what each FSMO role does:
-- http://www.msresource.net/kb/fsmoroles.html


And here's an article on how to move them (there's also some links to MS KBs
at the end of this):
-- http://www.msresource.net/kb/moveFSMOroles.html


The first article mentioned briefly covers placement.

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


Andrew,

In Active Directory there are the five FSMO Roles. There are two
forest-wide roles and three domain-wide roles.

The two forest-wide roles are the Schema Master and the Domain Naming
Master. There is only one DC in the entire forest that can hold each of
these roles ( naturally, one DC can hold all five of them - but that is for
another question ).

The three domain-wide roles are the PDC Emulator, the RID Master and the
Infrastructure Master. You will have each of these three in each domain in
the forest. So, if you have three domains you would have the three roles
for domain1, the three roles for domain2 and the three roles for domain3.

The role of the PDC Emulator is somewhat special and very important. The
key word in that role is "Emulator". Should you be in Mixed Mode and have
any WINNT 4.0 Backup Domain Controllers it is the WIN2000 Domain Controller
that holds the FSMO Role of PDC Emulator that 'speaks' to the BDCs. There
are several other functions that the DC with the role of PDC Emulator plays.

HTH,

Cary