Hi We have an issue with users wanting to set up their OOF on exchange 2007/2010 using outlook 2007/2010. users are getting the following error "your oof settings cannot be displayed, because the server is currently unavailable, try agian later". users can set OOF using OWA but are having intermintent issues setting it up internally and externally. Please advise. Regards, Sam

This subjet has been discussed numerous times before, at least two or three times a week, so check the forums. Primary cause on SBS is not setting up the server using the wizards, not having the correct DNS entries in externally for autodiscover and not having the SSL certificate setup correctly. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi Simon, Do you have a best practice guide on setting for setting up Exchange/Auto discover on SBS. We have a valid SSL cert and the autodiscover works internally when testing it using the "test email auto configuration" setting in outlook. Should the auto discover internally point to the EWS virtual directory or the auto discover? i have seen several posts on forums and each say something different. your help is much appreciated. Thanks SZ

It is no different to setting up autodiscover on the full product. Unless your DNS provider supports SRV records you need to use a Unified Communications Certificate, with the remote.example.com name as set by SBS as the common name. Running the wizards in SBS will configure everything internally. Don't try and configure things manually. A combination of the initial setup wizards and the fix my network wizard will ensure the internal things are configured in the way that they should. Externally, ensure that remote.example.com and autodiscover.example.com (where example.com is your public domain as used in the email addresses) are pointing to your external IP address as A records. It isn't as complex as some people try to make out. Where it gets complicated is when people start trying to change things around without understanding how it all fits, when in many cases all that is required is to get the SSL certificate installed correctly. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

So the OOF issue occurs when Outlook is connecting externally? If this is the case, my suggestion is: Make sure the external Autodiscover url is able to be resolved by your client machine outside your network. The external Autodiscover URl can be: https://yourSMTPsuffix/autodiscover/autodiscover.xml. Make sure the external Availability service URL is setup and resolved by the client computer. Refer to: http://technet.microsoft.com/en-us/library/bb201695.aspx Make sure the certificate name includes your SMTPsuffix. Check the permission settings. Refer to: http://blogs.technet.com/b/exchange/archive/2010/09/23/3411146.aspx Hope it is helpful.Best Regards Fiona Liao E: v-fiolia@microsoft.com

By the way, for Exchange issues in SBS, it is recommended to posted in http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/threads. Your understanding would be appreciated. Best Regards Fiona Liao E: v-fiolia@microsoft.com

It is no different to setting up autodiscover on the full product. Unless your DNS provider supports SRV records you need to use a Unified Communications Certificate, with the remote.example.com name as set by SBS as the common name. Running the wizards in SBS will configure everything internally. Don't try and configure things manually. A combination of the initial setup wizards and the fix my network wizard will ensure the internal things are configured in the way that they should. Externally, ensure that remote.example.com and autodiscover.example.com (where example.com is your public domain as used in the email addresses) are pointing to your external IP address as A records. It isn't as complex as some people try to make out. Where it gets complicated is when people start trying to change things around without understanding how it all fits, when in many cases all that is required is to get the SSL certificate installed correctly. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.