Scripting on CloudBolt Documentation

Disable OpenSSH on Windows servers

Mon, 01 Jan 0001 00:00:00 +0000

Currently, SSH is the only supported connection method in OneFuse. Trying to uninstall OpenSSH while connected using it is problematic. This method uses WinRM to connect to the target server to uninstall OpenSSH.

This article assumes you have a bastion/jump server configured with OpenSSH, and that your Windows templates already have OpenSSH installed. This has only been tested on Windows 2016 and 2019, but may work on other versions of Windows with modification.

Install packages with Chocolatey

Mon, 01 Jan 0001 00:00:00 +0000

This article assumes that your Windows templates already have OpenSSH and Chocolatey installed. If using a bastion/jump server, the article assumes that OpenSSH, Chocolatey and WinRM are configured. This has only been tested on Windows 2016 and 2019, but may work on other versions of Windows with modification.

The code provided in this walkthrough is a sample only. It should be thoroughly reviewed and tested before use in your environment.

Execute PowerShell scripts using a bastion host

Mon, 01 Jan 0001 00:00:00 +0000

This method allows for connection over PowerShell/WinRM to a target server. This is to support execution of scripts on Provisioned nodes that do not have SSH running.

Currently, the Scripting module only supports the use of OpenSSH connection types on Windows servers. This will require WinSSH to the Bastion host from the OneFuse appliance (TCP 22) to copy and execute the desired PowerShell script. Then, utilize WinRM (TCP 5985, 5986) to the Provisioned Node.

Produce output from Scripting policies

Mon, 01 Jan 0001 00:00:00 +0000

A managed object for OneFuse Scripting Policy can include “output” under the section “provisioningDetails” or “deprovisioningDetails”.

Prerequisites

The script being executed must produce valid JSON strings to STDOUT. This output is then captured by the Scripting Module and used to populate the “output” fields.

How it works

Each JSON string written towards STDOUT will result in an escaped JSON string in the array called “output” under “provisioningDetails” or “deprovisioningDetails”. The structure and key/value names of the JSON string depend on your requirement. The Scripting Module requires that the string must be a valid JSON string. This functionality is valid for both BASH scripts and PowerShell scripts.