Scope This article applies to PowerShell Universal environments earlier than 4.3.0 that are configured with multiple PSU servers using a SQL database. Problem The PowerShell Universal server may fail to start due to SQL timeout errors. Background ...
Scope This article applies to PowerShell Universal environments running version 4.3.0 or earlier and configured to use SQL persistence for job history. Problem An error will be generated by the SQL driver when attempting to interact with the Job ...
Scope This article provides details on how to import scripts for users that have existing PowerShell scripts they would like to surface in PowerShell Universal. Problem The scripts.ps1 metadata file is required to display scripts within PowerShell ...
Affected Versions - PowerShell Universal 4.2.0 - 4.2.4 Problem When viewing a script's jobs within the script's page, scheduled scripts will not be shown. Root Cause A change was introduced to allow for filtering out scheduled jobs. The script's page ...
Applicability This article applies to users running PowerShell Universal 3.x and 4.x who are attempting to run scripts are alternate users. The issue presents itself as an error while attempting to run scripts that states: Error running script. A ...
Applicability This article applies to users running PowerShell Universal 3.7.12 or later in IIS and attempting to start jobs are alternate user accounts. Root Cause PowerShell Universal 3.7.12 sets the environment variables for the Run As user ...
Update Please see the documentation at https://docs.powershelluniversal.com/config/hosting/high-availability for in-depth details on this topic. Below is an overview statement from Adam Driscoll on this topic as well. Adam's statement Our high ...
If you registered with Ironman Software before December 2020, you will need to create a new account with the same email address. If you are using the lost password functionality and not receiving an email, try creating a new account.
Update January 24th, 2023 Adam recently summarized the Developer's license per below: The only real limitation on the developer license is that it cannot be accessed remotely. The server is only available on loopback when using the dev license. If ...
Purpose The purpose of this article is to provide clear ordered steps for users of PowerShell Universal and to submit them to Ironman Software (typically for a support case). Background Having logs from PowerShell Universal is typically needed to ...
Purpose The purpose of this article is to outline an issue and workaround that is present in version 4.0.6 and 3.9.12 and earlier of PowerShell Universal. Issue When PowerShell Universal has git sync enabled in manual edit mode, it's possible to ...