Using classic Outlook for Windows in business environments
The most relevant diagnostic from the available guidance is to compare the Autodiscover/EWS path between the affected PC and the working terminal server, then check the server-side logs that capture free/busy requests.
For free/busy, use this comparison path:
- On the affected classic Outlook profile, run Test E-mail AutoConfiguration.
- Hold Ctrl, right-click the Outlook icon in the notification area, and select Test E-mail AutoConfiguration.
- Test Autodiscover for the affected user and note the returned EWS URL.
- Run the same test on the working terminal server session for the same mailbox.
- Since Autodiscover already looked the same in the comparison, that points away from a simple Autodiscover mismatch.
- If free/busy is failing, validate the EWS endpoint directly.
- Use the EWS URL returned from Autodiscover.
- Browse to that URL or run
Invoke-WebRequest -Uri "<endpoint URL>" -Verbose. - Preferably test from an external network when validating the published URL.
- If the issue is in a hybrid or published path, compare the request handling in logs.
- Check IIS logs for free/busy requests that return 503 Service Unavailable in
%SystemDrive%\inetpub\logs\LogFiles\W3SVC1. - If the request is not in
W3SVC1, check%SystemRoot%\System32\LogFiles\HTTPERR. - These logs help identify which server handled the request and whether IIS or another web component returned the failure.
- Check IIS logs for free/busy requests that return 503 Service Unavailable in
- If a load balancer is in the path, compare requests through it with a controlled test to the correct backend.
- Keep the published hostname and certificate validation.
- Do not leave temporary routing or Hosts-file overrides in place after testing.
For Automatic Replies, the available guidance confirms a known classic Outlook issue where opening Automatic Replies can fail with:
“Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.”
That issue was first observed with Current Channel Version 2505 (Build 18827.20128), occurs starting with builds 18510.10000+, and is fixed in Version 2508 Build 19127.20000.
Given that the same mailbox works in Outlook on the web and on the terminal server, the first comparison to make is the Office channel/build on the affected PCs versus the terminal server. If the PCs are on an affected build and the terminal server is not, that directly matches the known issue pattern for Automatic Replies.
Supported workaround for Automatic Replies:
- Set automatic replies in Outlook Web Access by opening the shared mailbox in a separate browser window, then Settings > Account > Automatic replies.
- For classic Outlook, switching Office to Semi-Annual Enterprise Channel avoids the bug until the fixed build is installed. After changing channel, use File > Office Account > Update Options > Update Now.
Based on the documented troubleshooting, the best logs/diagnostics to compare are:
- Test E-mail AutoConfiguration output, especially the returned EWS URL
- IIS W3SVC1 logs for free/busy requests
- HTTPERR logs if the request never reaches normal IIS logging
The context does not provide a separate Outlook client log specifically for comparing failed versus successful Automatic Replies requests on two machines. The strongest documented path is to compare build/channel for the Automatic Replies symptom and compare Autodiscover/EWS plus IIS/HTTPERR logging for the free/busy symptom before making any organization-wide EWS policy change.