Exchange 2010 - moving and changing IP addresses

I'm looking to move/vmotion 2 Exchange 2010 servers.
They'd be moving to a new host/datastore in vSphere and would be getting a new IP address on a new subnet, where 3 other Exchange servers have always been. So they're all being united to be one happy family, essentially.

My understanding is that no Exchange changes needed, just changing the IP address in Windows.

One of the Exchange servers being moved (server 1) has roles Mailbox, ClientAccess, HubTransport
The other being moved (server 2) has ClientAccess, HubTransport.

Both of these servers, however, also run OWA/IIS on them, and act as the front end login site for OWA (both internal/external urls)

Is there anything I'd need to do in preparation to support IIS/OWA? I'm reading mixed guides on different commands to run, IIS sections to access IP settings, etc.

My current plan is, before migrating them during the 24 hr maintenance window, to reconfigure their IP addresses/network and test everything, and then vmotion/move them to their new destination. If that's the wrong path, suggestions appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Senior IT System EngineerIT ProfessionalCommented:

I've done virtualised Exchange server 2007 cluster CCR migration from one data center to another in my previous company there was no downtime longer than 15 minutes during the MSCS failover.

Basically yes, you can:
1. Write down the services that Exchange is using then set it as disabled.

2. shutdown the passive node and then Vmotion into new ESXi hosts in the new location.

3. Turn on the VMs and change the IP address manually. From the below sequence:
Windows Node layer
Static routing if any configured using Netsh for heartbeat network.
MSCS (cluster node object)
And then change the services to automatic based on your notes above.

4. Reboot the server and then check the service health. Using any cmdlets that you have like test-service health, replication health, etc...

Once it is successfully running, the. You do the failover to the node above rinse and repeat.

All the best mate.

Let us know how you go.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amit KumarCommented:
1. As you don't have any DAG so cluster is not there, so there will not be any challenge to move Mailbox server.
2. Moving CAS/HUB server is challenge where you need to change DNS record internally and also change NAT on firewall with new IPs to same public IPs.

3. On the other hand see if if you have application servers and those are using HUB server as SMTP relay and if they have IP rather DNS name. so you will have work on it manually.

4. If you have any port restriction for internal infra then you may need to check ACLs in routers/swiches.
garryshapeAuthor Commented:
Good deal thanks guys
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

garryshapeAuthor Commented:
Follow-up question

Do you guys think it'd also make sense to clone the VM then move the clone over, in order to reduce downtime?
Senior IT System EngineerIT ProfessionalCommented:
No, better not to clone Exchange/SQL Server VMs as Microsoft won't support it if anything happens.
Just fail it over to the other DAG nodes.
garryshapeAuthor Commented:
Well I also just realized they don't host maiboxes all they do is run OWA
So I think it may be best to just deploy 2 new exchange servers to serve as OWA
Senior IT System EngineerIT ProfessionalCommented:
Wait.. why not migrating the one node to the other DataCenter and using NLB drainstopping method ?

if you want to deploy 2 new exchange servers (CAS role) to serve as OWA then yes it is fine but more work for you to configure the exchange server layer.
garryshapeAuthor Commented:
Well there are 2 Exchange 2010 servers serving as OWA:

MAIL1: This serves as OWA to an Exchange 2007 Mailbox server
MAIL2: This serves as OWA to an Exchange 2010 Mailbox server

I'm not sure how to migrate a node my understanding is I would just create a new servers in HQ site MAIL3 (Exchange 2007) and MAIL4 (Exchange 2010), then set them as the same internal URL and external URL for Client Access settings and shutdown the other Exchange servers and get rid of them.

Not familiar with NLB drainstopping.
Senior IT System EngineerIT ProfessionalCommented:
Hi garry,

How about create new thread and let us know the new thread URL so that it can attract more people to solve your additional issue / question ?

Do you not use some kind of load balancer for the HUB or CAS server ?
garryshapeAuthor Commented:
sure I'll do a new one

As for load balancer, no there is none, unfortunately.
I inherited the configuration and there was not even a casarray.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.