C
Chewy509
Hi Everyone,
I've been given the task to join one of our other offices into our
domain. After reading the Deployment Guide for AD in Branch Offices,
(which is a great reference), sorta leaves me wondering a few
questions.
Site A which is the Main Office (approx 40 users), hosts all the
current DC's, and Site B (which I'm planning to have its own DC) only
has about 6 users, which will be connected via 56K dial-up. After
reading through the above mentioned guide, I would prefer to have a DC
at Site B simply due to the link between the 2 sites is only 56K, and
would like it for network stability. Site B, is already setup on a
Domain, and existing hardware will be used.
So in the above situation, is it possible to connect the 2 sites using
RRAS, and have AD replication perform successfully, when it's the DC
that is hosting the link (via RRAS).
Also, the guide runs through using a staging area to build the branch
office DC, and then shipping the DC to the branch office. However in
my situation that's not really an option due to time frame (should be
done over 1 weekend), and since the company would like an engineer on
site at the Branch Office, it was suggested that all the work should
be done at Site B. So what I was thinking was, is to do the following:
1. Set up RRAS at Site A (to allow dial-in with callback).
2. Backup the current server at Site B, and clean install Win2K w/SP4.
3. Placing the server on Site B onto a different subnet (to Site A),
setup the link between Site A and Site B. All Site B TCP/IP traffic
gets routed to Site A as applicable, and vice versa. (I shouldn't need
RRAS for this?)
4. Once the link is established, and routing is occuring fine (I can
ping, and perform nslookup of site A as well as the Internet), join
the Server at Site B to the Domain at Site A, and then install DNS
services on the server at Site B.
5. Promote the Site B server to a DC of the Site A Domain.(I would
expect this to take about 1-2 hours over the 56K link, as AD shouldn't
be that big with only 40 users/44 computers in it). PLEASE CORRECT ME
IF I AM WRONG HERE.
6. Move the Site B DC (in AD) to a different site, and set the
replication cost appropriately, and set only to replicate every 8 hrs
(due to bandwidth limitations). Test replication once this has been
done.
7. Join the other 6 workstations at Site B, to the domain (with the
Site B server as the local DC for the domain).
So will this work, and what problems do I face? (It looks simple
above, but I know things will go wrong).
Chewy509...
I've been given the task to join one of our other offices into our
domain. After reading the Deployment Guide for AD in Branch Offices,
(which is a great reference), sorta leaves me wondering a few
questions.
Site A which is the Main Office (approx 40 users), hosts all the
current DC's, and Site B (which I'm planning to have its own DC) only
has about 6 users, which will be connected via 56K dial-up. After
reading through the above mentioned guide, I would prefer to have a DC
at Site B simply due to the link between the 2 sites is only 56K, and
would like it for network stability. Site B, is already setup on a
Domain, and existing hardware will be used.
So in the above situation, is it possible to connect the 2 sites using
RRAS, and have AD replication perform successfully, when it's the DC
that is hosting the link (via RRAS).
Also, the guide runs through using a staging area to build the branch
office DC, and then shipping the DC to the branch office. However in
my situation that's not really an option due to time frame (should be
done over 1 weekend), and since the company would like an engineer on
site at the Branch Office, it was suggested that all the work should
be done at Site B. So what I was thinking was, is to do the following:
1. Set up RRAS at Site A (to allow dial-in with callback).
2. Backup the current server at Site B, and clean install Win2K w/SP4.
3. Placing the server on Site B onto a different subnet (to Site A),
setup the link between Site A and Site B. All Site B TCP/IP traffic
gets routed to Site A as applicable, and vice versa. (I shouldn't need
RRAS for this?)
4. Once the link is established, and routing is occuring fine (I can
ping, and perform nslookup of site A as well as the Internet), join
the Server at Site B to the Domain at Site A, and then install DNS
services on the server at Site B.
5. Promote the Site B server to a DC of the Site A Domain.(I would
expect this to take about 1-2 hours over the 56K link, as AD shouldn't
be that big with only 40 users/44 computers in it). PLEASE CORRECT ME
IF I AM WRONG HERE.
6. Move the Site B DC (in AD) to a different site, and set the
replication cost appropriately, and set only to replicate every 8 hrs
(due to bandwidth limitations). Test replication once this has been
done.
7. Join the other 6 workstations at Site B, to the domain (with the
Site B server as the local DC for the domain).
So will this work, and what problems do I face? (It looks simple
above, but I know things will go wrong).
Chewy509...