Moving FSMO roles & AD Sites & Services Bridgehead roles (IP & SMTP)???
Hi, I am working migrating my FSMO roles from old Server 2008 R2 to my new Server 2016.
While in preparation, I was wondering about the AD Sites & Services Bridgehead role (IP & SMTP) for said servers.
From this forum discussion, it is automatically assigned? And there is really no need to manually switch it?
https://social.technet.microsoft.com/Forums/WINDOWS/en-US/100af9ac-3602-4da6-b705-880ced094b6e/do-i-remove-ip-or-ip-and-smtp-in-my-bridgehead-under-sites-and-services?forum=winserverDS
However, my plan is obvious, that I am migrating everything off of my old Server 2008 R2 to my new Server 2016 in order to decommission my old Server 2008 R2 domain controller.
So, if I migrate the FSMO roles from my old Server 2008 R2 domain controller to my new Server 2016 domain controller will AD Sites and Services reflect the changes in the Bridgehead role too? Or do I need to manually move those from my old Server 2008 R2 domain controller to my new Server 2016 domain controller?
Or do I even need to consider this part?
I do have physical domain controllers (Server 2008 R2) still at 3 branch sites. I plan to replace them with virtual machine Server 2016 domain controllers that will reside at my main branch site, but will service the branch sites via VLAN's, etc.
If I do need to move these Bridgehead roles, should I add the roles to the new Server 2016 domain controller first then remove it from my old Server 2008 R2 domain controller or vice versa?
Thanks in advance.
While in preparation, I was wondering about the AD Sites & Services Bridgehead role (IP & SMTP) for said servers.
From this forum discussion, it is automatically assigned? And there is really no need to manually switch it?
https://social.technet.microsoft.com/Forums/WINDOWS/en-US/100af9ac-3602-4da6-b705-880ced094b6e/do-i-remove-ip-or-ip-and-smtp-in-my-bridgehead-under-sites-and-services?forum=winserverDS
However, my plan is obvious, that I am migrating everything off of my old Server 2008 R2 to my new Server 2016 in order to decommission my old Server 2008 R2 domain controller.
So, if I migrate the FSMO roles from my old Server 2008 R2 domain controller to my new Server 2016 domain controller will AD Sites and Services reflect the changes in the Bridgehead role too? Or do I need to manually move those from my old Server 2008 R2 domain controller to my new Server 2016 domain controller?
Or do I even need to consider this part?
I do have physical domain controllers (Server 2008 R2) still at 3 branch sites. I plan to replace them with virtual machine Server 2016 domain controllers that will reside at my main branch site, but will service the branch sites via VLAN's, etc.
If I do need to move these Bridgehead roles, should I add the roles to the new Server 2016 domain controller first then remove it from my old Server 2008 R2 domain controller or vice versa?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Echoing on what Paul said, The Ability to select a Bridgehead in AD is a relic of old days when you had really bad WAN connectivity and things like an ISDN BRI or Dialup modems were common (56K). At that time, you could have a slower link that was more reliable than a faster link but AD may not see it. So you wanted to control how you communicated between sites. With WAN speeds and reliability now, it is usually ignored. AD does a good job selecting it and an handle outages better.
ASKER
That's pretty nifty.
However, what if there will be three Server 2016 domain controllers (two virtual machines) and one physical (will host the FSMO roles) after demoting all of my old existing Server 2008 R2 domain controllers?
Will the Bridgehead roles go to the correct Server 2016 domain controller (aka FMSO role holder (PDC)) remaining in my AD environment?
Thanks again.