Proxy - OWA - ISASERVER
Greetings!
Hear me out. We have exchange 2007 (with sp3), ISA 2006.
-Owa address is: servername.company.com
-ISA redirects that address to: servername2.company.com
If we presume that ISA is using a different certficiate then exchange owa we have a problem.
Example of the problem.
User settings in Outlook 2007 for proxy are set to redirected address: servername2.company.com and
basic authentication. But somehow after user reconnects on exchange server this settings are
automatically changed to owa primary address: servername.company.com and then he receives an error
message with certificate issue. How can we set up a permanent settings for proxy address to be
that redirected address servername2 and not primary owa address?
I hope you understand my problem. With best regards,bostjanc
March 17th, 2011 3:11am
Hi
The Autodiscover Service and the Outlook Provider
The Autodiscover service sends the request to the Outlook provider, which then uses the Services
Discovery API to retrieve the values in Active Directory. After the values have been returned, the data is passed to the Autodiscover service, which returns the information to the client in an HTTP response. This HTTP response contains the relevant values
in XML.
There are three Outlook provider settings, as follows:
The WEB setting contains the best URL for Outlook Web Access for the user to use. This setting is not required for Exchange 2007.
The EXCH setting references the Exchange RPC protocol that is used internally. This setting includes port settings and the internal URLs for the Exchange services that you have enabled.
The EXPR setting references the Exchange HTTP protocol that is used by Outlook Anywhere. This setting includes the external URLs for the Exchange services that you have enabled, which are used
by clients that access Exchange from the Internet.
http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80).aspx
Maybe you should find the reason why owa will be changed.
It is the setting of your local pc.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2011 11:45pm
Thank you for you answer, but this problem is becoming to be globally. Firstly I though maybe some Office update corrupted it, cause it used to work before. We haven't changed anything else except upgrading exchange to sp3 about 4 months ago. You are refering
that it must be a client setting on local pc. I have all the users with the same mistake. Can you point me to which direction should i change the settings?
Thank you for the answers, with best regards,bostjanc
March 21st, 2011 6:44pm