Out of Office agent is being enabled when it should not be after upgrading to Notes/Domino 8.x

HCL Domino Domino Forum
1

After upgrading to 8.x, you see that several users’ Out of Office agents are being enabled when they should not be. There are 2 known issues that can cause this to occur:

  1. if you use the convert utility to upgrade users mail file, the Out of office agent will be enabled for any Editor level access user that has enabled and disabled the out of office agent while it was on the 8.x server. This is a known issue and is addressed in SPR PALT7FGMAD and has been addressed in 8.0.3.

This issue is documented in the following Tech Note link:

http://www-01.ibm.com/support/docview.wss?uid=swg21307609

The work around for this issue is to either disable the agent after the convert runs or to remove the OOO agent from the mail file before the convert runs and have the convert task add the agent back into the mail file. There is an example agent on how to do this in the Technote

  1. if after running at an 8.x server for a while you upgrade to a later version on 8.x. For example, after running at 8.0.1 for a while and then upgrade to 8.0.2. You then might see that some users have the Out of Office agent enabled when they should not. In this case it is when the design task runs for the first time and updating the agent in the mail file and it thinks it needs to enable the Out of Office agent. SPR PALT7JBPEQ has been created for this issue but it has not been addressed yet. The Technote for this issue is currently in the process of being created but the work around for this issue is the same as Technote 1307609 listed above. Specifically, either manually disable the agent after the design task runs, or use the agent in that TN to remove the Out of Office agent from the mail files and then have the design task add them back in.

Both of these issues are caused by new functionality added into 8.0.x to allow the convert and design tasks to leave enabled agents enabled when they run.

2

Subject: Another workaround

Thanks for your contribution, I was getting mad about it, it was like no one ever met this problem.

The workarounds given by IBM are quite painful. But it got me to think about this one:

In my R8 mail template, I changed the OoO agent style from scheduled to hidden, targeting no-one. And being renamed to (OutOfOffice)|OutOfOffice .

I then achieved a successful test with a convert on a mail file with a Check Mark 5 icon on OoO agent (see technote).