RE: 2003 Server multi sites

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

anonymous_at_discussions.microsoft.com
Date: 07/31/04


Date: Sat, 31 Jul 2004 08:52:35 -0700

Thank you for replie but half of machines will still be
98 so local cache credentilas will not work
>-----Original Message-----
>If each site has less than 1k users and are connected
via a T1 I don't think you even need to have local DCs.
Clients at the remote offices will still be able to log
on and access resources if the network is available
because of cached credentials. If your network is full
fledged T1s then there shouldn't be any network outages
long enough to run into the problem of cached credentials
expiring.
>
>What I would look at is the network load on the T1s, the
estimated logon traffic generated by 1k users and compare
that to the estimated replication traffic generated by
AD. Often times in a fairly large AD environment you will
find that the authentication traffic of 1k users will be
smaller than the replication traffic of AD. If your T1
connections can support the authentication traffic of 1k
users then I wouldn't bother putting a local DC at those
locations. Just make sure you size your main office DCs
to support the load of the remote offices.
>
>Phil
>
>"webby" wrote:
>
>> I've got 8 sites and I'm putting 2 DC's on the 3 large
>> sites and 1 DC on each of the others. If you set them
up
>> as seperate sites with separate subnets within the
domain
>> it should dramatically reduce access time to
resources,
>> as AD should look on the local subnet first, it also
>> helps users locate resources.
>>
>> DNS is a must, and WINS is advisable as this will also
>> reduce browser traffic
>>
>> Looks like your on the right track
>>
>> >-----Original Message-----
>> >I have 2 DC's at a Main site
>> >10 Remote sites that all require dmain logon access
if
>> >the connectivity to the main site is down. Therefore,
I
>> >need to make servers DC's for each site.
>> >
>> >Each site has about 1,000 objects per location
>> >The sites are well connected sites all ATM T1 back to
>> the
>> >main site.
>> >
>> >
>> >Question #1:
>> >Do I need to make AD Sites or can they all be part of
>> the
>> >default first site?
>> >
>> >Question#2:
>> >In order to keep brwsing traffic back I am making
them
>> >WINS and DNS servers as well so that the requests to
the
>> >main site are minimal. I am making them WINS
replication
>> >partners and DNS servers as well. Should I do this?
>> >
>> >Anyone have more feedback on this?
>> >THANK YOU
>> >
>> >.
>> >
>>
>.
>



Relevant Pages

  • Re: Nesting domain groups under local groups
    ... access the other domain's file sharing resources, ... across the network with other users in this application. ... laptop/computer, using cached credentials, you can then connect to resources ... If the user disconnects ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Nesting domain groups under local groups
    ... it is tricky - the application checks the custom group membership, ... checking via various network communication methods. ... to access the other domain's file sharing resources, ... laptop/computer, using cached credentials, you can then connect to ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Nesting domain groups under local groups
    ... I didn't think to use remote credentials. ... components across the network. ... access the other domain's file sharing resources, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: cached login credentials
    ... , it takes longer to investigate an attack and clean up after it than it does simply to nuke-and-pave, flatten-and-rebuild, whatever. ... then over time through precision monitoring of network ... Anything that does an interactive logon will store cached credentials, ... > domain admin account credentials), is a credential cached anywhere for> the ...
    (microsoft.public.windowsxp.security_admin)
  • Re: cached login credentials
    ... administrator accounts is a good mitigation. ... then over time through precision monitoring of network ... you have a way to limit exposure to this sort of expanded attack originating ... Anything that does an interactive logon will store cached credentials, ...
    (microsoft.public.windowsxp.security_admin)