Using HTTP for Autodiscover (well all web services)
-
18 Juni 2010 17:02
So trying to configure the entire Web services to use HTTP instead of HTTPS; nothing is going to be published directly to the internet and client does not have internal CA nor do they wish to buy certs for somthing that will stay internal.
So OWA works just fine. Having a problem with Autodiscover, when I test-auto-configuration settings in Outlook 2007 I get a HTTP status error 404 for the SCP that I have configured for Autodiscover using HTTP
found this article and tried it, http://technet.microsoft.com/en-us/library/ee633481.aspx no luck
found this and tried it as well, http://blogs.msdn.com/b/dvespa/archive/2009/12/22/how-to-configure-a-http-endpoint-for-exchange-web-services-in-exchange-2010.aspx again no luck
Running Exchange 2010 with Rollup 3. Any help on getting this sto work?
Sean McNeill Microsoft Gold Partner http://staterainfrastructure.blogspot.com/
Semua Balasan
-
18 Juni 2010 18:21
You have a couple of things to deal with here. Outlook and Exchange 2010 is naturally wanting to do SSL.
So on the client side, you need to make sure that "Encrypt data between Outlook and Exchange" is unchecked on the Outlook client profile settings. Or you can disable it for everyone on the server side. Set-RpcClientAccess –identity servername –EncryptionRequired $false.
Also it is not documented very well, but you pretty much need to set CAS up for SSL Offloading.
I threw up a quick post on my blog that covers SSL offloading with a HLB. Just following from the Outlook Anywhere section on. Hope this helps, this post is a work in progress. http://howdouc.blogspot.com
Note the edit to the web.config files to force httpTransport.
Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com- Disarankan sebagai Jawaban oleh TWHarringtonMVP 18 Juni 2010 18:25
- Ditandai sebagai Jawaban oleh Sean McNeillMVP 25 Juni 2010 15:27
-
18 Juni 2010 20:28
If the only reason you are trying to use HTTP instead of HTTPS is because you don't want to purchase external CA's then you could install a CA server on your own network for free and issue your own certificates. Just a thought.
Dave
-
22 Juni 2010 3:29Moderator
If the only reason you are trying to use HTTP instead of HTTPS is because you don't want to purchase external CA's then you could install a CA server on your own network for free and issue your own certificates. Just a thought.
Dave
Yes, You could use self signed certificate in your exchange server.
Your expertise never fails to impress! -
22 Juni 2010 14:33
Just a general comment (and warning), if you plan on using Outlook Anywhere with Basic authentication, SSL is a requiment. You also can't use self signed certs for Outlook Anywhere.
Casper Pieterse, Principle Consultant - UC, Dimension Data South Africa, Microsoft Certified Master: Exchange 2007 -
22 Juni 2010 14:54
Just a general comment (and warning), if you plan on using Outlook Anywhere with Basic authentication, SSL is a requiment. You also can't use self signed certs for Outlook Anywhere.
Casper Pieterse, Principle Consultant - UC, Dimension Data South Africa, Microsoft Certified Master: Exchange 2007Someone has used self signed cert with Outlook Anywhere.
Plz have a look into this:
Regards,
Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com -
22 Juni 2010 15:04
Looks like this behaviour has changed with Outlook 2010. You will always receive a warning using a self-signed cert with Outlook 2010.
Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com
.png)
