Bob the PDC\BDC was in NT 40. There are is no PDC\BDC from win2000 on. Every DC is just a DC. There are different roles a DC can have. One of the 5 FSMO roles. A DC can be a GC, or DNS server as well. In your senario if server1 was down and you created a user in AD it should sync right back up with server1 when it comes online unless server1 was offline longer than the tobmstone lifetime. In this case you will need to do a metadata cleanup in AD to clean server1 out. Then do a clean rebuild of server1 and re-promote to DC. If the server was only down when you created the user and it does not sync when it comes back online then you have some replication issues you must look into. Are both of your DC's GC, Do they both have AD int. DNS? How are the DNS settings on the servers configured? What are the results if you run DCDiag? What are the results if you run repadmin?
On Sat, Mar 7, 2009 at 10:22 AM, Bob Muzzy <[email protected]> wrote: > > > > > Scenario: I take server1, a 2003 AD PDC, offline and create a user on > server2, a BDC (I know, that's not what MS calls them today, but that's the > way they work...) then bring server1 back online. > > > > > > > > Question: how to synchronize ADUC on both DCs. currently server1 doesn't > know about the addition to server2. Can this be done simply i.e. largely > automatically, without wading deep into ntdsutil.exe? I suppose I could > dump all user info from server2 to a .cvs file and import it onto server1. > Somehow I thought the update # for the user creation on server2 should be > higher that that on server1 such that it would automatically sync, no? > > > > > > > > Thanks, > > > > > > > > Bob Muzzy > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ > ~ ~ > > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ ~ <http://www.sunbelt-software.com/product.cfm?id=400> ~
