Advanced (Multi-Service)-Target Configuration

Author: | Reading time: 2 minutes | Category: ScriptRunner

Multi-Service-Target in ScriptRunner, Screenshot ScriptRunner, PowerShell Automation

This article has been translated automatically.

Configured actions are typically executed on target systems. However, customer feedback and our own experience have led to a more differentiated view on the use of scripts in larger virtualized environments.

The example of a virtual Exchange server is a good illustration of this.

The following subsystems can be distinguished for the comprehensive management of such a system environment: Hyper-V Host, Virtual Machine, Windows OS, Exchange Server application. In practice, there will be scripts and configured actions for the respective subsystems for which different administrative accounts are required.

At the same time, in large environments, similar activities should take place simultaneously on a number of similar subsystems, e.g. management of Windows Server OS, with the same administrative credential (bulk processes).

In order to meet these multidimensional requirements in ScriptRunner much better, the configuration of a target system was extended by the pre-assignment of administrative credentials and the PowerShell access settings. This means that very differentiated scenarios can now also be depicted for the customer.

Multi-Service-Target für PowerShell

Multi-Service Target for PowerShell

To take the example from above, you can now configure four “virtual” target systems:
– hyperv-host” with the associated administrative account for Hyper-V operations and the tags “Exchange”, “Hyper-V”
– “msx-server-VM” with the associated administrative account for VM operations with the tags “Exchange”, “VM”
– “msx-server-OS” with the associated administrative account for WinS operations with the tags “Exchange”,

– “msx-appl-svc” with the assigned administrative account for WinS operations with the tags “Exchange”, “Server Application”

For all these virtual target systems now the complete access information can be stored in ScriptRunner, even if it is physically the same machine or VM.

These posts might also be interesting for you:

ScriptRunner 2019R1, Network, Multi-Team
ScriptRunner Version 2018R3
Action Packs. ScriptRunner PowerShell Scripts