I have a virtualized SBS 2008 that I've been trying to spin off of but I just didn't have all of the pieces in place until recently. After a recent windows update, I went to work after that Saturday and there was some odd behavior on the network. I didn't think anything of it because the network has been an adopted nightmare since I inherited it and it just seemed like it was just another punch it was throwing at me. Well 2 weeks after the event I am sitting down to check why a computer won't gpupdate/force (even after leaving the domain and coming back) and I find out that SBS's host restarted while SBS was running and it caused Active directory to stop replicating properly. Now I have over 600 failed replications between DC's and I don't know how to fix it... I have read that if I have the broken DC demote from the forest and then be promoted after replication with any other DC's in the forest and then have it rejoin it would fix itself; but since it is FSMO, I'm worried about seizing FSMO to another DC and having the license timer ticking before I'm ready to roll off of it! Can I seize FSMO to another server then have all 5 roles go back to SBS and end the timer? Is there a better solution to this problem? I am in directory service recovery on the SBS in a test lab but I don't know how to repair AD from here...
↧