We are consolidating servers at clients place whre we are also standardizing the environment by reducing the users access to “Editor” Level. Facing many problems with OOO. Ca anybody share the process of “Configuring the Out of Office agent to run for Editor level users”.
Kindly share the code to configure “Allow user activation” and “Run on Behalf of” for Editor level users for all users in the server. (Code should cycle thru all mail databases).
Subject: Out Of Office Agent for Editor Level Users
In a fresh install, it works right out of the box without any further configuration. Could it be, that you have made customizations in the past?
Subject: Out Of Office Agent for Editor Level Users
During this consolidation,We are just moving mail files to another server. After moving to new server we are reducing the access level to “Editor”. Facing many issues with OOO.
I have seen Julie’s article about doing it programatically. Is there anyway to run through all mai databases and set the things. (llow user activation and run behalf fileds)
Julie’s Article :
Allowing editor-level users to run LotusScript and Java agents :
To enable and run LotusScript and Java agents prior to Notes/Domino 6, you needed at least Designer access and the right to run LotusScript and Java agents. This was because enabling the agent consists of two parts: first, signing the agent, and second, making it eligible to run on a schedule. Because signing the agent requires changing its design, you needed Designer access to do this. So for example, users needed at least Designer access to their mail files (and the right to run LotusScript agents) to run the Out of Office agent, which is written in LotusScript.
Many of our customers requested the ability to give users Editor access to their mail databases, and yet still be able to run the Out of Office agent. To accommodate this, we separated the two parts of enabling the agent by allowing the agent to become eligible to run without resigning it. We also needed a way to run the agent on behalf of the editor-level user who is not privileged to change the agent (or possibly does not have rights to run LotusScript or Java agents). We now provide this functionality, through the Allow user activation checkbox in the Agents properties box:
When this option is selected, editors can activate (enable) the agent. When it is unselected (which is the default), the agent behaves the same as in previous releases. When users with Editor access activate an agent, all they can change is the status of the agent. Editor-level users do not need rights to run LotusScript or Java agents. (If they are not given the rights to run agents, these users will not be able to run any agents other than ones set up to run by an editor.)
You can configure agents for editor-level users manually or programmatically:
Manually, you must have the right to sign agents to run on behalf of others. Then open Domino Designer, open the Agent properties box, and enter the names of the users into the “Run on Behalf of” field (shown in the preceding screen). Select the Allow user activation checkbox. The agent will be signed by you, and when an editor-level user you specified enables the agent, it will run as scheduled under the authority of that user.
Programmatically, you can use the AdminP request “Set User name and Enable Agent.” This can be initiated by the ConfigureMailAgent method on the new AdminP class, as the following example illustrates:
Dim AdminRequest As Variant
Set AdminRequest = session.CreateAdministrationProcess(“GorkyPark/Moscow”)
UserName = “Ninochka”
AgentActivatable = True
Agent = “DemoAgent”
If Not(agent.IsEnabled) Then
Call AdminRequest.ConfigureMailAgent(UserName, Agent, AgentActivatable, False)
Elseif
Call AdminRequest.ConfigureMailAgent(UserName, Agent, AgentActivatable, True)
The primary reason we added this feature is to allow mail users who have Editor access to enable LotusScript agents. You can find several examples of agents using this feature in the Notes 6 Mail template.
Once you’ve set up the agent to allow user activation, any editor-level user named in the Run on behalf o field can enable/disable the agent. Please note that Domino 5 servers will not recognise that the agent was enabled by an editor using Notes/Domino 6. As a result, an agent can get into a state where Release 5 will treat it as enabled, and Notes/Domino 6 will treat it as disabled (and vice versa).
To keep track of the enabled status, we’ve added icons to the Agents view in Notes/Domino 6. A check with a number 5 next to it indicates the agent is enabled only for Release 5 servers (5.0.7 and earlier). A check with a number 6 represents agents that run on Notes/Domino 6 (also 5.0.8 and later). The plain check identifies agents enabled for both Release 5 and Notes/Domino 6. To summarize:
A check with a 5 means the agent was disabled by an editor-level user in Notes/Domino 6. The agent will be treated as disabled by Domino 6 servers (also 5.0.8 and later), but as enabled on Domino 5 servers running 5.0.7 and earlier.
A check with a 6 means the agent was enabled by an editor-level user in Notes/Domino 6. The agent will be treated as enabled by Domino 6 servers (also 5.0.8 and later), but as disabled on Domino 5 servers running 5.0.7 and earlier.
A check without a number means the agent was not enabled/disabled by an editor-level user and will behave the same in Release 5 and Notes/Domino 6.
Note that starting with Domino 5.0.8, the agent manager can recognize agents turned on by editor level users. These agents are recognized by the agent manager and executed on Domino 5.0.8 and later servers. The 5.0.8 user interface does not accommodate this new feature, however. Therefore Release 5 editor-level users cannot activate agents, nor can Release 5.0.x Designer graphically differentiate the status of agents with “check 5” or “check 6” icons, indicating whether they were enabled by Release 5 or Notes/Domino 6 users.
Other security features
In addition to the preceding functionality, we’ve added a number of other security-related features to agents.