It doesn't sound like you would need a DC there. If the link goes down and
they can't authenticate to the central DC, they will be able to log in with
cached credentials anyway, just like a laptop. You would consider a DC if
they had a file server on site, for example, and if the disruption of not
being able to connect to it when the link goes down was too great. As it is,
they are more like 8 separate remote users connecting over VPN.
Anthony
www.airdesk.co.uk
"Rich" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Thanks for your reply
>
> The users over there a simply using TS to run most applications so if
> the link goes down they wouldn't be able to work anyway.
>
> On 19 Feb, 16:08, "Anthony" <anthony.s...@spammedout.com> wrote:
>> It will cause very little traffic. The main consideration in a case like
>> this is: what happens if the link goes down, and can I afford another DC?
>> Anthonywww.airdesk.co.uk
>>
>> "Rich" <barnett.rich...@gmail.com> wrote in message
>>
>> news:(E-Mail Removed) oups.com...
>>
>>
>>
>> > Sorry I forgot to say that both sites are conected via routers so are
>> > on different Subnets.
>>
>> > On 19 Feb, 09:51, "Rich" <barnett.rich...@gmail.com> wrote:
>> >> Hi
>>
>> >> We currently have two sites:
>>
>> >> One site which is the main site is AD 2003 and has about 45 machines
>> >> connected to it.
>> >> The other site has 8 machines which are part of a workgroup and
>> >> connect to services on the main site using Terminal Services.
>> >> I would like to connect the machines on the remote site to Active
>> >> Directory but am unsure how much traffic this will cause across the
>> >> link.
>>
>> >> At present the sites are connected via Gshdsl EPS9 link running at 2
>> >> meg
>>
>> >> Thanks- Hide quoted text -
>>
>> - Show quoted text -
>
>