PowerShell Universal

For managed Windows deployments of PowerShell Universal, the official MSI is service-oriented: the vendor documentation says it creates the PowerShell Universal Windows service and listens on http://localhost:5000 by default. Important MSI public properties include INSTALLFOLDER, TCPPORT, REPOFOLDER, CONNECTIONSTRING, DATABASETYPE, STARTSERVICE, SERVICEACCOUNT, SERVICEACCOUNTPASSWORD, TELEMETRY, ADDPSMODULEPATH, and INSTALLTYPE.

A quiet install can pass those properties to msiexec.exe /i PowerShellUniversal.msi /q /norestart. Decide up front whether the package should be a server install or user-context install, whether the service should start immediately with STARTSERVICE=1, and whether the repository/database paths should stay at the defaults under ProgramData or point to a managed SQL/PostgreSQL back end.

If you do not want the MSI-created service, the official hosting documentation also shows a manual service pattern using New-Service -Name "PowerShellUniversal" -BinaryPathName "Universal.Server.exe --service". Treat sizing as a server workload: the vendor’s recommended baseline for a modest production instance is 4 CPU, 16 GB RAM, 500 GB storage, and an MS SQL or PostgreSQL database rather than the small SQLite trial baseline.

Sources: PowerShell Universal installation documentation, hosting documentation, and system requirements.