Out of Office Error

If I remember rightly we had much the same issue, this article explain what we had to check i think, although I'm not convinced we ever fixed it. We're on Office 365 now which is wonderful.

http://www.slipstick.com/exchange/cmdlets/out-of-office-doesnt-work-with-exchange-2007-or-2010/

Have you tried using OWA to set out of Office? I'm pretty sure that still worked fine for us even though the client didn't.

What version of Outlook are you using? Perhaps Outlook 2013 might work where 2007 and 2010 don't.

Cheers

Ed

HKFuey,
Let's start checking on a server level as opposed to the client.  Open your exchange management shell and let's do some trouble shooting for the users in question.

http://exchange-tools.blogspot.com/2015/02/how-to-check-out-of-office-status-on.html

I tried Get-MailboxAutoReplyConfiguration "username" and it gives details of message, font etc. I really need to resolve the Out of Office error.

If we use Outlook Web Access we can change the settings.

This has happened since migrating from Exchange 2007 to 2010

I want you to try this with one of the client machines if you haven't already.

https://support.microsoft.com/en-us/kb/2596516

Ed's link is correct but if your 2007 exchange environment is still standing you may want to run the command from powershell in exchange 2007.

CAUSE

Users were being directed to their local Exchange forest for the web services that provide both sets of information. Because Outlook was now connected to the new Echange forest in the new domain, it broke both the Out-of-Office Assistant and users were unable to view free/busy data.

FIX

I applied the following command from the Exchange Powershell on the old Exchange forest directing the users to the OWA of the new domain/forest.

Get-WebServicesVirtualDirectory -Server <OLD CAS> | Set-WebServicesVirtualDirectory -InternalUrl https://OWA.newdomain.com/ews/exchange.asmx -ExternalUrl https://OWA.newdomain.com/ews/exchange.asmx

Once this was done, clients were able to resolve this from the old domain and bothe the Out-of-Office Assistant and Free/Busy started to work.

Hi foxluv

Thanks for that, unfortunately the old server is now deleted. We got a guy in to do the upgrade and it did not go very well. This is just one of the issues.

It's worth checking Autodiscover etc works, like I said I don't think we ever got ours to work other than via OWA, but all the problems I had with 2010 basically stemmed from autodiscover

The remote Analyser tool is good for tetsing your setup

https://testconnectivity.microsoft.com/

HkFuey,
On one of those outlook clients in question, remove the outlook profile and re-add it.  When you re-add it , it should link up to the exchange correctly.  Try that.

https://testconnectivity.microsoft.com/

Tried the above link a few times, it failed every time. Auto-discovery Problem?

Definitely

Ok I just found a post that dipersp had some major input that helped somebody out that had the same issues.  Run the commands to verify where everything is pointing.  I'm sure this link I was on with dipersp's suggestions will help you out.

https://www.experts-exchange.com/questions/28799119/Change-exchange-server-name-that-outlook-clients-connect-to.html

You should add an internal autodiscover record and an external one as well

http://www.techieshelp.com/create-autodiscover-record/

the external one should be autodiscover.yourdomainname.com

Although you might already have them, does this new server have a different IP address to the old one, it may just be as simple as changing the IP address associated with autodiscover in DNS.

In Exchange powershell run this command

get-ClientAccessServer | fl *uri*

Also verify if you have an autodiscover entry in your dns

http://www.techieshelp.com/create-autodiscover-record/

[PS] C:\Windows\system32>get-ClientAccessServer | fl *uri*

Result
AutoDiscoverServiceInternalUri : https://ourserver.ourdomain.com/Autodiscover/Autodiscover.xml

Since yesterday I have applied a new certificate and restarted the server. I confirm we have the autodiscover entry in DNS.

My next step is to do a repair on one client, we have already tried this, but will have another go. Only about 20% of clients having this error.

Does it work if you connect Outlook via RCP over HTTP offsite,? If it does you may be able to use that as a work around.

On any of the clients in question have you removed the outlook profile and then add a new one?

Yes we have done that. I'm thinking of getting the guy who did the Exchange migration back in to sort it. Thanks for the help so far.

Thanks everyone for trying to help!

This was the problem