add a DC in a LegSite

Hi,
In the disaster recovery plan we want to create a leg site and put a DC in
it.
Here are some questions on how to achieve this smoothly.
1. Should I create the new site/subnet first and then promote a server in
that subnet/site to DC, or should I promote a server in existing site/subnet
and then move this DC to the new site/subnet?
2. When promoting a server to DC, should the server be a member server
(already joined the domain) or just a workgroup member (no domain
membership)?
3. The DC will be an AD-integrated DNS server. Should I install the DNS
component (but not configured) before promoting or should I install and
configure DNS service after ptomoting to DC?
I wish to find out a best approach.
Thanks in advance!

On Wed, 2 Jun 2010 13:17:28 +1000, "tree leafs"
<> wrote:

>Hi,
>In the disaster recovery plan we want to create a leg site and put a DC in
>it.
>Here are some questions on how to achieve this smoothly.
>1. Should I create the new site/subnet first and then promote a server in
>that subnet/site to DC, or should I promote a server in existing site/subnet
>and then move this DC to the new site/subnet?
>2. When promoting a server to DC, should the server be a member server
>(already joined the domain) or just a workgroup member (no domain
>membership)?
>3. The DC will be an AD-integrated DNS server. Should I install the DNS
>component (but not configured) before promoting or should I install and
>configure DNS service after ptomoting to DC?
>I wish to find out a best approach.
>Thanks in advance!
>

I usually just craete the DC locally, allow it to udpate, etc, on the
local subnet, then right before I ship it, I change the IP ready for
the new location, then create a new Site, Subnet object for the new
subnet, associate it with the Site name, then move the server into
that new site. By the time it gets there and up and running,
replication has taken effect and the server is good to go!

Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

On Wed, 2 Jun 2010 13:17:28 +1000, "tree leafs"
<> wrote:

>Hi,
>In the disaster recovery plan we want to create a leg site and put a DC in
>it.
>Here are some questions on how to achieve this smoothly.
>1. Should I create the new site/subnet first and then promote a server in
>that subnet/site to DC, or should I promote a server in existing site/subnet
>and then move this DC to the new site/subnet?
>2. When promoting a server to DC, should the server be a member server
>(already joined the domain) or just a workgroup member (no domain
>membership)?
>3. The DC will be an AD-integrated DNS server. Should I install the DNS
>component (but not configured) before promoting or should I install and
>configure DNS service after ptomoting to DC?
>I wish to find out a best approach.
>Thanks in advance!
>

Oh, I forgot, one more thing, make sure the the first DNS IP is still
pointing to a DC/DNS in the location you configured it. This way, it
will still be able to fire up, logon, etc, and let replication get
caught up so it is aware of its new site, etc, then change it to point
to itself aftewards.

Ace

Thanks.
you answered my first question. what about my second and third questions?

"Ace Fekay [MVP - Directory Services, MCT]" <>
wrote in message news:...
> On Wed, 2 Jun 2010 13:17:28 +1000, "tree leafs"
> <> wrote:
>
>>Hi,
>>In the disaster recovery plan we want to create a leg site and put a DC in
>>it.
>>Here are some questions on how to achieve this smoothly.
>>1. Should I create the new site/subnet first and then promote a server in
>>that subnet/site to DC, or should I promote a server in existing
>>site/subnet
>>and then move this DC to the new site/subnet?
>>2. When promoting a server to DC, should the server be a member server
>>(already joined the domain) or just a workgroup member (no domain
>>membership)?
>>3. The DC will be an AD-integrated DNS server. Should I install the DNS
>>component (but not configured) before promoting or should I install and
>>configure DNS service after ptomoting to DC?
>>I wish to find out a best approach.
>>Thanks in advance!
>>
>
> Oh, I forgot, one more thing, make sure the the first DNS IP is still
> pointing to a DC/DNS in the location you configured it. This way, it
> will still be able to fire up, logon, etc, and let replication get
> caught up so it is aware of its new site, etc, then change it to point
> to itself aftewards.
>
> Ace

Hello tree,

1. Paul has a good article about lag site: http://www.pbbergs.com/windows/artic...tion_Delay.htm
2. Make it member server first
3. INstall DNS during promotion of the DC

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


> Hi,
> In the disaster recovery plan we want to create a leg site and put a
> DC in
> it.
> Here are some questions on how to achieve this smoothly.
> 1. Should I create the new site/subnet first and then promote a server
> in
> that subnet/site to DC, or should I promote a server in existing
> site/subnet
> and then move this DC to the new site/subnet?
> 2. When promoting a server to DC, should the server be a member server
> (already joined the domain) or just a workgroup member (no domain
> membership)?
> 3. The DC will be an AD-integrated DNS server. Should I install the
> DNS
> component (but not configured) before promoting or should I install
> and
> configure DNS service after ptomoting to DC?
> I wish to find out a best approach.
> Thanks in advance

I apologize for not addressing the other two questions. Meinolf
responded for you.

In addition, for #2, you can join it first, as Meinolf said. Or what I
usually do is simply directly promoted it to a DC alleviating the
extra step of joining it to the domain first as a member server, but
it won't really make a difference.

For #3, I usually install DNS as part of the promotion process, which
is the easiest, as Meinolf mentioned. But you can also install it
before or afterwards. It doesn't really matter. If you install it
before or afterwards, one piece of advise is to NOT create any zones
on it. If your current zones are AD integrated, they will
*automatically* replicate and show up. If you try and create the zones
manually prior to allowing replication to occur, then you will
introduce a duplicate zone issue in the AD database.

Ace

On Wed, 2 Jun 2010 17:35:12 +1000, "tree leafs"
<> wrote:

>Thanks.
>you answered my first question. what about my second and third questions?
>
>"Ace Fekay [MVP - Directory Services, MCT]" <>
>wrote in message news:...
>> On Wed, 2 Jun 2010 13:17:28 +1000, "tree leafs"
>> <> wrote:
>>
>>>Hi,
>>>In the disaster recovery plan we want to create a leg site and put a DC in
>>>it.
>>>Here are some questions on how to achieve this smoothly.
>>>1. Should I create the new site/subnet first and then promote a server in
>>>that subnet/site to DC, or should I promote a server in existing
>>>site/subnet
>>>and then move this DC to the new site/subnet?
>>>2. When promoting a server to DC, should the server be a member server
>>>(already joined the domain) or just a workgroup member (no domain
>>>membership)?
>>>3. The DC will be an AD-integrated DNS server. Should I install the DNS
>>>component (but not configured) before promoting or should I install and
>>>configure DNS service after ptomoting to DC?
>>>I wish to find out a best approach.
>>>Thanks in advance!
>>>
>>
>> Oh, I forgot, one more thing, make sure the the first DNS IP is still
>> pointing to a DC/DNS in the location you configured it. This way, it
>> will still be able to fire up, logon, etc, and let replication get
>> caught up so it is aware of its new site, etc, then change it to point
>> to itself aftewards.
>>
>> Ace
>