Active Directory trafic over WAN

Looking into finding guide lines for Network traffic generation for AD logon
and Exchange Mailbox access. ( both across a wan ).

Is there a document from MS that gives a ball park idea of how much network
traffic is generated by each user logon and mailbox access..

Looking into designing a Network WAN infrastructure for a client with 2
corporate head-quarters located in the same state and 40 retail location
across the state. The retail locations will have 10 to 15 computers, but no
servers on site, all AD authentication ( XP Client, Win2K3 servers ) and
Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox access
will be over the WAN.

Thanks !!!

I don't think you will be satisfied with the performance. I can't point you
to a doc but from experience, we have 50+ offices all over the world. Each
connected by a T1 to corporate and there is a definite benefit to having a
DC in each office. Especially if you set up sites for each office.

Set up a test with a couple of offices, one with a DC and sites setup and
one without a DC. For this purpose the test DC could just be a "box" cobbled
together just for this test.

hth
DDS

"Thinkpad21" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Looking into finding guide lines for Network traffic generation for AD
> logon and Exchange Mailbox access. ( both across a wan ).
>
> Is there a document from MS that gives a ball park idea of how much
> network traffic is generated by each user logon and mailbox access..
>
> Looking into designing a Network WAN infrastructure for a client with 2
> corporate head-quarters located in the same state and 40 retail location
> across the state. The retail locations will have 10 to 15 computers, but
> no servers on site, all AD authentication ( XP Client, Win2K3 servers )
> and Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox
> access will be over the WAN.
>
> Thanks !!!
>
>

The general guideline is that a link should be scaled so that when you add
up all the users there's enough bandwidth at a minimum, using the guideline
that heavy Outlook users consume 10Kbps, moderate 7Kbps, and light 5Kbps of
bandwidth. This is only a rough guideline. If your users are using cached
mode, you can probably get by with less because although the network use
isn't much different, the user experience is much better.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Thinkpad21" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Looking into finding guide lines for Network traffic generation for AD
> logon and Exchange Mailbox access. ( both across a wan ).
>
> Is there a document from MS that gives a ball park idea of how much
> network traffic is generated by each user logon and mailbox access..
>
> Looking into designing a Network WAN infrastructure for a client with 2
> corporate head-quarters located in the same state and 40 retail location
> across the state. The retail locations will have 10 to 15 computers, but
> no servers on site, all AD authentication ( XP Client, Win2K3 servers )
> and Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox
> access will be over the WAN.
>
> Thanks !!!
>
>

"Thinkpad21" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Looking into finding guide lines for Network traffic generation for AD
> logon and Exchange Mailbox access. ( both across a wan ).
>
> Is there a document from MS that gives a ball park idea of how much
> network traffic is generated by each user logon and mailbox access..
>
> Looking into designing a Network WAN infrastructure for a client with 2
> corporate head-quarters located in the same state and 40 retail location
> across the state. The retail locations will have 10 to 15 computers, but
> no servers on site, all AD authentication ( XP Client, Win2K3 servers )
> and Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox
> access will be over the WAN.
>
> Thanks !!!
>
>

I would look into the use of a Thin Client set-up, either Terminal Server
within Windows or building on that with Citrix. That way there is only the
neccesary traffic required for screen updates and thats pretty much it. No
real data is transferred so the overhead on bandwidth is kept to a minimum.
It just means investing slightly more in the servers at the head office
location(s).

Ewwwww....
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Danny Cooke" <(E-Mail Removed)> wrote in message
news:iSrlj.2579$(E-Mail Removed)...
>
> "Thinkpad21" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Looking into finding guide lines for Network traffic generation for AD
>> logon and Exchange Mailbox access. ( both across a wan ).
>>
>> Is there a document from MS that gives a ball park idea of how much
>> network traffic is generated by each user logon and mailbox access..
>>
>> Looking into designing a Network WAN infrastructure for a client with 2
>> corporate head-quarters located in the same state and 40 retail location
>> across the state. The retail locations will have 10 to 15 computers, but
>> no servers on site, all AD authentication ( XP Client, Win2K3 servers )
>> and Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox
>> access will be over the WAN.
>>
>> Thanks !!!
>>
>>
>
> I would look into the use of a Thin Client set-up, either Terminal Server
> within Windows or building on that with Citrix. That way there is only the
> neccesary traffic required for screen updates and thats pretty much it. No
> real data is transferred so the overhead on bandwidth is kept to a
> minimum. It just means investing slightly more in the servers at the head
> office location(s).
>

"Ed Crowley [MVP]" <(E-Mail Removed)> wrote:

>Ewwwww....

Not necessarily. Concurrent licensing can save a bundle of money using
Citrix and MS Office. It also means that you don't need a VPN to get
to all the data on your network if you work outside the LAN.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address private.php?do=newpm&u=
Or to these, either: private.php?do=newpm&u= private.php?do=newpm&u= private.php?do=newpm&u=

lmao Ed, how nice and constructive ;-p


"Ed Crowley [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Ewwwww....
> --
> Ed Crowley
> MVP - Exchange
> "Protecting the world from PSTs and brick backups!"
>
> "Danny Cooke" <(E-Mail Removed)> wrote in message
> news:iSrlj.2579$(E-Mail Removed)...
>>
>> "Thinkpad21" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Looking into finding guide lines for Network traffic generation for AD
>>> logon and Exchange Mailbox access. ( both across a wan ).
>>>
>>> Is there a document from MS that gives a ball park idea of how much
>>> network traffic is generated by each user logon and mailbox access..
>>>
>>> Looking into designing a Network WAN infrastructure for a client with 2
>>> corporate head-quarters located in the same state and 40 retail location
>>> across the state. The retail locations will have 10 to 15 computers, but
>>> no servers on site, all AD authentication ( XP Client, Win2K3 servers )
>>> and Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox
>>> access will be over the WAN.
>>>
>>> Thanks !!!
>>>
>>>
>>
>> I would look into the use of a Thin Client set-up, either Terminal Server
>> within Windows or building on that with Citrix. That way there is only
>> the neccesary traffic required for screen updates and thats pretty much
>> it. No real data is transferred so the overhead on bandwidth is kept to a
>> minimum. It just means investing slightly more in the servers at the head
>> office location(s).
>>
>
>

Lot's of opinions, but I didn't see where anyone gave you an actual
reference documents. Here:

http://www.microsoft.com/technet/pro...linettraf.mspx

http://www.microsoft.com/technet/pro....mspx?mfr=true




"Thinkpad21" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Looking into finding guide lines for Network traffic generation for AD
> logon and Exchange Mailbox access. ( both across a wan ).
>
> Is there a document from MS that gives a ball park idea of how much
> network traffic is generated by each user logon and mailbox access..
>
> Looking into designing a Network WAN infrastructure for a client with 2
> corporate head-quarters located in the same state and 40 retail location
> across the state. The retail locations will have 10 to 15 computers, but
> no servers on site, all AD authentication ( XP Client, Win2K3 servers )
> and Exchange ( Exch2007, Outlook 2K3 or 2K7 with cache mode ) mailbox
> access will be over the WAN.
>
> Thanks !!!
>
>