There's no simple way to do it. I would recommend breaking it into two phases, if possible: changing the names, and changing the IP addresses. Change the names while you're still in your current location. No doubt you'll run into problems that you need to troubleshoot, but it's going to be much easier to troubleshoot when you're not in the middle of the move, because there will be fewer factors to take into account. Read these links from the Server 2003 help files for detailed guidance:
If you are currently using DHCP, changing your IP addresses won't be that bad. First, plan out the static IP addresses for your domain controllers, DHCP servers, DNS servers, and any other server. Move your network equipment over first, reconfigure it, and make sure it's all working. Then, move over your DHCP servers, and reconfigure them for the new network. Be sure they're handing out new IP addresses for the gateways and name servers. Move over your DNS servers and change the static DNS addresses you have -- don't worry about computers that use dynamic DNS. Then, move over your domain controllers and other servers. Finally, move over your client computers.
If you're not currently using DHCP, this would be an excellent time to switch to it. You're going to have to reconfigure all your client computers, anyway, and DHCP will make it much easier as your users start using more laptop computers and networked PDAs.
The domain profiles should be fine -- they're not dependant on IP addresses or names, but rather a unique Security ID (SID) that will stay with the computer through the move.
Dig deeper on Windows Operating System Management
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.