Automatic Replies (Out of Office) / Free Busy Information Issues (Exchange 2010 SP1 & Office 2010)

All, Apologies for the long post although I thought I would post as much information as possible.

I am currently experiencing alot of issues with calendars and OOF within our Exchange organisation. Most clients (All of them except 1) are recieving:

'Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.'

Also, in the scheduling information, users cannot retrieve user free / busy informaiton.

I have looked at numerous articles for months trying to fix this issue with no avail. I am aware there are quite a few articles in relation to this but none have helped. Here is our scenario:

Windows 2008 R2 Enterprise
- Latest updates (12/04/2011) Including Microsoft .NET Framework 4.0 and SP1

Exchange 2010
- Latest updates (12/04/2011) Including SP1

- Approximately 170 Users using a mixture of Office 2003 / 2010.
- All accounts were migrated from Exchange 2003 directly to Exchange 2010

Autodiscover settings seem to be correct and when I test Email-AutoConfiguration from Outlook clients everything looks good and the Autodiscover service URL succeeds with no errors.

I have a wildcard certificate for our Exchange server for all our records and www.testexchangeconnectivity.com reports no issues with autodiscover and we are using split DNS. I have also recreated both the EWS and Autodiscover virtual directories.

Ive found that Test-OutlookWebServices get 401 Unauthorised on the EWS Directory. The EWS directory has both Windows Auth and Basic Auth set to true. I also get an invalid URL looking for an internal site which is not set in any settings.

Any info would be appreciated

find attached output:

[PS] C:\Windows\system32>test-outlookwebservices


RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1019
Type       : Information
Message    : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1006
Type       : Information
Message    : Contacted the Autodiscover service at https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1016
Type       : Information
Message    : [EXCH] The AS is configured for this user in the Autodiscover response received from https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1015
Type       : Information
Message    : [EXCH] The OAB is configured for this user in the Autodiscover response received from https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1014
Type       : Information
Message    : [EXCH] The UM is configured for this user in the Autodiscover response received from https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1016
Type       : Information
Message    : [EXPR] The AS is configured for this user in the Autodiscover response received from https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1015
Type       : Information
Message    : [EXPR] The OAB is configured for this user in the Autodiscover response received from https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1014
Type       : Information
Message    : [EXPR] The UM is configured for this user in the Autodiscover response received from https://mail.DOMAIN.com/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1022
Type       : Success
Message    : Autodiscover was tested successfully.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1104
Type       : Error
Message    : The certificate for the URL https://SRV.DOMAIN.LOCAL/Autodiscover/Autodiscover.xml is incorrect. For SSL to work, the certificate needs to have a subject of SRV.DOMAIN.LOCAL, instead the subject found is *.DOMAIN.com. Consider correcting service discovery, or installing a correct SSL certificate.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1106
Type       : Information
Message    : Contacted the Autodiscover service at https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1116
Type       : Information
Message    : [EXCH] The AS is configured for this user in the Autodiscover response received from https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1115
Type       : Information
Message    : [EXCH] The OAB is configured for this user in the Autodiscover response received from https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1114
Type       : Information
Message    : [EXCH] The UM is configured for this user in the Autodiscover response received from https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1116
Type       : Information
Message    : [EXPR] The AS is configured for this user in the Autodiscover response received from https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1115
Type       : Information
Message    : [EXPR] The OAB is configured for this user in the Autodiscover response received from https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1114
Type       : Information
Message    : [EXPR] The UM is configured for this user in the Autodiscover response received from https://SRV.DOMAIN.LOCAL:443/Autodiscover/Autodiscover.xml.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1122
Type       : Success
Message    : Autodiscover was tested successfully.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1013
Type       : Error
Message    : When contacting https://mail.DOMAIN.com/EWS/Exchange.asmx received the error The request failed with HTTP status 401: Unauthorized.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1025
Type       : Error
Message    : [EXCH] Error contacting the AS service at https://mail.DOMAIN.com/EWS/Exchange.asmx. Elapsed time was 789 milliseconds.

RunspaceId : 3e733bd3-a29c-47aa-8141-12b969781fb2
Id         : 1026
Type       : Success
Message    : [EXCH] Successfully contacted the UM service at https://mail.DOMAIN.com/EWS/Exchange.asmx. The elapsed time was 15 milliseconds.

Open in new window


-----------------------------------------

get-OutlookProvider:

Name                          Server                        CertPrincipalName             TTL
----                          ------                        -----------------             ---
EXCH                          mail.DOMAIN.com	              msstd:mail.DOMAIN.com    1
EXPR                          mail.DOMAIN.com                msstd:mail.DOMAIN.com    1
WEB                           mail.DOMAIN.com            msstd:mail.DOMAIN.com    1

Open in new window


-----------------------------------------

[PS] C:\Windows\system32>get-WebServicesVirtualDirectory | fl


RunspaceId                      : 3e733bd3-a29c-47aa-8141-12b969781fb2
CertificateAuthentication       :
InternalNLBBypassUrl            : https://mail.DOMAIN.com/EWS/Exchange.asmx
GzipLevel                       : Off
Name                            : EWS (Default Web Site)
InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
LiveIdSpNegoAuthentication      : False
WSSecurityAuthentication        : False
LiveIdBasicAuthentication       : False
BasicAuthentication             : True
DigestAuthentication            : False
WindowsAuthentication           : True
MetabasePath                    : IIS://SRV.DOMAIN.LOCAL/W3SVC/1/ROOT/EWS
Path                            : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\ews
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
Server                          : SRV
InternalUrl                     : https://mail.DOMAIN.com/EWS/Exchange.asmx
ExternalUrl                     : https://mail.DOMAIN.com/EWS/Exchange.asmx
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
DistinguishedName               : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=VB,CN=Servers,CN=Exchange Administr
                                  ative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN Organisation,CN=Mi
                                  crosoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=priv
Identity                        : SRV\EWS (Default Web Site)
Guid                            : dbe6c346-6f3f-4a31-9572-1ef4e69fd596
ObjectCategory                  : DOMAIN.LOCAL/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass                     : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged                     : 28/02/2011 10:10:23 AM
WhenCreated                     : 28/02/2011 9:55:12 AM
WhenChangedUTC                  : 27/02/2011 11:10:23 PM
WhenCreatedUTC                  : 27/02/2011 10:55:12 PM
OrganizationId                  :
OriginatingServer               : DC.DOMAIN.LOCAL
IsValid                         : True

Open in new window

sennellAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sennellAuthor Commented:
Thanks DrUltima,

I have now solved this issue.

The issue was in relation to the actual folder permissions for the EWS directory under "C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS".

Even though the permissions were set correctly on the actual IIS site, for some reason the "Anonymous" user was missing completely from the Directory itself. Hence the 401 Unauthorised. I added Read, Read + Execute and List folder contents as permissions to the Anonymous user on the EWS folder and OOF started working. All calendars and OOF are now fully functional.

Cheers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sennellAuthor Commented:
worked it out overnight
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.