Exchange Server - OWA 2003 vs Outlook 2003/Outlook 2003 RPC/HTTP

Hi all,

I would like to get your feedback regarding a customer scenario. Customer
has 2 sites, 1 with 1000 users and 1 with 500, Sites are connected thru 4x2
Mbps lines

They want to deploy an Exchange 2003 cluster in the biggest site and they
would like to avoid the need of deploying aditional mailbox servers in the
second site and the question is what the recommended client in this scenario
is.

They want to deploy a FE/BE topology with a FE in the second site. they have
DCs and GCs in the second site, and they are asking what client will provide
the end users the best performance.

I have been reading many documents and seems Outlook 2003 with Cache mode is
the best option (here they would not install the FE), then Outlook 2003
RPC/HTTP as the second one and finally OWA

From your experiences what is the best client we can deploy in this
centralised topology, giving the end users the best performance?

Cheers

  Jac replied...

Hi
Outlook with RPC in cache mode is by far the option with the least bandwith
consumption.
all other options consume between 30% and 300% more.
(worst case is owa without compression)

HS

problem with OWA redirection Exch 2k7 Exchange Server I have a single exchange server with all components loaded server and I allow SSL (443) through the firewall to this exchange 2007 server for OWA, autodiscover, etc. I purchased a SAN cert from entrust and it is loaded and functioning believe). I am trying to follow the steps in this article: How to Simplify the Outlook Web Access URL http: / / technet.microsoft.com / en-us / library / aa998359.aspx The problem is the home directory tab and change to "A redirection to a URL" and then put " / owa" in the box - it does not work. I cannot get to the owa site at all - through the default site or with the explicit path defined. I do remove the redirect on the default site I can get to https: / / webmail.mydomain.com / owa just fine. I do not have any content loaded for the default site but I well. My goal is to redirect https: / / webmail.mydomain.com to https: / / webmail.mydomain.com / owa. I do not want all of the other sites such as https: / / webmail.mydomain.com guess I would not care if they all were redirected as long as activesync and outlook anywhere worked (I have not gotten that far yet though). I just assumed they should

Exchange 2007 & Outlook 2007 autodiscover service Exchange Server Hi, I believe I have a pretty good handle on web services (availability service, OOF, OAB and Unifed Messaging service) and they all work fine. Outlook Anywhere even works correctly (as configured by the autodiscover service). These services are all published of each of the Exchange web services. If I choose the "test autoconfiguration" option in Outlook 2007 I can see that these are all set correctly. My issue is that my these services to the internet using basic authentication. What I do not understand is why Outlook 2007 is ever trying to access the external versions of the various Exchange web service the internal autodiscover service. No credential prompt happens at this stage. Surely the fact that Outlook has successfully found the SCP entry in Active Directory should tell it that it is currently for each of the Exchange web services? However, once Outlook receives the URLs from the autodiscover service it now tries to access the external versions which of course require a credential prompt! Why does Outlook want to access the external versions of the URLs? If Outlook chose only to use the internal versions then everything would work correctly. My question is

user is mapped to REALM \ user, which is what staff use to logon to Windows, OWA, etc with. OWA works fine. Using Outlook 2003 with a user logged on to Windows as REALM \ user everything works fine. Using Outlook 2007 with a user logged on to Windows as ADdomain \ user everything works fine. Using Outlook 2007 with a user logged on to Windows as REALM \ user things break. Specifically: - Outlook 2007 cannot access the autodiscover service. I think this happened when I added the SSL getting "Autodiscover to https: / / server.domain.com / Autodiscover / Autodiscover.xml FAILED (0x80040113)" in the log. - Outlook 2007 keeps prompting for username / password. When provided REALM \ user does not work, the ADdomain for collecting mail, accessing public folders, downloading OAB. So logging on to Windows (and therefore Outlook) with domain credentials works fine but using the REALM password that the domain account is

What is Outlook Anywhere and how does this compare to Outlook Web Access? Exchange Server Hi, I have Exchange 2007 and its Outlook Web Access with SSL on IIS. I presume this means that when the users logs onto OWA, via https: / / myserver / owa / , that their user id and password are encrypted. I notice that during the entire OWA session, the url remains https and therefore I guess this means all views in OWA are encrypted also (although in my case, IE says I have a and didn't bother going to a certificate authority). I keep hearing about Outlook Anywhere and the little reading I did about it, seems to indicate it does the

Cannot access Global Address Book Exchange Server Vista, outlook 2007, exchange 2007 When trying to access global address book, I get message: The connection to Microsoft exchange is unavailable. Outlook must be online or connected to complete this action. Offline is NOT checked, I get wrong???????? Exchange Miscellaneous Discussions Exchange Server 2007 (1) Exchange Server 2003 (1) Windows Vista (1) Outlook 2003 (1) Outlook 2007 (1) Outlook (1) Office (1) Vista (1) Hello, Thank you for your post. My name is Robbin correct. As I understand it, the issue is: When you open Global Address Book from Outlook 2007 on a Windows Vista computer, error message is received said " The connection to Microsoft would like to confirm: 1. Does this issue occurs to all of your clients with Outlook 2007 on Windows Vista computer? 2. Have you tried using OWA to check this issue? Is the result same? This issue may occur if the client