ScriptRunner Action Pack for Windows System Management

Author: | Reading time: 2 minutes | Category: Action Pack

ScriptRunner Action Packs

This article has been translated automatically.

Many routine tasks from daily IT operations can be automated, delegated and greatly simplified using PowerShell scripts and ScriptRunner. To avoid each administrator writing their own scripts to Standard Use Cases, we provide our Action Packs. So you can concentrate on your individual use cases during the script development and use the standard use cases from our script collections.

List of our Action Packs:

  • Active Directory
  • Exchange
  • Hyper-V
  • Office365
  • Windows File Management
  • Windows Print Management
  • Windows System Management
  • VMware
  • Citrix

More information about our Action Packs can be found on our website.

New – the Action Pack for Windows System Management

The new Windows System Management Action Pack contains a total of 140 scripts for managing system settings for Windows 10 clients and Windows servers. The majority of the scripts can be used for both systems. Special scripts for Windows 10 Clients as well as for Windows Server can be found in separate subfolders.

General for both systems:

  • BitLocker
  • Defender
  • EventLogs
  • firewall
  • local account
  • network
  • processes
  • remote desktop
  • reporting
  • Scheduled Tasks
  • services
  • system
  • Query (query scripts)

Windows 10 Clients:

  • Windows 10 Apps
  • Computer Restore

Windows Server:

  • Windows Server Backup

So the Action Pack scripts are integrated into ScriptRunner

To use the scripts in ScriptRunner, there are alternative ways of integration:

  1. You download the script collection from ourGitHub repository as a ZIP file and copy the scripts you want to use into the working directory of ScriptRunner.
  2. You connect ScriptRunner to our GitHub repository and set up a synchronization. This can be done directly in the working directory of ScriptRunner or in a separate directory.

Two examples of use cases from the new Action Pack

After the scripts from the Action Packs have been synchronized, they can be used to create actions. Two examples will show how fast the scripts are ready for use.

Use-Case: Bitlocker Backup KeyProtector (Script: Backup-SysMBitLockerKeyProtector)

The use case:

The Backup-SysMBitLockerKeyProtector script stores the recovery password protection for a volume protected by BitLocker Drive Encryption in Active Directory Domain Services (AD DS). To be able to select the parameters dynamically via the dropdown menu, corresponding query scripts can be used for the drive selection and the Key Protector Object. The computer selection can be done via an AD query.

In the full case, the user selects the computer and drive, the Protector Object is determined with the query script, and the recovery password protection is stored in the AD when the script is executed.

That’s how it works:

Create a new action (+New) and select the “Backup-SysMBitLockerKeyProtector” script. Then select your target system and the corresponding credentials. The own machine can be used as a target, since the script can access other computers remotely.

Create Backup Bitlocker Action

Executing the Action

If the action is started via the admin app, the variables drive, ProtectorID and target system can now be selected.

Use Backup Bitlocker Action

Use case: Activating/deactivating firewall rules by the service desk

Use case:

If you regularly receive support requests regarding problems with the local Windows firewall, you can allow the service desk direct access to the firewall settings via the ScriptRunner Delegate App. An integrated query script can also be used to provide the service desk with a set of firewall rules to be changed via a drop-down menu.

That’s how it works:

In this case, the query must first be created using query script, and after the action has been created, it must be released to the service desk by delegation.

Create the query script:

Under “+New –> Querie –> With a Script” select the Querie script “QUY_Get-SysMFirewallRules.ps1” from the Action Pack and confirm the settings as shown in screenshot 3.

Create Firewall Query Script

Create the action:

Now create a new action with the script “Set-SysMFirewallRuleStatus”. Activate the newly created query script for the RuleName parameter via the binocular symbol. If the settings are selected as shown in the following screenshot, the rule can be selected from the drop-down menu when the action is executed and whether it should be activated or deactivated.

Create Firewall Rules

Release for the Service Desk:

Use the +New field to create a new delegation and select the action you just created. In the “Delegate this Action to…” window, select the Service Desk account.

Delegate FirewallSetting Action

After the entries have been confirmed, the Service Desk can execute the action with the selected parameters via the Delegate App.

Use DelegateFirewall Action

You still have questions about ScriptRunner and/or the Action Packs? We will be glad to help you.

You might also be interested in these posts:

Secure Password Server, PowerShell
ScriptRunner 2019R1, Network, Multi-Team
ScriptRunner Version 2018R3