Any Gotchas Shutting Down Colo for a Short Term to Move
We (WAN is four locations throughout the US) are in the process of moving from one ISP to another to get more bandwidth. This will necessitate shutting down the ESXi box at the old location which holds top level Windows 2012 (Not R2) servers for:
Domain Controller
Trend Micro
WSUS Server
DFS Server
Then moving to it's new location in a different stat and bringing it back online.
What steps should we take to assure a smooth transition?
Any gotchas we need to be concerned about, specifically the DC?
Domain Controller
Trend Micro
WSUS Server
DFS Server
Then moving to it's new location in a different stat and bringing it back online.
What steps should we take to assure a smooth transition?
Any gotchas we need to be concerned about, specifically the DC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you do not have Exchange (looks like not), I agree - no big issue if done in an orderly way. I have done this a couple of times for clients (without Exchange) and everything came back up as it was supposed to.
ASKER
Thanks John,
Sounding better all the time.
One of the guys thought we would have an issue with FSMO's.
Hopefully it will be accomplished in two days or less.
Sounding better all the time.
One of the guys thought we would have an issue with FSMO's.
Hopefully it will be accomplished in two days or less.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for pjam's comment #a40892163
for the following reason:
Andrew,
Thanks, hopefully this will cool fevered brows.
Accepted answer: 0 points for pjam's comment #a40892163
for the following reason:
Andrew,
Thanks, hopefully this will cool fevered brows.
ASKER
don't like this new interface. Hopefully I have done this correctly
ASKER
Updated Info FYI
I thought I would update you to what transpired. The ESXi server containing the DC, AV Server, Reputation Server and the DFS Server were removed from the rack for transportation to new location toward the end of the day yesterday. Our Outlook at all four sites stopped working even though we could ping the Exchange Server. Apparently since we are a subset of the parent company the Messaging supplier had only created a trust between that DC and the parent company. In order to change the trust to one of the secondary DCs they will need to bring own the parent company (over 40,000 clients compared to our 700 or so).
It also caused havoc here with our two T1s because the clients could not get updates from the AV Server.
Moved the ESXi back into the rack and working on plan B.
I thought I would update you to what transpired. The ESXi server containing the DC, AV Server, Reputation Server and the DFS Server were removed from the rack for transportation to new location toward the end of the day yesterday. Our Outlook at all four sites stopped working even though we could ping the Exchange Server. Apparently since we are a subset of the parent company the Messaging supplier had only created a trust between that DC and the parent company. In order to change the trust to one of the secondary DCs they will need to bring own the parent company (over 40,000 clients compared to our 700 or so).
It also caused havoc here with our two T1s because the clients could not get updates from the AV Server.
Moved the ESXi back into the rack and working on plan B.
ASKER
We are changing the IP number, but not at first. We will be running in tandem for a period.