Windows Forum

Ask something
Discussion Locked

BDC is not functioning after removing fr

0 helpful
8 replies

by vuitanh

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm setting up a NT 4.0 test environment, which I brought up a BDC on the regular network, synced with the PDC, checked the log for succesfully synced, and remove from the network. After removing from the network the SAM database isn't there, which mean I can't go to Domain User Manager or Server manager. What is the problem here and how can I fix it?

8 replies

by ntoz

Actualy your sam database is there, in order to connect to your BDC in a test enviroment, you need to promote it to a PDC. User Manager for domains only talks to a PDC. In windows 2000 this was address by making it possible to update any domain controler, in windows 2000 your still stuck with connecting to a PDC. Remeber you should not return your BDC to the regular network until you have forced it back to being a bdc.

Pete

by ntoz

Let me rephrase this as looking it over, it doesnt make sense, sorry. In short:

In Windows NT 4.0 the domain controler has to be a PDC in order to use User Manager

In Windows 2000 you can update any domain with account changes out side of special needs like updates to the directory its self.

Pete

by ashuras

I suppose this is a straigtforward question, although BDC is still able to authenticate user, only PDC is allowed to do changes in User Manger.

Just need to promote your BDC to PDC, but when connecting back to network may have slight problem, as 2 PDCs occur.

by rvkempen

Promote it to a pdc using server manager, this is the same situation as when your pdc went down.
When having to put it back to your original network, when you start it up, your original pdc will demote itself, so be carefull, as it will sync all the changes you've made at your original bdc, which you upgraded.
There really is no point in promoting a bdc unless your pdc goes bang.
You never want to have two similar sites to manage, put them in different domains instead, and use trusts.

Good luck.

Ron.

This discussion is closed to new replies.