RE: Cached mode over WAN - how many users and what type of connection?
- From: "Evan Mann" <emann@xxxxxxxxxxxxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 11:52:53 -0500
I probably have 500 or more users actively connected in cached mode
using Exchange over HTTP at any given time, if not more.
I have 10mbits of outbound bandwidth, but I've not done any reporting to
find out how much Exchange actually uses for OWA/Exchange over RPC.
Based on total traffic, I'd say I'm using a peak of around 1.0mbps for
the Exchange connections. On a consistant basis, I think I'm under
1.0meg outbound for Exchange connections only.
Factors effecting that are number of users active, number of e-mails,
size of e-mails, if outlook is left open all the time (small bits of
bandwidth used to update cache) or only opened every X hours (large
chunks of bandwidth used to update cache).
-----Original Message-----
From: Danny [mailto:nocmonkey@xxxxxxxxx]
Sent: Thursday, January 26, 2006 11:27 AM
To: [ExchangeList]
Subject: [exchangelist] Cached mode over WAN - how many users and what
type of connection?
http://www.MSExchange.org/
Exchange 2003...sizing remote users via WAN connection.
What is the most amount of simultaneously connected Outlook 2003 (Cached
Mode) users you have over a WAN connection? And what type connection is
it?
Thanks,
...D
--
CPDE - Certified Petroleum Distribution Engineer CCBC - Certified
Canadian Beer Consumer
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
emann@xxxxxxxxxxxxxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx
Other related posts:
