Link to home
Start Free TrialLog in
Avatar of osiexchange
osiexchange

asked on

Out of Office just stopped working

Have a user whose Out of Office just stopped working. User was using Outlook 2007. Upgrading to 2010 did not work. We are on Exchange 2010 SP1, update rollup 3. Creating a profile on a completely different workstation does not help so its not a local issue. Not even sure where to start or how to troubleshoot. I did run a test autoconfiguration by holding down the control key and right clicking the Outlook icon. User is correctlly pointing to the OOF server same as everyone else. Is Out of Office a rule just like local rules you would set. I mean I know how its set in Outlook but is it stored on the server just like a rule?
ASKER CERTIFIED SOLUTION
Avatar of askang2
askang2

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of osiexchange
osiexchange

ASKER

It doesn't function when set. We have verfied that setting in Outlook and OWA. It is defintely set but it just doesn't function as it should.
try opening outllook with the /cleanrules switch.  Make sure to export your current rules before you do this.
Then set OOF and test again.
Already done that. Many times over.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Tried that also. Testing by sending an email from inside. Also, I found this article below and used the tool to look at the settings. This is a real good article on troubleshooting. What is strange in my case is when you set Out of Office, the banner in Outlook 2010 displays at the top indicating that Out of Office is set yet when you use the tool to view the settings, it is set to False.

http://www.msexchange.org/articles_tutorials/exchange-server-2007/tools/troubleshooting-out-of-office.html
sounds like it is a setting in exchange. is the setting that allows out of office for external emails checked.
Try deleting the ost file on the client machine. This resolved the issue for one of our users who upgraded from Outlook 2003 to Outlook 2010.

Failing that are there any other office/outlook installations showing in add/remove programs that might be conflicting?

Also try clearing any email credentials in the "Credential Manager" in Control panel and restart Outlook.


Finally its a long shot but deleting the following key from the registry used fix out-of-office functionality in Outlook 2003, as its 2003 specific its unlikely to be relevant but if the key is present from a previous installation might be wrth deleting (pretty sure newer versions of office do not have that key but worth browsing under the parent keys to check) :

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\outlook\Resiliency
The problem was resolved by moving the users mailbox from 2010 back to 2007. We still have a 2007 server left in the environment since we are in the process of a migration. Nothing I tried resolved the issue while the users mailbox was on 2010.

On that note, we did apply update rollup 3 for Exchange 2010 SP1 about 10 days ago. What I have noticed and is not related to this particular problem, is that anyone that had their Out of Office set when I applied the Update Rollup could not remove their Out of Office setting when they returned after the update was installed. We had to export out their rules, delete the rules, and import the rules back in. Again, this only affected users that had their Out of Office on when the update was applied. I was wondering if anyone else ran into this problem. We are not absolutely 100% positive the rollup caused the issue but nothing else was done to Exchange so it looks pretty suspicious. Also a warning for anyone else that is thinking about deploying this rollup.
Have you moved the mailbox back to Outlook 2010 yet?
Not yet. Was going to leave it on 2007 as long as possible. The user is out for an extended period of time. I am guessing though when I move it back, it will be OK. I am more concerned about about the possible effects of the update rollup.
Moving the user back to 2010 and OOO still works OK.
Can the question be closed/ deleted then as there is no longer an issue?
Partically resolved on my own.
You should of either deleted the question or closed it accepting your comments as the solution