Hello,
Regarding the new Out of Office Service; What happens with the users already out of office when i change from the OoO Agent to the OoO Service? Will they automatically be updated or will they need to update it themselves? - Do I need to run some kind of command to reenable the OOOs?
Thanks, Kjeld
Subject: what we did…
We found that users were not able to use the new OOO service until their mail template was upgraded. Before enabling the service, I did a tell amgr sched and found the users who had OOAgent enabled. We did not upgrade the mail template for those users until they returned from their vacation and disabled their OOAgent. (Yes, the agents and the service CAN run at the same time.)
But, another way to handle it would be to get that same list, and determine the start and end dates for those users. Upgrade all the mail templates, and then simply go into those users mailfiles and re-enabled the OOO on the service. I am not sure if the service will re-send the message to people who already emailed them during that time period, which is why I didn’t do it that way.
Subject: Read over the out of office wiki:
Read over this wiki:http://www-10.lotus.com/ldd/dominowiki.nsf/dx/01072009040728PMWEBSS8.htm
The wiki has a link to:
This explains the setup.
Basically your server, client and templates needs to be 8x, ideally the same 8x version.
There are a couple of issues when upgrading to 8x pertaining to out of office (ooo):
Title: Out Of Office agent enabled when it should not be after upgrade to Notes/Domino 8
Doc #: 1307609
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21307609
The other issue pertains to “first time” ooo “Editor” level users. “First time” is defined as they have a fresh ooo profile document and agent. Sometimes Lotus Support will recommend to delete the ooo profile, ooo agent and refresh design for ooo anomalies. If the “first time” user has their agent enabled during the time of the switch their agent will remain enabled but the client will report disabled. The easy way around the issue is one of the following:
Disable ooo agents prior to the switch
Use the Out of Office dianostic tool to delete the ooo profile, ooo agent and refresh the design: Title: How to use the Out Of Office (OOO) diagnostic tool.
Doc #: 1296389
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21296389