I haven't done this yet with production servers,
but in MCSE class were I teach we change IP addresses many times, and it normaly works...
Here are some tips, most of them obvious but anyway:
* Make sure you have a good backup, it is good to backup the "System State" to a file with W2K own backup before changes, and not only using your 3rd party tape backup.
This helps with fast resrotres.
* Make sure DNS works fine.
* Check event viewer now, restart the servers and check event viewer before any changes, and ofcourse check again after changes.
* Check that AD users and computers, and the other 2 AD management consoles from Administrative Tools work fine.
* Document your TCP/IP network. Note especially manualy configured IP addresses and options.
Don't forget all devices and programs like printers, SQL clients (or other ODBC clients manualy configured with server IP address).
* Remeber that some changes must be done in the FireWalls, Routers, ISP DNS registrations, and so - make sure every one knows what he should do.
* The change itself should be quite simple - change the IP on all servers, make sure to set also other TCP/IP options, like DNS . Restart all servers to make sure.
* Change DHCP scopes and options.
* Change any manualy configured IP clients and programs.
* If you use NAV CE antivirus, the clients will not find their parent server. You'll need to do the GRC.DAT trick or to uninstall and reinstall the clients.
Reply with your comments afterwords so we can learn also...
Also when you change it you may want to run from cmd ipconfig /registerdns to force the server to register its new IP, also check that any services that run on the DC that it reflects the new IP , such as DNS or WINS....and depending on the size and qty of DC's you will want to run and force the replication of the AD so all
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.