Best process for seting up remote DC?

[Hank Arnold]

We have a single forest/domain with two subnets (192.168.1.x &
192.168.100.x) connected via a WAN/T1. Currently all servers are in the main
site (192.168.1). We have two DC's (both GC's) currently running in the main
subnet. I want to add a DC with DNS but no DHCP in the remote subnet. DHCP
is currently provided by a 3Com Router.

For practical reasons, I need to set it up in the main site and then move
it. I want to be sure that the users in the 192.168.100 subnet use the new
DC as their primary logon server and make sure that users in the 192.168.1
subnet use the two local DC's first before trying to use the one over the T.

Is there a "best process'" type of documentation for accomplishing this?

TIA.

 

[Tomasz Onyszko [MVP]]

We have a single forest/domain with two subnets (192.168.1.x &
192.168.100.x) connected via a WAN/T1. Currently all servers are in the main
site (192.168.1). We have two DC's (both GC's) currently running in the main
subnet. I want to add a DC with DNS but no DHCP in the remote subnet. DHCP
is currently provided by a 3Com Router.

For practical reasons, I need to set it up in the main site and then move
it. I want to be sure that the users in the 192.168.100 subnet use the new
DC as their primary logon server and make sure that users in the 192.168.1
subnet use the two local DC's first before trying to use the one over the T.

Is there a "best process'" type of documentation for accomplishing this?

Do You have sites (at AD level) and subnets created to reflect Your
network topology - in general (from Your description) You will need at
least two sites in AD, one for main location and second for the other
location connected with this T1 link.

you can setup and promote Your DC in main location, then deliver
(physically) machine to remote location and in AD You have to move this
machine from Default first site (or whatever is called your main site)
to the site for this remote location (You can move DC using AD Sites and
Services snap-in).

Users will first look for DC's in its local network - if they will find
one they will use it, if not they will try to find DC in other sites.

That's in short word

 

[Hank Arnold]

Thanks, Tony.... much appreciated. Would you think this is something that I
should do on or off shift? I can't allow *any* disruption to operations....

Hank

 

[Hank Arnold]

Sorry about that.... Tomasz... ;-(

Hank

Thanks, Tony.... much appreciated. Would you think this is something that
I should do on or off shift? I can't allow *any* disruption to
operations....

Hank

 

[Tomasz Onyszko [MVP]]

Thanks, Tony.... much appreciated. Would you think this is something that I
should do on or off shift? I can't allow *any* disruption to operations....

You can do this on shift becouse this will not affect your existing
environment

 

[Hank Arnold]

We do have two sites defiled: "Default-First-Site" and "Kingston" (the
remote site).

I assume that I also have to change the IP address to a 192.1.100 subnet
address?

Hank

 

[Tomasz Onyszko [MVP]]

We do have two sites defiled: "Default-First-Site" and "Kingston" (the
remote site).

I assume that I also have to change the IP address to a 192.1.100 subnet
address?

OK - now You have to define proper subnets objects which will reflect
subnets used in Your location - for example If 192.1.100 subnet is used
in Kingston location you have to create such subnet in AD and theh
assign it to Kingston site.

 

[Hank Arnold]

I messed up..... I currently have the sites defined and assigned in AD Sites
and Services as:
192.168.1.xxx Default-First-Site
192.168.100.xxx Kingston

Is that what you mean?

 

[Tomasz Onyszko [MVP]]

I messed up..... I currently have the sites defined and assigned in AD Sites
and Services as:
192.168.1.xxx Default-First-Site
192.168.100.xxx Kingston

Is that what you mean?

Yes, If this reflects Your networks in this site this is what you should
have in your AD - now You have to build new DC and put it in the
Kingston site.

 

[Hank Arnold]

Thanks again for the help.... Much appreciated...