Outlook 2007: 'Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later. users using outlook 2003 can configure out of office without no problem. We are using exchange 2007. Using out of office via Webmail works fine.I did this Get-webservicesvirtualdirectory | fl identity,internalurl,externalurl

This is what i get below[PS] C:\Documents and Settings\Administrator.GORKANA\Desktop>Get-webservicesvirt ualdirectory | fl identity,internalurl,externalurl

Thanks for your reply.We are using exchange 2007Some users are using outlook 2003 and some of them 2007.Users using outlook 2003 have to problem in using out of office.Users using outlook 2007 are the ones getting the error message that the server is unavailable of which i am part of.As i said i am from an AS 400 background. I know our exchange server is called grkms1. Everything works fine, webmail, sending and receiving except Out of Office for users using Outlook 2007. I don't think this is a client issue.How can i tell if this is resolved correctly? Out of office works fine with Webmail.I have looked at the autodiscover which i think is affecting us. I was trying to create a new autodiscover directories using the exchange cmd shells.Do you think this is the issue if not can you help me with commands.Many thanks+44 79 407 44 100

On your CAS, you should replace the certificate with one that has names for OWA, Autodiscover, CASNetBiosName, CasNetBiosNAme.domain.com.

Once that is on your CAS, you should re-configure your InternalURLs and ExternalURLs for all your services. You should verify that they are pointed to an FQDN that is resolved both internally and externally on your network.

Specifying the InternalURL updates the Service Connection Point (SCP) within Active Directory. Outlook 2007 clients automatically locate this in AD and connect to the appropriate InternalURL. For clients who are not domain joined or are on the internet (don't have direct connectivity to AD), you need to specify the -ExternalURL which clients get from the Autodiscover Service.

So you also need to make sure you specify the -AutodiscoverServiceInternalURI and make sure that it uses an FQDN that's specified in the certificate. You can set this by doing something such as: Set-ClientAccessServer -Identity CASServer -AutoDiscoverServiceInternalURI https://mail.domain.com/Autodiscover/Autodiscover.xml

The EWS service is the web service that allows access to the OOF. So make sure you specify the correct URL for that service: Set-WebServicesVirtualDirectory -Identity “CASServer\EWS (Default Web Site)” -InternalURL https://mail.domain.com/EWS/Exchange.asmx -ExternalURL https://mail.domain.com -BasicAuthentication:$true

Thanks The E, for such a valuable post. In addition to this, i want to add more steps.

This is a known issue, but it happens only in few circumstances. This is the issue if Autodiscover is not working properly, which obviously support only Outlook 2007. Due to this your users are not able to set OOOA.

Just share few more details that is it happening from internal and through Outlook Anywhere also.

I'm having the same issue with this affecting only non-domain joined users, using Outlook 2007. In the knowledge base article it talks about a software fix and also creating a srv record in DNS. My question is that it makes a statement of: "In your external DNS zone, remove any HOST (A) or CNAME records for the Autodiscover service." Does this mean if I have a host record of autodiscover (which I do), that I need to delete it? Also, does this record need to be implemented in conjunction with the software fix or are they independant of each other?

I too am experiencing the same issue. I'd like to point out that this issue and its specific symptoms (which from what I've read, have yet to be fully disclosed) have popped up recently. The rollup package referenced in KB 940881 is from August '07 and, if I understand Outlook Anywhere connectivity, only pertains to clients on the LAN as external clients don't give a rip about SRV or SCP records; they'll use the Outlook 2007 coded and appended (yourdomain.com and autodiscover.yourdomain.com respectively) DNS information and then your properly registered public A record will do the rest.

bkebbay, please confirm that external clients (Outlook Anywhere) are experiencing the issue. Identifying this detail will help steer us all in the right direction.