After renewing exchange server certificate withDomain CA ..we are getting..problems with setting out of office assistant (Error Msg... Your Out of Office settings cannot be displayed, because the server currently unavailable. Try again later) , OWA (error" 440 Login Timout" )and ' free/busy data could not be retrived ' when trying to schedule meeting with others.. Any Ideas..

Did you also change the host/URL you're clients are using? Try the following: Get-WebServicesVirtualDirectory | fl InternalURL,ExternalURL Do the URLs match what you expect? Next use the "Test E-Mail Autoconfiguration" option in Outlook, does it return the same URLs for Availability Service and OOF URL? Erik

Hi, When outlook 2007 wants to set OOF, it communicates with 'Exchange Web Servises' (EWS) virtual firectory in IIS. Outlook 2007 does not know path to EWS virtual directory in IIS so it queries the autodiscover service on Exchange 2007 server. Therefore the autodiscovery service must be correctly configured when using Outlook 2007. Outlook 2007 "finds" autodiscover service either by query AD or DNS. http://technet.microsoft.com/en-us/library/bb124251.aspx For the possible causes, please view the troubleshooting steps from the link below: http://www.proexchange.be/modules.php?name=News&file=article&sid=686 Thanks Allen

Thanks Allen for your reply, We created exchange certificate request from cmdlet and got new certificate from our intnernal CA and configured it through cmdlet in IIS, SMTP and POP and it did great job... We are now planning to use OWA from outside company and we want to have different URL for outside use.. If we got new exchange certificate from global certificate publisher do we still need to keep certificate from our internal CA or we need to remove certificate from internal ca and import certificate we got from global ca publisher... Any idea will help us... Thanks for your time... Tejas

Hi, If you need to access the OWA from external environment, I suggest we use public certificate as it can be trusted smoothly. In fact, you can use the previous certificate for internal communication and the public certificate for external user. To achieve this, we have to create another Web Site in IIS, that is so complicated compare to one certificate. Thus, I dont recommend this approach. Now please just import the public certificate to replace the original one in IIS. After that, the existing certificate will be replaced by the new one. Then please go into Exchange PowerShell and enabled it for Exchange services (IIS, SMTP and POP). Thanks Allen

Hi all, I'm getting a similar issue but I only notice it for one user so far, strangely everyone else in the company has no issues with setting their OOF. http://img56.imageshack.us/img56/6236/ooofm0.jpg When I run Get-WebServicesVirtualDirectory | fl InternalURL,ExternalURL I get the below info InternalUrl : https://khexg.domain.com/EWS/Exchange.asmxExternalUrl : https://owa.domain.com/ khexg = mail server Certificat is a San with subject names - DNS Name=owa.domain.com DNS Name=autodiscover.domain.com DNS Name=khexg.domain.com I've given up trying to get autodiscover working externally though my ISA 2006 firewall but would like some advice for troubleshooting this OOF error for a single user. Thanks Tommo.

Tommo, Do not give up yet...i feel your frustration. I was having the same OOF issues and my OWA is on ISA 2006. I reconfigured my AutoDiscover virtualdirectory, EWS, and OAB to point to my respective internal and external urls and now everything is working. Run the following: Get-GetWebServicesVirtualDirectory | fl internalURL,externalURL Verify the results has the correct internalURL and externalURL. Mine shows something similar to these: InternalURL : https://exchcas01.dankwax.root.com ExternalURL : https://mail.dankwax.com InternalURL : https://exchcas02.dankwax.root.com ExternalURL : https://mail.dankwax.com InternalURL : https://exchcas03.dankwax.root.com ExternalURL : https://mail.dankwax.com Also, run Get-OutlookProvider and make sure the results has your servername under Server. Before when mine was not working it showed something like this: Name Server CertPrincipalName TTL EXCH 1 EXPR 1 WEB 1 To get it working i set it to my server and now the working results is something like this: Name Server CertPrincipalName TTL EXCH exchcas01 1 EXPR exchcas02 1 WEB exchcas03 1 Lastly, run Get-AutoDiscoverVirtualDirectory. The results should look something like this: Name Server InternalUrl AutoDiscover (Default Wed Site) exchcas01 https://exchcas01.dankwax.root.com AutoDiscover (Default Wed Site) exchcas02 https://exchcas01.dankwax.root.com AutoDiscover (Default Wed Site) exchcas03 https://exchcas01.dankwax.root.com Hope this help you resolve some if not all of your OOF issues.

Reason 1: Wrong Autodiscover Service settings Reason 2: Wrong certificateReason 3: Wrong permission settings on the EWS virtual directory.Reason 4: Logged on with another user account None of these solutions are working. I have been through all my settings. I made sure all my urls are pointing to the correct place and have tested them to make sure I get to the xml pages. I downloaded the hotfix from microsoft but it says the update is not needed on this website. Any other solutions would be a BIG HELP! Thanks, Mark

This link (http://www.proexchange.be/modules.php?name=News&file=article&sid=686) no longer seems to work. I have a situation as described below, where I have one person that can't get OOF to work. Everyone else is fine. The one person can reset OOF using OWA. EWS authentication: anonymous, basic, Windows enabled; others disabled. Would certainly appreciate any suggestions.

run " Get-WebServicesVirtualDirectory | fl InternalURL,ExternalURL" from where? i run it from the command promp and the system has no idea what this is

I ran into the same issue. there is no ISA in between in my Exchange 2007 SP2 Ent. After spending a couple of day and with MSFT Support we figured out and it was a DNS issue. Make sure you have correct DNS entries. I face this problem to all my internal users. The best way to check it edit your host file test it before making any changes to your DNS. cheer:)

Exch Power Shell - Exchange server