Thanks Ken i know i was vague but if i detailed the whole thing i'd be here for weeks.
Basically, the problem dc is not replicating to any other dc's other than in the same site. However i have been able to transfer the role, but other sites in the domain haven't picked up the change yet. I noticed today that the bridgehead for the site is the failed dc, so i have made the new one the bridgehead and hopefully this will help replication to the other dc's in other sites (touch wood) The flip side to this problem is that the dc is an exchange 2k server as well and the guys in Tampa are reluctant to migrate the users to Melbourne, FL until they get their new link up in a few weeks time. But this may have to force the issue. Thanks for your help. From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Friday, 15 May 2009 12:24 PM To: NT System Admin Issues Subject: RE: PDC Emulator help You can probably fix this with less effort than what I'm detailing below (depending on whether the problem is with replication, what's in AD, what's in DNS etc). I'm not sure what you've already investigated etc, but there's no real information in your post to isolate the problem. To completely nuke the issue you can: - Verify that your new candidate DC is replicating properly with other machines in the environment - Stop the problem DC from replicating to other DCs - If required, seize the FSMO role onto the new DC (verify in AD, e.g. using ntdsutil, who is the PDCe role holder) - DCpromo the problem DC out of the domain - Force replication from the new FSMO role holder out to other DCs - Ensure that DNS is updated correctly (service record registered to point to new DC) Cheers Ken ________________________________ From: Greg Mulholland [g...@krystaltek.com] Sent: Friday, 15 May 2009 10:04 AM To: NT System Admin Issues Subject: PDC Emulator help We are running a windows 2000 native domain. After some major issues with our PDC emulator (win2k) ie machines in other sites could not replicate with it, the pdc role has been transferred to another win2k dc in the same site. The problem now is that other dc's in other sites still think the pdc emulator is the old one. Anyone have any ideas of how i can force these other dc's to sync or look at the right pdc. There are 3 win2k dc's and the rest are win2k3 Greg ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
