Changes like this typically make me nervous. The help files I have found are very clear, and the solution seems just as clear, but the consequences of being wrong are extreem.
Basically, I have a small AD forest with several servers, two of which are Domain Controllers. DC1, now holds all of the typical roles AD uses: Schema Master, Domain Naming master, RID, PDC emulator master and Infrastructure master.
According to my research, the Infrastructure master should never be on the same DC as the Global catalog unless there is only one DC. In my case, I have two DC's on one domain (the only Domain I have for now), with another comming online in a new domain in the same forest. So, this will be one forest, two domains, the root with the two original DC's mentioned above, and the third DC in the proposed domain, now in testing.
My logical conclusion is that, as I move into adding and testing this new domain, I really ought to move the Infreatructure master over to DC2 in the Root domain.
My only real problem here is... to me this is a big scary thing! I envision system wide failure, total loss of communication and me looking for a new job all because I messed with something that, by the books seems easy, but I have never done before and don't fix what ain't broke! .
...But the adult in me says: this is all nonsence. I am sure it is a seamless process that can be done without a hitch and infact should be done because it is the right way to go.
This brings me to you...
Should I move the Infrastructure Master role?
If I do, will it cause any problems, interuptions or require a reboot of my major systems once I select "OK"?
As far as I can tell, my AD network seems to be working fine so, once I bring the new Domain on line, how important is this recomended move?
Thanks in advance...