twinstead
asked on
performance question: OWA VS Outlook/RPC over HTTP VS Standard outlook
Gentlemen:
I have a network in Mexico that is on the other end of a sonicwall VPN. Since a T1 was going to be prohibitively expensive, we have a dedicated 4mb DSL connection that holds the VPN. Performance is OK, but there is a certain amount of fluctuation over the course of the day, from acceptable to fairly slow.
We have an exchange 2007 server on this end. Right now, because of the relatively slow bandwidth, all of the users use OWA to connect from the Mexico plant to the exchange server here. They all have outlook 2003, but it isn't used. I'd like many of them to be able to use Outlook.
My question is what would be the best performance option in that situation? Should I just keep them on OWA, configure outlook to connect to the exchange server up here using RPC over HTTP, or use the regular mapi connection of outlook 2003 in cache mode?
I have a network in Mexico that is on the other end of a sonicwall VPN. Since a T1 was going to be prohibitively expensive, we have a dedicated 4mb DSL connection that holds the VPN. Performance is OK, but there is a certain amount of fluctuation over the course of the day, from acceptable to fairly slow.
We have an exchange 2007 server on this end. Right now, because of the relatively slow bandwidth, all of the users use OWA to connect from the Mexico plant to the exchange server here. They all have outlook 2003, but it isn't used. I'd like many of them to be able to use Outlook.
My question is what would be the best performance option in that situation? Should I just keep them on OWA, configure outlook to connect to the exchange server up here using RPC over HTTP, or use the regular mapi connection of outlook 2003 in cache mode?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No Problem. FYI, one thing I discovered with RPC over HTTP (Outlook Anywhere) for Exchange 2007 was the authentication method. Previously, we utilized Exchange 2003 and NTLM. When we switched to Exchange 2007, NTLM would not connect. I contacted Microsoft and discovered that the ability to utilize NTLM in Exchange 2003 was a bug and they fixed that in 2007. So, Basic is required and when Outlook comes up and tries to connect via Outlook Anywhere, the user is prompted for their domain username and password. This shouldn't be a problem with your users as they are already required to do that with OWA, but it is a configuration head's up.
Glad I could help and thanks for the points!
Glad I could help and thanks for the points!
ASKER
As far as the network goes, from what I can tell the entire industrial plant slows down during the afternoon. It appears the Mexcian telecommunications infrastructure can have some issues.
Thanks for your advice!