KB0073 - Resetting PowerShell Universal configuration data
Scope
The scope of this document is applicable to all PowerShell Universal installations.
Problem
Incorrect configuration causes PowerShell Universal to behave in a manner that prevents the user from fixing the configuration. This can include problems such as:
- Inability to login
- Admin console misbehaving
- Failing to load resources like APIs and scripts
Solution
All PowerShell Universal configuration data, aside from Identities and App Tokens, is stored within the repository directory. By default, this directory is within %ProgramData%\UniversalAutomation\Repository. PowerShell Universal loads these files when started and, if enabled, uses a file system watcher to pick up changes to these files while running. If, for example, authentication or authorization are not working, you can get back to a clean state by editing or deleting the authentication.ps1 and\or roles.ps1. Empty of missing files will cause PowerShell Universal to default back to its original configuration.
Make sure to backup and files you may be modifying directly before doing so.
Related Articles
KB0020 - Firewall Configuration for PowerShell Universal
Purpose The purpose of this document is to provide information about the necessary filewall settings required by PowerShell Universal. Overview PowerShell Universal does not offer a built in firewall. We recommend using standard firewalls available ...
PowerShell Universal Service crashes on startup after an upgrade to 1.4.6
Version: PowerShell Universal 1.4.6 Issue The PowerShell Universal service will crash with the following error in Event Viewer. Application: Universal.Server.exe CoreCLR Version: 4.700.19.56402 .NET Core Version: 3.1.0 Description: The process was ...
KB0069 - PowerShell Universal Startup Process
Purpose The purpose of this document is to outline the steps that PowerShell Universal takes when starting up. Process 1. Insert current product version and install date in database Updates the database with a record about the current product version ...
KB0036 - How to set the license via environment variable
Purpose The purpose of this article is to explain how to set the license for PowerShell Universal by way of environment variable instead of the traditional file-based method. Scope For now, only Windows is in the scope of this article. Linux and ...
KB0074 - Connecting to PSU API w/Windows Auth
Scope This article applies only to PSU environments where Windows Authentication[1] is enabled and known to be working[2]. Problem You are not able to interact with the PSU instance using the Invoke-WebRequest PowerShell cmdlet even though logging in ...