Active Directory: Flexible Single-Master Operations (FSMOs) скачать в хорошем качестве

Active Directory: Flexible Single-Master Operations (FSMOs)

Back to Active Directory! Because even though AD uses a multi-master model these days, there are some jobs that just shouldn't be done by multiple machines. And this is where we get the FSMOs! I know this one has a lot of talking in it, and some parts of it get pretty complex. But understanding why the FSMOs exist, and how they function, starts to become pretty important as you start working with larger domains and forests. So hopefully this breakdown helps out with that! EXTRA CREDIT: There was a time where I would make sure that I always had one DC that was not a Global Catalog, specifically so I could have a "correct" place to put the Infrastructure master. In retrospect, that was an example of "cargo cult administration," or doing things without understanding why I was doing them. :) For smaller networks, the most important FSMO to look after is the PDC Emulator. And one of the most important things to do on the PDC-E is making sure it has external time sync set up correctly, especially if you're trying to interoperate with other devices that also keep their own time sync. Don't register the Schema Management snap-in just so you can use the GUI to transfer the FSMO, like I used to. It's not worth it, honestly. :) Just use the Move-ADDirectoryServerOperationMasterRole cmdlet in PowerShell instead! One command to do all the work, rather than fiddling with three separate GUIs.