KB0032 - (Windows) About the difference between the MSI and ZIP installs

KB0032 - (Windows) About the difference between the MSI and ZIP installs

Question

What's the difference between the MSI and ZIP installations of PowerShell Universal for Windows operating systems?

Answer

The MSI install is a self-contained web hosting platform using Microsoft Kestrel[1]. The ZIP installer is intended for integration with Internet Information Services (IIS)[2]. Most customers who already utilize IIS in their environment prefer the ZIP and others prefer the MSI.

References



    • Related Articles

    • 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 ...

    • KB0017 - Windows Auth Checklist

      Purpose The purpose of this article is to list the prerequisite conditions for ensuring that Windows Authentication in PowerShell Universal will function as expected (i.e. seamless logon without authentication pop-ups) Scope The scope of this article ...

    • KB0078 - Service fails to start during PowerShell Universal v5 Upgrade when using SQLite and MSI

      Scope Users that are upgrading from PowerShell Universal v4 to PowerShell Universal v5 using the MSI and SQLite persistence database. Problem The service may not start in a timely manner and cause the MSI process to fail. Root Cause PowerShell ...

    • KB0082 - Why is PSU listening on port 5000 even though it is not configured to?

      Background You have PSU setup using only HTTPS (typically on port 443) by way of the appsettings.json file located in $Env:ProgramData\PowerShellUniversal[1]. Problem The PSU instance is listening on two ports: the default port of 5000 and the port ...

    • KB0066 - Get-WMIObject cmdlet not working

      Scope This article applies to any scenario where the Get-WMIObject cmdlet is expected to be available and functioning within a PowerShell Universal instance. Effectively, this article will only apply to instances that run under the Windows operating ...