Your best bet might be to use some type of software packager/installer to capture the associated registry changes into a .zap or a .msi file. Create a clean workstation with no software installed other than the OS. Configure the IP settings as they currently exist on your network: DHCP-assigned IP & gateway, manually-assigned DNS/WINS. Use this to create your "before" snapshot. Then make the appropriate changes to the network settings and create an "after" snapshot to roll out to your clients. This will obviously require a great deal of testing, especially if your client hardware is not uniform -- different NIC adapters, motherboards, etc. will create different (and often incompatible) registry entries.
Dig deeper on Domain Name System (DNS)
Related Q&A from Laura E. Hunter
Active Directory expert Laura E. Hunter offers some advice for changing the IP addresses of domain controllers.continue reading
A Windows administrator moving from Windows Server 2003 to Windows Server 2003 R2 wants to perform a restore of a previous server to a new one ...continue reading
An admin has two domains and two Active Directories. He wants to know how to join the Active Directories so that internal staff can access both, but ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.