Win 2003 network help on remote site

Hello,

We need to connect our new remote office to our existing Windows 2003
active directory network and wondered what the best way to it.

The two offices will be connected through the internet using a VPN. The
head office has 50 users and the remote office has 20 users. What
additional hardware would be required at the new remote office and how
would be best to set it up. Is it as simple as installing another DC in
the remote office. If the VPN were to go down would they still be able
to work and log on etc?

Would it be better to create a child domain, for example:
"remoteoffice.company.local" or just leave it as one domain, for example
"company.local"

The domain controllers are currently configured as:

Schema owner: server1
Domain role owner: server1
PDC role: server2
RID pool manager: server2
Infrastructure owner: server2

Any help gratefully received.

Thank you.

Aaron Humperdoomperdink

Se the remote office as a site in your existing domain.

hth
DDS
"Aaron Humperdoomperdink" <(E-Mail Removed)> wrote in message
news:Xns98C8AB9E9B045blahblahcom@216.168.3.44...
> Hello,
>
> We need to connect our new remote office to our existing Windows 2003
> active directory network and wondered what the best way to it.
>
> The two offices will be connected through the internet using a VPN. The
> head office has 50 users and the remote office has 20 users. What
> additional hardware would be required at the new remote office and how
> would be best to set it up. Is it as simple as installing another DC in
> the remote office. If the VPN were to go down would they still be able
> to work and log on etc?
>
> Would it be better to create a child domain, for example:
> "remoteoffice.company.local" or just leave it as one domain, for example
> "company.local"
>
> The domain controllers are currently configured as:
>
> Schema owner: server1
> Domain role owner: server1
> PDC role: server2
> RID pool manager: server2
> Infrastructure owner: server2
>
> Any help gratefully received.
>
> Thank you.
>
> Aaron Humperdoomperdink

"Danny Sanders" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> Se the remote office as a site in your existing domain.
>
> hth
> DDS
> "Aaron Humperdoomperdink" <(E-Mail Removed)> wrote in message
> news:Xns98C8AB9E9B045blahblahcom@216.168.3.44...
>> Hello,
>>
>> We need to connect our new remote office to our existing Windows 2003
>> active directory network and wondered what the best way to it.
>>
>> The two offices will be connected through the internet using a VPN.
>> The head office has 50 users and the remote office has 20 users.
>> What additional hardware would be required at the new remote office
>> and how would be best to set it up. Is it as simple as installing
>> another DC in the remote office. If the VPN were to go down would
>> they still be able to work and log on etc?
>>
>> Would it be better to create a child domain, for example:
>> "remoteoffice.company.local" or just leave it as one domain, for
>> example "company.local"
>>
>> The domain controllers are currently configured as:
>>
>> Schema owner: server1
>> Domain role owner: server1
>> PDC role: server2
>> RID pool manager: server2
>> Infrastructure owner: server2
>>
>> Any help gratefully received.
>>
>> Thank you.
>>
>> Aaron Humperdoomperdink
>
>
>


Thanks for the reply.

What do you mean site in existing domain?

See:
http://support.microsoft.com/kb/823063/en-us

hth
DDS
"Aaron Humperdoomperdink" <(E-Mail Removed)> wrote in message
news:Xns98C8B244756D9blahblahcom@216.168.3.44...
> "Danny Sanders" <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):
>
>> Se the remote office as a site in your existing domain.
>>
>> hth
>> DDS
>> "Aaron Humperdoomperdink" <(E-Mail Removed)> wrote in message
>> news:Xns98C8AB9E9B045blahblahcom@216.168.3.44...
>>> Hello,
>>>
>>> We need to connect our new remote office to our existing Windows 2003
>>> active directory network and wondered what the best way to it.
>>>
>>> The two offices will be connected through the internet using a VPN.
>>> The head office has 50 users and the remote office has 20 users.
>>> What additional hardware would be required at the new remote office
>>> and how would be best to set it up. Is it as simple as installing
>>> another DC in the remote office. If the VPN were to go down would
>>> they still be able to work and log on etc?
>>>
>>> Would it be better to create a child domain, for example:
>>> "remoteoffice.company.local" or just leave it as one domain, for
>>> example "company.local"
>>>
>>> The domain controllers are currently configured as:
>>>
>>> Schema owner: server1
>>> Domain role owner: server1
>>> PDC role: server2
>>> RID pool manager: server2
>>> Infrastructure owner: server2
>>>
>>> Any help gratefully received.
>>>
>>> Thank you.
>>>
>>> Aaron Humperdoomperdink
>>
>>
>>
>
>
> Thanks for the reply.
>
> What do you mean site in existing domain?
>

"Danny Sanders" <(E-Mail Removed)> wrote in news:ODaYubJRHHA.3444
@TK2MSFTNGP03.phx.gbl:

> See:
> http://support.microsoft.com/kb/823063/en-us
>


Thanks for the info. One more question though.


The remote site would have a copy of the global catalog on the DC but the
FSMO roles would still be at the head office. If the WAN link between the
remote site and head office were to go down for an hour or even a few days
I am guessing the remote site would not function. Would this be correct?
Is there any way to stop the down time if this was to happen?

If the WAN link between the
> remote site and head office were to go down for an hour or even a few days
> I am guessing the remote site would not function. Would this be correct?
> Is there any way to stop the down time if this was to happen?

They would have limited functionality depending on what their local DC
provides. At least provide DHCP, DNS, and access to their files.

The link is going to go down, depend on it. You might consider going with a
company like Sprint for a circuit to the remote office and use the VPN as a
backup.

hth
DDS

"Aaron Humperdoomperdink" <(E-Mail Removed)> wrote in message
news:Xns98CA8BC789E40blahblahcom@216.168.3.44...
> "Danny Sanders" <(E-Mail Removed)> wrote in news:ODaYubJRHHA.3444
> @TK2MSFTNGP03.phx.gbl:
>
>> See:
>> http://support.microsoft.com/kb/823063/en-us
>>
>
>
> Thanks for the info. One more question though.
>
>
> The remote site would have a copy of the global catalog on the DC but the
> FSMO roles would still be at the head office. If the WAN link between the
> remote site and head office were to go down for an hour or even a few days
> I am guessing the remote site would not function. Would this be correct?
> Is there any way to stop the down time if this was to happen?
>