BDC not working like PDC

[Mark]

A while ago I created a BDC (Windows 2000) using the
wizard and now I have a copy of my AD on it. I can make
changes to AD on the PDC and it replicates to the BDC with
no problem. As a test, I shut down the PDC to test the BDC
and the following happened.

1. Users could log into AD but very slow, 2 to 3 times as
long to load their roaming profile.

2. Very slow to access Terminal Server and connect to
applications on it.

3. Users lost the ability to connect to our Exchange
Server 2000.

I then realized that the PDC was set as a Global Catalog
Server by default but the BDC was not. I checked on GCS on
the bdc, let it replicate and now the following happens.

1. Users can still log into the AD on the BDC (PDC down)
but still slow but does authenticate. Not nearly as fast
as the PDC.

2. TS apps run OK and I can now get access to mail using
Outlook 2000 but really slow. I received many calls from
users that they lost the ability of Outlook 2000 but I was
able to connect to the mail server during my tests.

Does anyone know exactly what to do to make a BDC (Windows
2000) perform exactly like a PDC (Windows 2000)? I want it
to be as fast as the PDC and connect to all apps and
resources and be available should my PDC go down.

Please help,

Thanks,
Mark

 

[Frank]

Mark,

There is no BDC or PDC's in Windows 2000.

Frank

 

[Hindy]

Mark,

Windows 2000 uses a mulit-master approach to DC's - there
are no PDC's and BDC's like in NT4 as all are equal.

However, you need to look into the Flexible Single Master
Operations Roles (FSMO). This is whats likely to be
causing your problems. One of these roles is the PDC
Emulator role (not emulator - it emulates the NT PDC).

Read this for starters:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;197132