i have upgrade my domino server 6.5.6 to 8.5.1, convert design of all mail file and now i see some OutOfOffice in agent list.how i can disable, delete or migrate this agents ?
thanks
Subject: OOO Service Info
There are a series of things you need to have in place to ensure that the OOO Agents aren’t used by people and that they use the OOO Service.
Here is a link to the wiki with great detail on the process of implementation and requirements for enabling for users:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/01072009040728PMWEBSS8.htm
You need to be sure that you have the server, mailfile template, and Notes client all at some flavor or R8; and that the service is enabled. If any piece of that isn’t true, then the OOO service won’t be applied to a specific user.
But that is all spelled out in great detail in the wiki.
William
Subject: What about enabled agents?
Mmmh, the wiki says to skip enabled agents from the disable list. That doesn’t make sense!
I can see why they won’t interfere with running agents and kill them while users are away … but not killing them creates a much bigger problem:
Once a user with a running OOA is upgraded he can’t access the preferences for the OOA anymoren (as we have switched to OOS).
Therefore his Agent remains intact and bugs the user with the request to disable him. But the user can’t do this anymnore as he is now presented with the OOS GUI.
Any ideas how to prevent this?
Thanks
Harald
Subject: Agents getting disabled vs. re-enabled during design upgrade
Hi - Note that you can control whether enabled agents stay that way or are disabled by a template upgrade (functionality was added in R8). Default behavior is that the design of the agent will be updated, and then the agent will be re-enabled. This can be changed by using either of the following notes.ini variables:
DESIGN_AGENT_UPDATE = 1
→ will not re-enable the agent; will overwrite if the agent in the template has a newer design than the agent in the database
DESIGN_AGENT_UPDATE = 2
→ will not re-enable the agent; will overwrite even if the agent in the template has the same or older version than the one in the database
Also, in most cases, an enabled OOO agent can be successfully disabled by the user, after the server has changed configs to use the OOO service. While this isn’t flawless, we did a significant amount of work for this scenario (work was done in the R8 mail template), and I’ve just confirmed this with two mailfiles (where owner had Manager access in one, and Editor access in the other): User enables OOO agent; admin changes server from agent to service config, and restarts server; user opens mailfile, brings up OOO UI, and opts to disable OOO… agent is disabled, and when user subsequently enables OOO, the service is correctly enabled).
Subject: forwarded to development
lm/mh