I’ve read many posts having to do with the new and wonderful out of office service. I even read the help. The piece of information I am looking for is about the client. The servers are not clustered and all my servers (except for one that is on Release 7.x) are at 8.5.1. All of the servers have mixed client environment of 8.0.x and 8.5.1. Do clients have to be at 8.5.x before I can choose service instead of agent?Also, I only have one server that is at release 7 (It also hosts Document Manager so I can’t upgrade it). If I understand correctly, assuming I can use service for clients at 8.0, I can set my All Servers config doc to Service and then create a config doc for my Release 7 server and set that to Agent. Is that correct?
Thank you.
Subject: me too!
I’m in a similar situation, mid migration from 6.5 to 8.5.1.
I too would like to know if I can enable the service for those who are on 8.5.1 client and template whilst there are other users on 6.5 client and template. Would the old versions just continue to use the agent?
Subject: Out of Office Clients
I decided to put in a PMR and this was my response. I haven’t had a chance to work on it again yet.
FROM IBM:
There is a nice write up by a colleague of mine, Amy Knox, describing the finer details of the Out Of Office service. You can find that document here: http://www-10.lotus.com/ldd/dominowiki.nsf/dx/01072009040728PMWEBSS8.htm
One thing to point out is that in a mixed environment, clustered or not, it might work. We have seen the TaskType field in the 8.x mail template being overwritten from the service back to the agent when there was a non 8.x server contained within the configuration document.
I would suggest that you test first to see if the service will enable or not by enabling the service in you configuration document. If that doesn’t work, then it just confirms what we have seen. I can then ask our mail routing team if copying the configuration document will be ok so you don’t lose any field values.