Win 2003 DC moving to new office - sanity check

[Guest Barkley Bees]

We have two main Offices - A and B. Office A is where our main DC is located

(Windows 2003 Domain native mode, single forest, single site - GC, DHCP,

WINS, DNS). Site B also has a DC (GC, WINS, DNS - No DHCP). The two sites

are connected by IPSec VPN tunnel (30MB bandwidth).

 

Office B is moving to a new location that will be getting a new address

range so I will need to move the DC. It seems simple enough but I was hoping

to get a sanity check on my planned process below:

 

Day 1

- Run DCPromo on Office B DC to demote it to a member server.

- Remove from Domain.

- Rename (to follow naming convention for new office).

- Shutdown server.

- Allow ~16 hours for all changes to replicate.

 

Day 2

 

- Physically move server to new site.

 

Day 3

 

- Power on DC at new Office and configure new IP.

- Join to Domain.

- Configure WINS.

- DCPromo "additional DC for existing domain"

- Set as GC.

- Configure & verify DNS.

- Configure & verify WINS replication.

 

 

*note: all client PC's are configured to talk to the DC's at Office A for

DNS, WINS, DHCP.

 

Thanks all.

[Guest Meinolf Weber]

Re: Win 2003 DC moving to new office - sanity check

 

Hello barkley,

 

There is no need for removing the server from the domain, if you just will

change the name. This can also be done by a member server. For the clients

DNS i would set the site DNS server as preferred and the other as secondary.

If the link to the other office will be down no one can login.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> We have two main Offices - A and B. Office A is where our main DC is

> located (Windows 2003 Domain native mode, single forest, single site -

> GC, DHCP, WINS, DNS). Site B also has a DC (GC, WINS, DNS - No DHCP).

> The two sites are connected by IPSec VPN tunnel (30MB bandwidth).

>

> Office B is moving to a new location that will be getting a new

> address range so I will need to move the DC. It seems simple enough

> but I was hoping to get a sanity check on my planned process below:

>

> Day 1

> - Run DCPromo on Office B DC to demote it to a member server.

> - Remove from Domain.

> - Rename (to follow naming convention for new office).

> - Shutdown server.

> - Allow ~16 hours for all changes to replicate.

> Day 2

>

> - Physically move server to new site.

>

> Day 3

>

> - Power on DC at new Office and configure new IP.

> - Join to Domain.

> - Configure WINS.

> - DCPromo "additional DC for existing domain"

> - Set as GC.

> - Configure & verify DNS.

> - Configure & verify WINS replication.

> *note: all client PC's are configured to talk to the DC's at Office A

> for DNS, WINS, DHCP.

>

> Thanks all.

>