Hello,I'm trying to get outlook 2007 to work with an exchange 2007 on the HMC platform. (outlook anywhere)So far sending, and receiving emails works correctly with the Outlook client.However, when I open the calendar and try to create a new appointment, I can type it, but when trying to save nothing happens > no error message.
The strange thing is that via the owa I can create it perfectly.Via the outlook client it's possible to edit that appointment or delete it.
When trying to check the calendar options > free/busy options, and try to add a permission, I get "the bookmark is not valid" Also the address book isn't working in outlook.When testing with "test email autoconfiguration" I get : "autoconfiguration was unable to determine your settings"> the log files shows that the outlook is trying to lookup via https://customerdomain.be/autodiscover.xml and the next options, but can't find it.Does anyone know if it's related to the calendar problem, and how I can resolve it?
grts,
Dimi
You must make sure that Autodiscover is working fine!
Have a look at these postshttp://www.pro-exchange.be/blogs/exchange2007/archive/2009/03/17/your-out-of-office-settings-cannot-be-displayed-what-s-wrong.aspxhttp://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
http://msexchangeteam.com/archive/2007/04/30/438249.aspxhttp://technet.microsoft.com/en-us/library/bb332063(EXCHG.80).aspx
Ok, tnx Johan!I'll take a look at the links
I did take a look at the autodiscover today and it's possible to resolve via external DNS now. (autodiscover.customername.be)Problem now is that since we're using the HMC, it gives an error :"Certificate name validation failed""Host name autodiscover.customername.be does not match any name found on the server certificate CN=*.hmcdomain.be, O=*.hmcdomain.be, OU=Domain Control Validated, C=BE "
To use wildcard certificates you need to do additional configuration.It is not supported by default
Take a look at this posthttp://www.pro-exchange.eu/modules.php?$1&name=News&file=article&sid=898
From a hoster perspective using the wildcard for *.hmcdomain.be is probabely not very interesting. Most likely your customers will have their own email domain which is used for the autodiscover process.
Therefore it's better to use the HTTP Redirect method from Outlook to redirect the client to a different URL which is SSL protected with a certificate using a single subject name (or SAN's if you need it).
An example:
Hoster Org us consolidatedmessenger.com
Customer Organization is contoso.com
You have a publishing rule and listener on ISA (10.10.10.1) that denies HTTP requests and redirects you to the URL https://mail.consolidatedmessenger.com/autodiscover/autodiscover.xml
You have a second publishing rule and listener on ISA (10.10.10.2) that accepts HTTPS requests and has a certificate for mail.consolidatedmessenger.com. This publishing rule has all your virtual directories for Exchange published (OA, EAS, EWS, AUTODISCOVER).
In order to make this work for outlook you simply create a autodiscover.contoso.com DNS record that points to 10.10.10.1.
Now when Outlook will connects to 10.10.10.1 ISA will issue a redirect to outlook and you will receive a one-time prompt that you have to accept. Afterwards outlook will automatically redirect itself to https://mail.consolidatedmessenger.com/autodiscover/autodiscover.xml
See this blog posting for more info: http://blogs.msdn.com/brad_hughes/archive/2007/12/18/autodiscover-http-redirect-method-using-isa-instead-of-a-second-web-site.aspx
Hope this helps for you...
Sincerely,
Tonino BrunoTonino@btconsulting.be | ICT Consultant | B.T. Consulting bvba
Thanks Tonino!We just placed an ISA server in between, so I'll let you know if the problem is solved.
grts