![]() I’ve done a large migration of domain controllers before and used Wireshark to help identify systems that are still pointing to old domain controllers. The packet capture shows that system 192.168.100.22 is using DC2 for DNS. This might be the most important pre-change step. Wireshark can help you identify what systems are pointing to your domain controller for various services like DNS, DHCP, and so on. Find Devices Pointing to the Domain Controller with Wireshark I’ll need to consider this when changing IP addresses. You can quickly check the installed roles and features with this command: Get-WindowsFeature | Where-Object īelow you can see my DC2 server has some critical services running on it including DHCP and DNS. Check the control panel for installed software.I recommend checking what services are running on the server, you don’t want to change the IP and then have something break because you didn’t know it was a DHCP server or a web server. I’m making changes to DC2 which has no FSMO roles running on it. Keep in mind you would need to move any services that are manually configured to the server. To help avoid disruption to authentication services you could move the FSMO roles to another domain controller that is on the same site. You can get a list of all domain controllers in your domain with this command: Get-ADDomainController -filter * | select hostname, domain, forest Check FSMO Rolesĭoes the DC hold any FSMO roles? Easily check with this command: netdom query fsmoīelow you can see all my FSMO roles are on DC1. If you have multiple DCs and the change breaks the server you can still operate from a secondary DC. I do not recommend making major changes to domain controllers if you have a single domain controller. It is best practice to have multiple domain controllers and backup Active Directory for disaster recovery reasons. If you do this often you will probably come up with your own checklist. I’ve migrated many domain controllers from small to large networks and these steps have been a lifesaver. I recommend reviewing each item on this checklist before making changes. If you are changing to a different subnet there are additional things to consider that I go over in the checklist. See my checklist below.įor this demonstration, I have the following settings. Any changes to a domain controller can disrupt services and impact business operations. In this post, I will demonstrate how to change the IP address on a domain controller.īefore you change the IP address it is very important to run through a checklist. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |