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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
Do you guys think it'd also make sense to clone the VM then move the clone over, in order to reduce downtime?
Garry,
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.
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.
ASKER
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
So I think it may be best to just deploy 2 new exchange servers to serve as OWA
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.
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.
ASKER
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.
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.
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 ?
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 ?
ASKER
sure I'll do a new one https://www.experts-exchange.com/questions/28712311/Migrate-OWA-servers-2007-and-2010.html
As for load balancer, no there is none, unfortunately.
I inherited the configuration and there was not even a casarray.
As for load balancer, no there is none, unfortunately.
I inherited the configuration and there was not even a casarray.
ASKER