Jump to content

Moving DC/Exchange to new Site


Recommended Posts

Posted

Looking for some expert advice here on a move that I am going to be

making. Trying to avoid any problems. We are in the process of

keeping many roles on one server to spreading them out. In the

process we are moving production into a data center.

 

All are running 2003 r2, fully patched. Exchange is 2003 as well,

fully patched.

 

Site 'Main' in AD. 192.168.2.0 network

Main office we have 3 servers.

Server A - DC/DNS/GC/Exchange/File (All Op Masters)

Server B - BES

Server C - DC/DNS/GC/Print

 

Site 'Data' in AD 192.168.8.0 network

This is the new Site

Server 1 - DC/DNS/GC

 

Site 'Branch' in AD 192.168.4.0 network

Server X - DC/DNS/GC

Nothing happening in this site or with this server.

 

The three sites are connected via firewall site to site vpn's.

Circuits are T1's. Site's Main and Data are not physically far from

each other.

 

I need/want to move Server A from site Main to site Data. Will also

be moving Server B. Server C is staying at Main. I've been doing

some looking into what all I will need to do to pull this off, but

want some advice please.

 

Here is what I am thinking.

1. Stop Exchange services. Set to manual.

2. Move the server from Main to Data in Site and Services.

3. Change the IP settings.

4. Power down and move to new location.

5. Power up and verify DNS records.

6. Bring up exchange services. Set back to automatic.

6. Verify replication with old site.

7. Run netdiag and dcdiag to verify all is well.

 

Does that sound right? Missing anything? How is my order? Should I

stop netlogon before moving in Sites and changing IP?

 

Any MS KB's or other articles you can point me to would also be

appreciated.

 

thanks in advance.

  • Replies 2
  • Created
  • Last Reply

Popular Days

Guest Mathieu CHATEAU
Posted

Re: Moving DC/Exchange to new Site

 

Hello,

 

You may wait for AD replication before changing ip address. the KCC runs

every 15 minutes, that sould be ok.

 

By the way, Exchange on DC is BAD.

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"Rick" <txjeepers@yahoo.com> wrote in message

news:1191275587.377170.112300@19g2000hsx.googlegroups.com...

> Looking for some expert advice here on a move that I am going to be

> making. Trying to avoid any problems. We are in the process of

> keeping many roles on one server to spreading them out. In the

> process we are moving production into a data center.

>

> All are running 2003 r2, fully patched. Exchange is 2003 as well,

> fully patched.

>

> Site 'Main' in AD. 192.168.2.0 network

> Main office we have 3 servers.

> Server A - DC/DNS/GC/Exchange/File (All Op Masters)

> Server B - BES

> Server C - DC/DNS/GC/Print

>

> Site 'Data' in AD 192.168.8.0 network

> This is the new Site

> Server 1 - DC/DNS/GC

>

> Site 'Branch' in AD 192.168.4.0 network

> Server X - DC/DNS/GC

> Nothing happening in this site or with this server.

>

> The three sites are connected via firewall site to site vpn's.

> Circuits are T1's. Site's Main and Data are not physically far from

> each other.

>

> I need/want to move Server A from site Main to site Data. Will also

> be moving Server B. Server C is staying at Main. I've been doing

> some looking into what all I will need to do to pull this off, but

> want some advice please.

>

> Here is what I am thinking.

> 1. Stop Exchange services. Set to manual.

> 2. Move the server from Main to Data in Site and Services.

> 3. Change the IP settings.

> 4. Power down and move to new location.

> 5. Power up and verify DNS records.

> 6. Bring up exchange services. Set back to automatic.

> 6. Verify replication with old site.

> 7. Run netdiag and dcdiag to verify all is well.

>

> Does that sound right? Missing anything? How is my order? Should I

> stop netlogon before moving in Sites and changing IP?

>

> Any MS KB's or other articles you can point me to would also be

> appreciated.

>

> thanks in advance.

>

Guest Tarun Arora
Posted

Re: Moving DC/Exchange to new Site

 

Hello Rick,

 

I will Backup the server first and possible do a test restore before a

server is physically moved from one location to another.

 

I will also verify that KCC\ISTG has established new replication partners

correctly and review inter-site link costs just to make sure they are still

relevant and up to date.

 

Make sure one DC has enough capacity to cater all users in Main site.

 

Regards,

-Tarun

 

"Rick" <txjeepers@yahoo.com> wrote in message

news:1191275587.377170.112300@19g2000hsx.googlegroups.com...

> Looking for some expert advice here on a move that I am going to be

> making. Trying to avoid any problems. We are in the process of

> keeping many roles on one server to spreading them out. In the

> process we are moving production into a data center.

>

> All are running 2003 r2, fully patched. Exchange is 2003 as well,

> fully patched.

>

> Site 'Main' in AD. 192.168.2.0 network

> Main office we have 3 servers.

> Server A - DC/DNS/GC/Exchange/File (All Op Masters)

> Server B - BES

> Server C - DC/DNS/GC/Print

>

> Site 'Data' in AD 192.168.8.0 network

> This is the new Site

> Server 1 - DC/DNS/GC

>

> Site 'Branch' in AD 192.168.4.0 network

> Server X - DC/DNS/GC

> Nothing happening in this site or with this server.

>

> The three sites are connected via firewall site to site vpn's.

> Circuits are T1's. Site's Main and Data are not physically far from

> each other.

>

> I need/want to move Server A from site Main to site Data. Will also

> be moving Server B. Server C is staying at Main. I've been doing

> some looking into what all I will need to do to pull this off, but

> want some advice please.

>

> Here is what I am thinking.

> 1. Stop Exchange services. Set to manual.

> 2. Move the server from Main to Data in Site and Services.

> 3. Change the IP settings.

> 4. Power down and move to new location.

> 5. Power up and verify DNS records.

> 6. Bring up exchange services. Set back to automatic.

> 6. Verify replication with old site.

> 7. Run netdiag and dcdiag to verify all is well.

>

> Does that sound right? Missing anything? How is my order? Should I

> stop netlogon before moving in Sites and changing IP?

>

> Any MS KB's or other articles you can point me to would also be

> appreciated.

>

> thanks in advance.

>


×
×
  • Create New...