| description |
|---|
In-browser PowerShell terminals. |
{% hint style="info" %} Terminals require a license. {% endhint %}
Terminals are in-browser PowerShell consoles that you can execute arbitrary commands within. Terminals are configured to target an environment that you select and can optionally us Run As credentials to run as other users. The history of terminals is maintained within the PowerShell Universal database. You can reconnect to disconnected terminals as long as they haven't timed out.
{% hint style="info" %}
Terminal configurations are stored in terminals.ps1
{% endhint %}
You can configure a new terminal by navigating to Automation \ Terminals and clicking Create New Terminal. You'll be able to select the environment and credential to run the terminal as.
.png)
To use a terminal, click the Open Terminal button for the terminal you wish to launch. Depending on your configuration, this may start a new PowerShell process based on the environment you selected.
.png)
Once the terminal has launched, you'll be able to issue commands.
.png)
To stop a terminal, you can navigate to the terminal instances tab on the Terminals page. Click the trash can to stop the terminal.
.png)
If you navigate away from PowerShell Universal, the terminal will go idle. You can reconnect to a terminal by clicking the Open Terminal button for the idle terminal instance.
.png)
Terminals will time out automatically after 5 minutes. You can customize the timeout by setting the -IdleTimeout parameter of New-PSUTerminal.
Terminal history can be enabled per terminal configuration.
.png)
When terminal history is enabled, you will be able to view the history of all commands that were executed within the terminal. Click the View Command History button for the instance in question.
.png)
You will be able to review what the command was that ran, when it was ran, who started the terminal and what the output of the command was.
.png)