Out of office message is not working. Auto Reply is not working

Arif Khan
Arif Khan used Ask the Experts™
on
We have migrated our exchange from exchange 2007 to Exchange 2013 then exchange 2013 to exchange 2016.
Now everything seems working fine except out of office. We set auto reply but it is not working. When any user send emails, auto reply does not go to him. No notification of OOF

Product-Exchange 2016
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Satish AutiSenior System Administrator

Commented:
What is the outlook version you are using?
Arif KhanSystem Administrator

Author

Commented:
Outlook 2010. But this, I dont this is limited to outlook . Because we can set OOF message from OWA also, nothing is working
Satish AutiSenior System Administrator

Commented:
Are you able to configure new outlook profile for affected user?
Try doing that, so will come to know auto discover is working properly or not?
Know it's also not working in OWA as well but still give a try.

If auto discover is working fine but still issue persists, then try restart MSExchangeAutodiscoverAppPool

Restart-WebAppPool MSExchangeAutodiscoverAppPool
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Arif KhanSystem Administrator

Author

Commented:
Did not help this, kindly suggest any other step
Satish AutiSenior System Administrator

Commented:
Please see if auto reply and OOF settings are configured in exchange 2016 from Exchange Admin Center because in exchange 2007/2010 hub transport use to set auto replies and OOF settings for entire org. Now hub transport is no more role of exchange 2016.

You must check the rules and correct them.

https://www.codetwo.com/admins-blog/how-to-block-sending-out-of-office-messages-on-exchange-server-for-external-recipients/
Satish AutiSenior System Administrator

Commented:
To check the settings. (Default is * domain) use power shell.

Get-RemoteDomain Default | fl AllowedOOFType, AutoReplyEnabled, AutoForwardEnabled

If it's not enabled run the below command to enabled it.

Set-RemoteDomain Default -AutoReplyEnabled $true –AutoForwardEnabled $true –AllowedOOFType $ExternalLegacy
Arif KhanSystem Administrator

Author

Commented:
HI Satish,

Thanks for your reply. I checked, it is already enabled but still no auto reply

C:\Windows\system32>Get-RemoteDomain Default | fl AllowedOOFType, AutoReplyEnabled, AutoForwardEnabled


AllowedOOFType     : External
AutoReplyEnabled   : True
AutoForwardEnabled : True
Satish AutiSenior System Administrator

Commented:
Ok, Can you please verify the auto discover settings?


1. Test E-mail Autoconfiguration and see which OOF URL it's pointing.

2. Remove the anonymous authentication and set to integrated and basic authentication for EWS directory in IIS on Exchange.

3. Stop and restart IIS.

https://technet.microsoft.com/en-us/library/aa996324.aspx

Finally you can try to reset the AutodiscoverVirtualDirectory.

Remove-AutodiscoverVirtualDirectory

New-AutodiscoverVirtualDirectory

 

Hope it helps!
Arif KhanSystem Administrator

Author

Commented:
Should I reset both Default and Backend virtual directory of AutoDiscover?
Satish AutiSenior System Administrator

Commented:
From the client side do the Test E-mail autoconfiguration and check where it is pointing. Reset that one.

auto.JPG
Arif KhanSystem Administrator

Author

Commented:
Satish AutiSenior System Administrator

Commented:
Reset that one and see the results.
Arif KhanSystem Administrator

Author

Commented:
Hi Satish,

Thanks for your message. I have reset the Auto Discover virtual directory using ECP, it is successful. But still Auto reply is not working. After resetting AutoDiscover, now getting issue of "Mail tips could not be retrieved. However, it is not creating any mail flow problem. So, I will work first of OOF and then on this new error. Assist me pls
Any other step please?
Satish AutiSenior System Administrator

Commented:
Can you try to recreate the OOF once? Also let me know is the users are still using old profiles or after migration you have configured new ones.
As I read somewhere we need to recreate the outlook profiles after migration to exchange 2016.
Arif KhanSystem Administrator

Author

Commented:
I reset the Auto reply message. I am setting Auto reply from OWA not from outlook. It did not help me.
Satish AutiSenior System Administrator

Commented:
Could please run below command one more time?

Set-RemoteDomain Default -AutoReplyEnabled $true –AutoForwardEnabled $true –AllowedOOFType $ExternalLegacy

Set-RemoteDomain –AllowedOOFType $ExternalLegacy - Enables OOF for Outlook 2003 and previous (for Exchange 2007 and 2010 support)
Satish AutiSenior System Administrator

Commented:
Arif KhanSystem Administrator

Author

Commented:
Ok. I am checking.

Yes, we are mail flow go through Logix filter
Arif KhanSystem Administrator

Author

Commented:
I have checked but no luck
Satish AutiSenior System Administrator

Commented:
What it working while migration from exchange 2007 to Exchange 2013?
Arif KhanSystem Administrator

Author

Commented:
Actually I migrated only and tested everything except OOF. Now client is saying that it was not working since migration time. I am not sure.

Here I tried to check the OOF on outlook 2010, it is giving error that " Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.
Satish AutiSenior System Administrator

Commented:
Satish AutiSenior System Administrator

Commented:
I guess this is very similar with your issue.

https://www.petenetlive.com/KB/Article/0000897
Arif KhanSystem Administrator

Author

Commented:
After going through this article. Error "Mail tips not enable" is resolved. And, Able to set the Auto reply. But it is not working. I set auto reply and sent test mail. Not getting any auto reply
Satish AutiSenior System Administrator

Commented:
Try to restart exchange services and then test again.
Arif KhanSystem Administrator

Author

Commented:
Done. But still I am very wretched. bad luck.
Satish AutiSenior System Administrator

Commented:
It's not so long now.. we are reached very near to resolve it now but something simple we are missing..

Can you give a try to reset the IIS again?
Arif KhanSystem Administrator

Author

Commented:
Yes, I did it Bro, no luck.
System Administrator
Commented:
Hi Satish,

I am really very much thankful to you for your all efforts which you made to assist me towards fixing this problem.

Finally, I got solution. I removed Deny permission of ExchangeLegacyInterop from ADSIEDIT-->Default Receive connector
Satish AutiSenior System Administrator

Commented:
This is something new I learn. Can you share the link where you found this solution.
Arif KhanSystem Administrator

Author

Commented:
Hi Satish,

we did RnD and it worked :D. Well, your really great and helpful.
Arif KhanSystem Administrator

Author

Commented:
This fixed the problem

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial