Feb
17
17
RES Wisdom: parameters and conditions
One of the questions we get a lot is if we can give an example of a job where we use parameters and conditions. For those of you that are not familiar with the concept:
- a parameter functions as a placeholder for actual information
- a condition determines wheter a task, module or run book should be executed.
In order to make this a bit more clear I would like to work with the following example: an Administrator wants to have one job to set the shell of a user on a workstation to:
- the Windows shell, so not managed with RES PowerFuse
- the PowerFuse shell, so managed with RES PowerFuse
- the Subscriber shell, so a simple menu option to force a user to login centrally or start one or two applications locally
The steps to create a module like this are:
- create a module set shell
- create a module parameter Shell-type, which will be a list parameter in which you deliver the following options
- create a task set shell to set the shell to the Windows shell and make it conditional based on the following options
- create a task set shell to set the shell to the PowerFuse shell and make it conditional based on the following options
- create a task set shell to set the shell to the Subscriber shell and make it conditional based similar to the previous two.
This results in the following task view.
When you schedule this module you will be asked to which you want to switch and only this task will be executed. Of course this is just an example in the same manner you can install or uninstall a progam, add or remove someone from a mailing list, etc.
COMMENTS: 0
Leave a Comment
Leave a Reply
CATEGORIES: