We use Shavlik also (not sure if I mentioned before and didn't read back through to check). Yes, and no. The issue I found was if I have not yet updated the Reader DC Application, but we released Shavlik updates for Reader DC. Shavlik/Software Update in SCCM updates the computer without any issue, which changes the Version/DisplayVersion. Here is where the issue starts. If you have the detection method the way I do with Version is equal to 17.009.20044, then when Shavlik updates the computer the version no longer matches so it is not detected. IF you have Reader DC deployed as Required, this will trigger SCCM to try and install again, since it is no longer detected. In the case of Reader DC (I think Acrobat also) this can be solved by, either setting the detection method to Version is greater than or equal to 17.009.20044 or by adding a Requirement to the Deployment Type that the Version is either "less than or equal to 17.009.20044 or the version doesn't exist at all" (in case of not being installed yet). The greater than or equal to method is valid for these products because the MSI Product Code is not changed as I detailed in previous post. Therefore even if you are several version behind on the Application and Shavlik updated the computer the detection method will still be valid and more importantly the uninstall string is still valid since the MSI Product Code is the same. I personally do NOT like this method because the Application still says the old version number is installed, even though if you check programs and features and the new version is indeed installed. I do the second option because it is applicable to MORE programs. I'll try to explain. By using a detection method with version is equal to coupled with a Requirement, when a newer version is installed by Shavlik, the next time "Application Deployment Evaluation Cycle" runs (we do daily in client settings) the Application is no longer displayed in software center at all since a newer version is installed than the application I have deployed, since the Requirement is no longer met. This IS a bit over kill for Reader DC since it uses MSI/MSP relationships properly, but most programs don't. Case in point, Flash Player. Expanding on this, most programs MSI Product Code changes when a new version is installed, like Flash Player. Flash Player is even more of a PITA, because the EXE install is totally different than the MSI, it is not just a wrapped MSI with and EXE. Adobe Flash Player 21.0.0.213 NPAPI not detecte... |Shavlik User Community. So we cannot use the MSI Product Code for detection, but rather we needed something that does bot EXE and MSI. That answer is: "[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayerPlugin]". So with this example you can see when a new version is installed by Shavlik, even if your detection says it is still installed, the uninstall string will be broken, because the MSI Product Code has changed. So Software Center still says the software is installed, but if you try to uninstall it will not be able to since MSI Product code has changed. In this way the Requirement just no longer displays the deployed version of Flash Player in Software Center to avoid confusion and issues for the user. Hope this all makes sense! I know I went a bit crazy here, but without detail it is even more confusing. My entire argument for my method is debunked though if you don't deploy updates from shavlik until you update the application that is deployed via software center. We just never seem to be ready with Applications when we're doing updates with Windows/Shavlik to our users. 😞
... View more