ScriptRunner Web Apps

Actions define the complete policy set for executing and delegating scripts. The detailed display of a policy (as above) also shows the dependencies to the individual components of a policy. The context-sensitive action bar below displays the available setting and display options depending on the selected main menu and selected choice in the list. With one click, you can execute an action immediately for testing or display all reports for the action.

Dynamic queries allow the user to make a selection for a PowerShell parameter. Users, groups, virtual machines, organizational units, printers and much more can be searched and selected in the Browser App. Queries can be cascaded and executed automatically. The results of dynamic queries can be determined from the Active Directory, with query scripts, from lists or files. The associated query wizard (above) simplifies configuration. The test function allows you to test the query immediately.

The settings for the target systems determine the authorization context in which a script may be executed on this system. Depending on the PowerShell mode, different settings for remoting (above) or local processing can be set on the ScriptRunner system. If several target systems are combined in a container, different options for script execution, such as parallel processing, 1 out of n or round robin, can be used.

This is your central repository for all scripts that you want to use in a team with ScriptRunner. You can view the change log of each script, upload new scripts to the ScriptRunner system, or use cmdlets in actions directly. A tag filter controls the display in all main menus. So that you always have an overview.

ScriptRunner follows the “security by design” philosophy. An important feature is the separation of rights for the user and for script execution. While the actions can be started by authorized users, the scripts are executed on the corresponding target systems with separate administrative accounts. A detailed view of the credential policy (above) shows you in which actions and target systems the selected administrative account is used. The integration and use of enterprise password server systems for the administration of administrative accounts is also possible.

The ScriptRunner policies allow the secure delegation of actions to other IT teams, service desks or end users. Delegated actions can be started by the user in the Delegate Web App. You specify the structure and appearance in the Delegate App in the action. With one click you can check and define which actions have been delegated to a specific user or group (above). The assignment is done via Active Directory accounts and groups as well as the integrated role model of ScriptRunner.

Complete automation scenarios, such as for monitoring events, with ITSM, workflows or applications, are made possible with ScriptRunner Automation Connectors. ScriptRunner takes on the role of a central automation platform for PowerShell scripts in such scenarios. No matter how and from which side the order to execute a script arrives: ScriptRunner executes it safely, controlled and monitored by guidelines. This gives you full control and transparency over the use of all PowerShell scripts in your IT infrastructure – central, secure, traceable.

The central concept of ScriptRunner enables you to set up central reporting for PowerShell in the first place. You want to be able to trace at any time when a script was executed and with which parameters and rights. You want to know what the result was, you want to be able to compare reports. Use our integrated reporting functions including differential view, clipboard, sending and downloading reports and much more. If you are also subject to regular audits, you can use our option for long-term storage of all reporting information in an external database.