Should be no problem at all.
Make sure that hosts file on all stations doesn't contain a record of your exchange server
In order to clear your PC's DNS client cache, you can re-boot or run ipconfig /flushdns
Main Topics
Browse All TopicsWe run Exchange 2003 Native Mode with a typical DNS infrustructure, dynamic and secure update and DHCP blah.
Well I have an exchange server on a different VLAN in another building. I'm trying to move this server local to the other exchange server on another VLAN
My question is can I RE IP my Exchange Server without any mistakes or trouble from the user?
I don't want to create a CNAME record if thats what you were going to suggest.
I would imagine it would just take time for DNS to replicate the changes but I want to prevent is from everybody having to reconfigure their Oultook because all their profiles have the old IP configured in their profile
What do you think?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
Outlook profiles do not use the IP address of the Exchange server. They rely on DNS and the Exchnage servers NetBIOS hostname. Therefore as long as you don't have any ports locked down between VLANs and you allow time for DNS changes to replicate then you should not have many problems.
It is always likely that some clients will have issues as their cached DNS may not refresh automatically and may need to be flushed using ipconfig /flushdns. However in a situation such as this I always recommend that all client systems that may be affected be re-booted and this normally prevents these kind of issues.
As for the servers once the DNS record is update I would perform a flush dns on all the Exchange servers so that there are no communication issues between them.
You can do this, but I like to do it gently.
Shut down the exchange stores and stop all the services. Change your IP and settings, move your DNS servers to the new subnet (if you are going to) then reboot.
Either manually configure DNS for the new IP, or do it at a time when you have no users online so it can update.
Don't forget to reconfigure any port forwarding on the router!
go with what keiran said, but it is not an issue at all, i have done this more often than i care to remember.
we did this a lot on deployments accross wans when migrating mailboxes to a new server we would move the new bax locally then migrate the mailboxes and then move the server to the new location.
when the server comes up with the new ip, the dns usually takes around 15 or 20 mins to replicate to all DC's but this depends on how many there are and so on.
all you need to do is ensure that the DNS is working correctly.
what is however a complete nightmare on exchange is renaming the server, so just dont do it
Ok I wont rename it haha. But I was afraid that if i change the IP after it gets back to it's new location, the old IP will never release in DNS therefore, a stale record that will need to be deleted manually.
Anyways thanks for the advice, I will close this ticket out tomorrow since I'm about to fall asleep. Had a long night decommisioning a server and moving mailboxes.
Thanks
Some things to keep in mind when changing the IP of a mail server:
If the mail server has an external address, you'll need to modify the MX, A, and PTR records for the external name space.
If the mail server has an internal ip address, you may have to modify your NAT rules to forward port 25 (and any other exchange-related ports being used, 80,110, etc..) to the new IP address.
Business Accounts
Answer for Membership
by: snyderkvPosted on 2008-01-12 at 22:00:34ID: 20646592
How about this.
I simply set the new IP on the Exchange Servers second NIC and set it up with the mac reservation in DHCP. Then I set up another port on the switch to the same old VLAN so clients can continue to use the old VLAN until I'm ready to cut over. by that time the new IP would be registered and replicated in Active Directory. So once I cut off the old IP clients would have to flush their cash or reboot and they would pic up the new IP
?