I must have read 200 posts in the past 2 days from people that have similar problems, yet none have provided a solution for me. I have an SBS 2008 server running exchange 2007 (sp1, rollup 4). Everything has been running great for 2 years until last week when someone noted that the "Out of Office Assistant" did not work from the outlook client (most people who've used that in the past have been remote users accessing OWA where out of office works just fine). Attempting to access Out of Office results in the error: "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later". I knew immediately that the issue was related to autodiscover (as we did not have an autodiscover DNS record). We already had a cert at remote.mydomain.com, so I followed Microsoft's directions to configure an SRV record and that immediately began working (i.e. I can setup outlook 2007 profiles via autodiscover just fine (both on the LAN and via outlook anywhere). I have also run the test at https://www.testexchangeconnectivity.com and it gives me a thumbs up - shows everything A-OK. I can also run the "Test Email Autoconfiguration" from outlook and it completes with zero errors. However, both Out of Office and Free/Busy information remain unavailable to me. I'm stumped. It appears my autodiscover is working just fine, but I don't know what else to pursue.

Hi, If auto-discover is working fine then it might be due to outlook client issue, have a look into this article\KB which suggest to changed in registry entry,http://msmvps.com/blogs/bradley/archive/2009/02/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable.aspx http://support.microsoft.com/kb/958934/EN-US Do let us know if this don't resolve the issue. Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Hi Does the OOO work from OWA? Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Yes, Out of Office works fine from OWA.

Ok, correct me if I'm wrong now, but you have a 3rd part certificate with the name remote.domain.com installed and that works like it should? In that case you have run some commands to get everything to work Verify everything before doing any changes, this is done by Get-ClientAccessServer | fl AutoDiscoverServiceInternalUr, AutoDiscoverServiceExternalUri Get- WebServicesVirtualDirectory | fl internalurl, externalurl Get- UMVirtualDirectory | fl internalurl, externalurl Go to Server Configuration => Client Access => OAB (Default Web Site) Properties ------- Set-ClientAccessServer -Identity hostname -AutoDiscoverServiceInternalUri https://remote.domain.com/autodiscover/autodiscover.xml Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -internalurl:https://remote.domain.com/EWS/Exchange.asmx Set-UMVirtualDirectory -Identity "UnifiedMessaging (Default Web Site)" -InternalUrl:https://remote.domain.com/UnifiedMessaging/Service.asmx Exchange Management Console: Server Configuration => Client Access => OAB (Default Web Site) Properties: Internal URL: https://remote.domain.com/OABJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

I am awaiting a call from Microsoft to provide me with that hotfix, I'll report back if it has any bearing.

Correct, I have a rapidssl cert for remote.mydomain.com that works fine. Running the command: Get-ClientAccessServer | fl AutoDiscoverServiceInternalUr, AutoDiscoverServiceExternalUri returns 2 blank lines, so I ran the Set command you provided and I still get 2 blank lines when running the Get command afterwards. Running the command: Get- WebServicesVirtualDirectory | fl internalurl, externalurl returns the same result for both internal and external URL (https://remote.mydomain.com/EWS/Exchange.asmx Running the command: Get- UMVirtualDirectory | fl internalurl, externalurl returns the same result for both internal and external URLs (https://remote.mydomain.com/UnifiedMessaging/Service.asmx

Oh and I also checked the Exchange management console, server config, client access, OAB (SBS Web Application) and the internal URL is already https://remote.mydomain.com/OAB

I also ran this command (as found in another forum post on the subject) via the exchange shell on the server: test-outlookwebservices |fl and got the erorr: 1013, (401) Unauthorized Is my issue related to permissions somewhere?

The hotfix noted earlier did not fix my issue.

Hi, Please post test-OutlookWebservices |fl command in EMS, then post here. Thanks AllenAllen Song

[PS] C:\Windows\System32>test-OutlookWebservices |fl Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address administrator@mydomain.com. Id : 1007 Type : Information Message : Testing server server.mydomain.local with the published name https://remote.mydomain.com/EWS/Exchange.asmx & https://remote.mydomain.com/EWS/Exchange.asmx. Id : 1019 Type : Information Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://remote.mydomain.com/autodiscover/autodiscover.xml. Id : 1013 Type : Error Message : When contacting https://remote.mydomain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (401) Unauthorized. Id : 1006 Type : Error Message : The Autodiscover service could not be contacted.

Do I need to run the command with a different user? (if so how do I do that?) It is using administrator@mydomain.com and that's not an address we use.

Hi, Is there any error received on the other services OAB, Free/Busy except for OOF? Whether all the users have the OOF issue? Test-outlookwebservices -identity user@domain.com |fl Allen Allen Song

I re-ran the test with several accounts and got the same unauthorized error (copied below). Yes we are also having problems with OAB, Free/Busy and OOF and yes all users have the issue. [PS] C:\Windows\System32>Test-outlookwebservices -identity user@mydomain.com |fl Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address user@mydomain.com. Id : 1013 Type : Error Message : When contacting https://remote.mydomain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (401) Unauthorized. Id : 1006 Type : Error Message : The Autodiscover service could not be contacted.

I solved the problem by disabling loopback (see steps below), BUT is this the best solution? Could this cause other issues or open vulnerabilities? 1.Click Start, click Run, type regedit, and then click OK. 2.In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa 3.Right-click Lsa, point to New, and then click DWORD Value. 4.Type DisableLoopbackCheck, and then press ENTER. 5.Right-click DisableLoopbackCheck, and then click Modify. 6.In the Value data box, type 1, and then click OK. 7.Quit Registry Editor, and then restart your computer.

Thanks for sharing Don't forget to set your reply as answer, it help others with same issue to find the solutionJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi, Yes, that's the correct answer. You can refer to the below article to confirm that. http://support.microsoft.com/?id=896861 Thanks AllenAllen Song

I couldn't get any of the answers above to work. BUT...what I did notice (using the Outlook connection diagnostics), was that Outlook tries to use the WAN domain name for the Exchange server...and then I wondered if it was trying to contact/download the Exchange/SBS2008 server via WAN, rather than LAN? I then edited the hosts file on the client (a terminal server) and inserted the LAN IP and the WAN domain name - and voila, it worked. All users on the terminal server was all of the sudden able to use Offline Assistant in Outlook 2007. How to (hosts file way) Say that your LAN IP of your SBS2008 server is 192.168.0.2 and your server's WAN domain name with SSL is remote.yourdomain.com. Now edit the hosts file (on the client PC) in C:\Windows\System32\Drivers\etc\hosts file and add this at the bottom (be sure to end the file with a few extra line breaks/carriage returns): 192.168.0.2 remote.yourdomain.com This worked for me.