ASP and Exchange 2003

[jvande]

We are looking to host a customer with approxiametely 55 mailboxes on exchange using outlook 2003 as the client. We plan on having them access the exchange server which resides on a T1 through their company DSL Internet line. There will be no dedicated connection to our exchange server to their outlook clients just the DSL internet line. Will this be a problem?

 

[gmcdonnell]

Outlook 2003 / Exchange 2003 is better than earlier versions in that the combination uses less bandwidth than earlier versions, but 55 users will very likely overload the T-1 and will certainly overload the DSL connection unless the mailbox useage is very light.

Also, you'll probably need a router based VPN between the two sites. Outlook 2003 can talk to Exchange 2003 via HTTP or HTTPS but the Exchange server still needs to be a part of their Active Directory domain, which necessitates that several other ports be open. And to put the Exchange server out on the Internet without a firewall is inviting disaster from a security standpoint.

/gary

 

[MidwestAdmin]

Have you looked at providing just the new OWA web interface? Looks just like Outlook 2k3. It may not meet every criteria but is better on banwidth than the full Outlook client.

 

[jvande]

What about a point to point T1 from us to our client. Is that workable?

 

[Evilbart]

if you will be using outlook 2003 (even over wan) network traffic will decrease.
I have performed tests with this and ol2003 clients consume less bandwith (local store in ol2003 feature)

i ran across white papers with exact figures, but as always i can't dig 'em up when i need them.

// Bart