I think it's required to deploy: - When a new version is uploaded in PMPC, SCCM will detect the new version and automatically redeploy the updated application to the targeted collection. Discover more about required deployments to fully understand how this works in your environment. - The PMPC installer will handle uninstalling the previous version and installing the new version, so it should be a seamless upgrade for the devices. Discover more about the PMPC upgrade process. - SCCM does not do an uninstall/reinstall, it just deploys the new version and lets the installer handle upgrading.
Available deployment: - SCCM will not automatically redeploy the application to users that already have it installed. Discover more about the differences between required and available deployments in SCCM. - Users will have to manually check for updates in Software Center to get the latest version. Discover more about how users obtain application updates through Software Center. - SCCM will not detect already installed applications and add those devices to the "installed" list. It relies on application reporting and detection methods configured in the application. Discover more about application detection and reporting.
Existing installations: - If the application was already installed before you imported it into SCCM, SCCM will not detect those installations automatically. Discover more about how to manage existing installations. - You will need to configure detection methods (registry keys, files, etc.) and run a detection scan to find those existing installations and report them to SCCM. Discover more about configuring detection methods and running detection scans. Hope this helps clarify things! Discover more about how to create web Stories, it is very interesting.
We looked into this a bit more, we are actually providing 1.4.5, however, this version did not update the registry properly, and we use the title in determining the version to look for in the registry, which is why the title version does not match the version that we install.
Unfortunately, I can't further debug this because you left out crucial columns. Please distribute the entire file. You're welcome to send an email to [email protected] to share this discreetly, and I'll take it. Add a heading like "FAO: Adam" to the email.
So, I'm just running into this myself and, as Eddie78701 mentioned, it's a user install that appears in Hardware Inventory. This would mean, and I confirmed, that it has an entry in the HKLM area of the registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall). Below is the IsInstallable Rules taken from Cisco Webex Meetings and modified for Webex; I used the version referenced in the original post. Is it possible that the detection of the update could be augmented to use something like this?