Re: setup a dc in a remote site

Hi, you situation is different from mine in that our new server has alrady
been shipped to the new site.
However, looking at your plan - after the new DC has been reset its IP
address and shipped to the new site how can you guarantee the replication
between the two sites to occur? Does it happen automatically or you have to
configure the AD site and services to manually create the connections?
Intereted to know if you have done it.
Thanks,

"Hank Arnold" <rasilon@xxxxxxx> wrote in message
news:OEtProrkGHA.1936@xxxxxxxxxxxxxxxxxxxxxxx
I'm thinking of doing something similar. The remote subnet already exists.
My ideas of the process was:

1) Set up an additional/3rd DC (with DNS) in the main subgroup
(102.168.1.xxx). Let it replicate. Make it a GC. the other FSMOs will stay
on the main DC

2) Take it off line and change the IP address to the remote subnet
(192.168.100.xxx)

3) Move it to the remote site and power on.

4) Let it replicate overnight

5) Test in the AM.

Probably do steps 2 - 5 on a Saturday (off shift).

Any concerns about doing it this way?


Regards,
Hank Arnold

second dc wrote:
Hi There,
is there a step-by-step guide for setting up a dc in a remote site?
WAN connection is in place.

This is my plan:
1. on the DC in site 1 (home site), create a new subnet and a new site.
2. in site 2 ( remote site) install the base OS (win2k3 server) on the
new dc-to-be in the new subnet
3. join the new server to the domain
4. promote the new server to DC
5. add the dns role to the new dc - is it atomatically becoming
ad-intgrated DNS?
Is it ok and how to make sure each step is successful?
thanks in advance.


.

Relevant Pages

  • Re: New Remote Office
    ... Say you have two AD sites called site1 and site2, where site1 represents a central site with multiple subnets and site2 represesnts a remote office with a single subnet. ... -Sites constrain replication between DCs and prevent replication traffic from hogging bandwidth. ... taking the server to the remote site to perform DC promo there. ... Are there likely to be any DNS issues with the new remote server connecting ...
    (microsoft.public.windows.server.general)
  • Re: sites and services
    ... What could be smarter than using the DC in the same IP subnet? ... >> controller with AD and is a GC server, at a remote site, and you ... >> create a new site in sites and services and add that server to it, ... >> domain controller they hit. ...
    (microsoft.public.windows.server.networking)
  • Re: New Remote Office
    ... You have a new site and you have a subnet established there with a VPN linking the two sites. ... Build the new server and join it to the domain as a member server ... When it has ensure that the clients at this new site are pointing to the new DC as the primary DNS server. ... therefore having a DC at the remote site. ...
    (microsoft.public.windows.server.general)
  • Re: Adding a DC/GC on a different subnet
    ... I have two GCs and DCs on network 10.100.100.0. ... > a server at the remote site to a DC and a GC but the clients still cannot ... If I demote the DC/GC at the remote site clients are ... Do you have a subnet defined in AD Sites and Services for the 102 ...
    (microsoft.public.win2000.active_directory)
  • Re: Remote DC with MS-SBS 2003 Premium
    ... which would make it simply a member server in the home office. ... the new 192.168.1.* subnet. ... My SBS 2003 server is running ISA2004 and I have 2 NICs. ... and the remote site uses 192.168.1.* for internal addressing. ...
    (microsoft.public.windows.server.active_directory)
Loading