The error “Your Automatic replay setting cannot be displayed because the server is currently unavailable” usually occurs when AutoDiscover feature has not been published or configured and Outlook Anywhere has already been enabled.
At first run this command to check whether AutoDiscovery has been configured or not. Steps are described below to check the same.
1). Run the outlook and click on the notification area appearing in the bottom right corner of your screen.
2). Now click on the Outlook icon, holding CTRL button.
3). Now select Test Email AutoConfigration
Fill the Email Address and password In the next window that will appear after click on the Test E-mail AUtoconfigration. Uncheck the option Use Guessmart. Now click on the Test
Now check out the results. If you got unsuccessful results means AutoDiscovers is not configured for your email
If you are getting the successful output, than the missing URL for the Out of Office (OOF) service is causing the problem
After a successful AutoDiscover check for OOF URL whether it is correct or not. For that look in the result tab of Test Email AutoConfigration for OOF URL. Look for the protocol group as shown below:
1). Disable the protocol Exchange RPC and enable Exchange HTTP when you are using Outlook internally.
2). When you are using Outlook Externally then use protocol Exchange HTTP
Now if you have confirmed that your OOF URL is wrong. You can contact with your Exchange Administrator to correct the same.
That may happen due to the wrong credentials that you are passing to the Exchange CAS Server. Add the registry value to solve it:
You can also change your OOF message using OWA. Follow the following steps for the same:
In Outlook 2007: To set automatic replies in Outlook 2007 select Out of Office Assistant on the top right corner.
In Outlook 2010: From the top right corner, select the option Set Automatic Replies
In Outlook 2013: In Outlook 2013 click on the gear icon available on the top right corner and select option Set Automatic Replies.
Exchange administrator can solve the issue by setting up the correct internal and the external URLs for EWS using the PowerShell Cmdlet (Set-WebServicesVirtualDirectory). To check the current setting use Get- WebServicesVirtualDirectory Cmdlet. You can also use Remote connectivity analyzer developed by Microsoft for the verification.