Hi, I’m trying to do a zero-config MSI deployment to upgrade an existing install to a newer version. The log detects the MSI and checks for the product code, finds that the product code w/ an older version exists, but then decides the app is already installed and exits w/o running the install. Is this normal? I would think a feature like this would be designed to recognize a newer version of an app w/ the same product code and upgrade?
Here’s the relevant section of the install log:
|[Initialization] :: Discovered Zero-Config MSI installation file [C:\Windows\ccmcache\1lu\Files\Teams_windows_x64.msi].|PSAppDeployToolkit|10/9/2024 3:32:36 PM|11124 (0x2B74)|
|---|---|---|---|
|[Installation] :: Reading data from Windows Installer database file [C:\Windows\ccmcache\1lu\Files\Teams_windows_x64.msi] in table [Property].|Get-MsiTableProperty|10/9/2024 3:32:37 PM|11124 (0x2B74)|
|[Installation] :: Getting information for installed Product Code [{731F6BAA-A986-45A4-8936-7C3AAAAA760B}]...|Get-InstalledApplication|10/9/2024 3:32:37 PM|11124 (0x2B74)|
|[Installation] :: Found installed application [Teams Machine-Wide Installer] version [1.4.0.4167] matching product code [{731F6BAA-A986-45A4-8936-7C3AAAAA760B}].|Get-InstalledApplication|10/9/2024 3:32:39 PM|11124 (0x2B74)|
|[Installation] :: Skipped 101 entries while searching, because they were considered Microsoft updates.|Get-InstalledApplication|10/9/2024 3:32:39 PM|11124 (0x2B74)|
|[Installation] :: The MSI is already installed on this system. Skipping action [Install]...|Execute-MSI|10/9/2024 3:32:39 PM|11124 (0x2B74)|
|[Post-Installation] :: Bypassing Close-InstallationProgress [Mode: NonInteractive]|Close-InstallationProgress|10/9/2024 3:32:39 PM|11124 (0x2B74)|
|[Post-Installation] :: MicrosoftCorporation_TeamsMachine-WideInstaller_1.6.0.1381_EN_01 Installation completed with exit code [0].|Exit-Script|10/9/2024 3:32:39 PM|11124 (0x2B74)|