S
shima111970
Good morning,
In the near future I will be updating our Server 2012 R2 domain controllers to new ipv6 addressing. We are moving away from our providers /48 block and going with our own /48 so we don't have to change system ipv6 addresses down the road. With that said, I am trying to think of the best way to update our DC’s to the new addresses. We have 3 sites with a primary and secondary DC at each site. There are 2 possible courses of action I can think of:
1) Starting at the first site Re-ipv6 address the DC's and update DNS pointers. Will this work with no replication problems considering I have to move routing, firewalls, core switch svi's, and distribution switching prior to changing to the new DC ipv6 addresses? During this update ipv4 connectivity will remain active.
2) Backup ipv4 DHCP scope for the primary, demote, shutdown, and remove the DC's from the site I am working with, and then ip updated 2012 R2 servers, promote them, and re-import DCHCP to the primary, then check dcdiag, repadmin, and make sure replication is working.
Thanks for any help with this somewhat messy question.
Continue reading...
In the near future I will be updating our Server 2012 R2 domain controllers to new ipv6 addressing. We are moving away from our providers /48 block and going with our own /48 so we don't have to change system ipv6 addresses down the road. With that said, I am trying to think of the best way to update our DC’s to the new addresses. We have 3 sites with a primary and secondary DC at each site. There are 2 possible courses of action I can think of:
1) Starting at the first site Re-ipv6 address the DC's and update DNS pointers. Will this work with no replication problems considering I have to move routing, firewalls, core switch svi's, and distribution switching prior to changing to the new DC ipv6 addresses? During this update ipv4 connectivity will remain active.
2) Backup ipv4 DHCP scope for the primary, demote, shutdown, and remove the DC's from the site I am working with, and then ip updated 2012 R2 servers, promote them, and re-import DCHCP to the primary, then check dcdiag, repadmin, and make sure replication is working.
Thanks for any help with this somewhat messy question.
Continue reading...