The only change in the OOO agent is that it is being enabled and disabled by users who have designer access to theire own mail database. There has been no change to the code in the template so therefore, again, I believe the agent should not get reset.
The other funny thing is if I do tests in my dev environment then the agent does NOT get reset and everything is fine. It only seems to happen when our administrator does the replace/refresh in the live environment.
Subject: RE: Out of Office agent disabling AGAIN!!!
Hi,
Thank you for your response. I agree with you. I dislilke modifying the standard template either. But when the company requires it, well, so be it
But going back to your response. I think I should have made myself a bit clearer. The user enables/disables the OOO in the standard template way (they do not enable/disable via designer). So nothing has been touched in the template or the client version except the enabling/disabling.
We found out what the problem was. It was the way the Administrator was signing the agent. Instead of signing just the elements that had been changed he was signing absolutely everything.
As to enabling/disabling, if a user or someone, enables/disables an agent then the refresh process does NOT count this as the element being changed (see link in original post)
