Hello Daniel, thank you very much for the help. At the end of this post I'll elaborate why I want to be able to upgrade locally an GPO deployed MSI.
Yes this is possible from "Program and Features" applet of Control Panel. However, if the product was deployed with the assign method of GPO deployment, then its GPO deployment will be triggered again on every time the machine starts.
What I have observed is that if I install the MSI with GPO (assign to computer), reboot, and manually remove it from the control panel, there is a key in the registry:
Code: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\4013E8F4BBC5D4248B6B68ABD17CD35E
That contains information about the "ProductName", "PackageCode", etc. (this registry key is removed if I remove the MSI directly from the GPO editor).
Rebooting the machine does not install the software again. The culprit seems to be that key, because looking at the log in C:\Windows\TEMP\MSI*.log I can see an error message code 2753 about a file not being marked for installation.
The same error can be observed if I try to manually run
msiexec.exe /x package.msi /L*V uninstall.log
For some reason, I see that uninstalling the package triggers an installation, because in the log I see some lines above this error, that there is an action started configured only in the AIP for installation.
Yes I think this should be possible if the old and new version of your product have the same installation type. A per-user installation type cannot upgrade a per-machine installation type and vice versa. However, this is not a recommended practice at all. If a product was installed by a GPO, then the product upgrade should still be done by the GPO or at least the GPO should uninstall the installed product before proceeding to the manual installation of the new product version.
Both the AIP "Installation Type" and the GPO assignation mode are set to "the machine". Manually upgrading the package seems to work.
The application I'm packaging using Advanced Installer is one that can update itself. In essence, there will be another MSI (created with Advanced Installer) with a newer version downloaded, and the application will try to run it using msiexec, as the local system user (the application happens to have a daemon running as a service). Under normal circumstances, this seems to work (at least in our tests), but the problem arises when, for some reason, the local admin in the machine has uninstalled the application. From that point on, there is no automatic way to recover, because both the GPO installation fails (as commented above), and a manual installation of the MSI fails as well.
And there is where I'm stuck. Many thanks in advance (at least for reading this whole bunch). I'll update the thread as I test further with GPO, and trying to update when no user is logged on.
FOLLOW US
Get the latest news in Application Packaging