There are a lot of docs on creating sites. You don't have to have another
site but it is beneficial if you have a slow link connection to control
replication on a schedule and have users authenticate to the local domain
controller. Note that you want that domain controller physical secured to
some degree as it will contain critical domain information. You can prestage
the new domain controller including using the dcpromo /adv option to install
it from media however I am unsure of the tactic of having two domain
controllers not being able to replicate for a couple of weeks. My guess is
that it would work but barely, but for sure any Group Policy changes would
not propagate and the Event logs would be full of errors. There could be
complications with the new dc not being able to contact the other fsmo
roleholders, particularly the Rid Master though if you do not need to add
any users or groups at that site after the install it may be OK. Of course
it would need to point to itself as it's primary preferred dns server. You
could install the server as a regular server and create local user accounts
on it and other servers that need to offer shares until the link is ready.
Then you could use dcpromo /adv to install the domain controller and let it
replicate changes over the link. Be sure to make the new domain controller a
global catalog server. I would definitely post in an active_directory
newsgroup about having two domain controllers not being able to replicate
for two weeks for more advice on that tactic, maybe from someone who has
actually done such. The links below may help. --- Steve
http://www.microsoft.com/technet/pro...1/adogd06.mspx
http://www.petri.co.il/install_dc_fr...erver_2003.htm
"Joe R." <(E-Mail Removed)> wrote in message
news:1B4C0DFC-08B3-445F-9B1D-(E-Mail Removed)...
>I have a client that has a windows 2003 domain setup in a single location.
> However, they are growing and are putting a new office in IL. So, they
> will
> have two locations. The new office in IL will not have an IT person on
> staff
> so they want to have a single location to handle most of the
> administration.
> They want that location to be their current office in WI. I believe the
> solution for this would be to configure a new server and make it part of
> the
> domain as an AD server. However, I would need to create a second site and
> have it put in that site. Is there a document that talks about creating
> sites and configuring this?
> To complicate things a bit, they are going to be connected via frame
> relay.
> However, the frame relay will not be installed for about 1 month.
> However,
> the office opens up in 2 weeks and they want to have the server installed
> when the office opens. Can I setup the new server at the main office in
> WI,
> put it in it's own site, allow it to replicate, and then move it to IL,
> change the IP address and allow the users to begin logging in? I realize
> that no replication will take place during this time. However, when the
> frame relay comes on-line, will it then automatically begin replicating
> with
> the server in WI?
> Any help and suggestions you can give me on this would be greatly
> appreciated! Thank you in advance.
Similar Threads
Linear Mode
