| Author |
Message |
IceBlue
Guest
|
Posted:
Wed Aug 03, 2005 8:59 am Post subject:
RPC-over-HTTP bandwidth requirement |
|
|
Hi,
Does anyone know the minimum requirement of bandwidth for running an outlook
2003 client (using rpc-over-http feature)? How many users can a 128Kbps or
64Kbps link accomodate?
Thanks,
|
|
| Back to top |
|
 |
Rui J.M. Silva [MVP]
Guest
|
Posted:
Thu Aug 04, 2005 4:59 pm Post subject:
Re: RPC-over-HTTP bandwidth requirement |
|
|
It depends.
Will the users use the link all at the same time?
What is your users' profile in terms of message size, number of messages,
....
I'd say that if you use offline mode and have rational limits, you'll
probably manage to accomodate around 10 users.
--
Rui JM Silva
MVP Windows Server System - Exchange Server
Blog "subject: exchange", http://msmvps.com/ehlo
"IceBlue" <IceBlue@discussions.microsoft.com> wrote in message
news:1C089F51-866C-406C-BAAD-5FB06E77D5E3@microsoft.com...
| Quote: | Hi,
Does anyone know the minimum requirement of bandwidth for running an
outlook
2003 client (using rpc-over-http feature)? How many users can a 128Kbps or
64Kbps link accomodate?
Thanks,
|
|
|
| Back to top |
|
 |
IceBlue
Guest
|
Posted:
Fri Aug 05, 2005 8:59 am Post subject:
Re: RPC-over-HTTP bandwidth requirement |
|
|
Yes, they will be using the link all at the same time.
Let's say we are replacing an exchange server (serving a number of users at
a remote site) with outlook/RPC over HTTP. The link, number of users, number
of messages and size of messages are all the same, how much additional
bandwidth do we need to add for the RPC-over-HTTP to work?
The links where the exch. server will be removed are all low bandwidth
(32Kbps to 128Kbps)
"Rui J.M. Silva [MVP]" wrote:
| Quote: | It depends.
Will the users use the link all at the same time?
What is your users' profile in terms of message size, number of messages,
....
I'd say that if you use offline mode and have rational limits, you'll
probably manage to accomodate around 10 users.
--
Rui JM Silva
MVP Windows Server System - Exchange Server
Blog "subject: exchange", http://msmvps.com/ehlo
"IceBlue" <IceBlue@discussions.microsoft.com> wrote in message
news:1C089F51-866C-406C-BAAD-5FB06E77D5E3@microsoft.com...
Hi,
Does anyone know the minimum requirement of bandwidth for running an
outlook
2003 client (using rpc-over-http feature)? How many users can a 128Kbps or
64Kbps link accomodate?
Thanks,
|
|
|
| Back to top |
|
 |
Mark Arnold [MVP]
Guest
|
Posted:
Fri Aug 05, 2005 4:59 pm Post subject:
Re: RPC-over-HTTP bandwidth requirement |
|
|
On Thu, 4 Aug 2005 23:35:36 -0700, "IceBlue"
<IceBlue@discussions.microsoft.com> wrote:
| Quote: | Yes, they will be using the link all at the same time.
Let's say we are replacing an exchange server (serving a number of users at
a remote site) with outlook/RPC over HTTP. The link, number of users, number
of messages and size of messages are all the same, how much additional
bandwidth do we need to add for the RPC-over-HTTP to work?
The links where the exch. server will be removed are all low bandwidth
(32Kbps to 128Kbps)
|
I wouldn't do anything about the banmdwidth. Because the users will be
using cached mode they won't know if there's a bit of a squeeze on the
bandwidth because they're operating against the local store.
They'll notice if a mail between two folks in the same location takes
an age to get there but that's unlikely unless it's a large attachment
and then the users should be slapped for not using shortcuts etc.
The removal of an Exchange server obviously reduces the server to
server bandwidth which is replaced by the client to remote server
traffic. It's not an apples for apples trade off.
Start with the same link and monitor it for a while. If you do need to
increase a link then you can do that but it's not worth second
guessing such a small link at this time. |
|
| Back to top |
|
 |
Rui J.M. Silva [MVP]
Guest
|
Posted:
Fri Aug 05, 2005 4:59 pm Post subject:
Re: RPC-over-HTTP bandwidth requirement |
|
|
There's a *GREAT* document about traffic analysis:
"Client Network Traffic with Exchange Server 2003"
http://www.microsoft.com/technet/prodtechnol/exchange/2003/clinettraf.mspx
There you can read (Conclusion, pag.332:
"
If you deploy Outlook 2003 for your roaming users, using RPC/HTTP will only
add a very small amount of traffic (compared to classic RPC access), so you
can use this feature confidently. Cache with Outlook 2003 adds more traffic
when you send messages because you also synchronize the "sent items folder,"
but, because some actions are made locally (such as read old messages and
change view), the total traffic generated with Outlook 2003 with cache mode
is generally better than Outlook 2003 without cache mode.
"
--
Rui JM Silva
MVP Windows Server System - Exchange Server
Blog "subject: exchange", http://msmvps.com/ehlo
"IceBlue" <IceBlue@discussions.microsoft.com> wrote in message
news:85BEE2B0-1352-45CC-A174-4789716DB115@microsoft.com...
| Quote: | Yes, they will be using the link all at the same time.
Let's say we are replacing an exchange server (serving a number of users
at
a remote site) with outlook/RPC over HTTP. The link, number of users,
number
of messages and size of messages are all the same, how much additional
bandwidth do we need to add for the RPC-over-HTTP to work?
The links where the exch. server will be removed are all low bandwidth
(32Kbps to 128Kbps)
"Rui J.M. Silva [MVP]" wrote:
It depends.
Will the users use the link all at the same time?
What is your users' profile in terms of message size, number of messages,
....
I'd say that if you use offline mode and have rational limits, you'll
probably manage to accomodate around 10 users.
--
Rui JM Silva
MVP Windows Server System - Exchange Server
Blog "subject: exchange", http://msmvps.com/ehlo
"IceBlue" <IceBlue@discussions.microsoft.com> wrote in message
news:1C089F51-866C-406C-BAAD-5FB06E77D5E3@microsoft.com...
Hi,
Does anyone know the minimum requirement of bandwidth for running an
outlook
2003 client (using rpc-over-http feature)? How many users can a 128Kbps
or
64Kbps link accomodate?
Thanks,
|
|
|
| Back to top |
|
 |
|
|
|
|