It certainly confirms a possible condition, but it also details how/why it can happen.
Its a well-known best practice to not put the Infrastructure Master on a Global Catalog Server. This is not a secret, and certainly not something only known to MCSEs. Its written in many books, as well as listed on many websites detailing best practices for the assignment of FSMO roles. There are potentially lots of surprises in store for you. As easy Windows interfaces make things look - its not fool-proof administration, and you still have to have a solid understand of what you are doing in order to avoid pitfalls. I highly recommend a google search of "FSMO best practices <https://www.google.com/search?q=FSMO+best+practices>". IANAMCSE, IANAL, YMMV -- Espi On Sat, Mar 14, 2015 at 9:25 AM, Klaus Hartnegg <[email protected]> wrote: > Am 14.03.2015 um 16:11 schrieb Micheal Espinola Jr: > >> Did you happen to follow the citation link (#6) back to the Microsoft KB >> > > Of course I did, and it appears to confirm it. > > article that was written in 2007? >> > > So what? Windows allows to configure trust without telling about such > unexpected restrictions. The fact that I only know because I happened to > stumble over it makes me nervous. I started to search a list of > prerequisites, but so far didn't find anything. > > >
