So we cannot use the MSI Product Code for detection, but rather we needed something that does bot EXE and MSI. Adobe Flash Player 21.0.0.213 NPAPI not detecte. 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. Case in point, Flash Player.Įxpanding on this, most programs MSI Product Code changes when a new version is installed, like Flash Player. This IS a bit over kill for Reader DC since it uses MSI/MSP relationships properly, but most programs don't. 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. I do the second option because it is applicable to MORE programs. 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. ![]() 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. 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. 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). IF you have Reader DC deployed as Required, this will trigger SCCM to try and install again, since it is no longer detected. 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. Shavlik/Software Update in SCCM updates the computer without any issue, which changes the Version/DisplayVersion. ![]() The issue I found was if I have not yet updated the Reader DC Application, but we released Shavlik updates for Reader DC. We use Shavlik also (not sure if I mentioned before and didn't read back through to check). Dues to the configuration of the Setup.ini it will run silently, apply for transform and apply the patch. The install command line is now nothing but "Setup.exe" with no switches whatsoever. ![]() ![]() Then go edit the deployment type to change the install command line. This way it gets the MSI Product code to use for uninstall and detection method. Now all you do is import the AcroRead.msi into SCCM update the version information to be 15.016.20039. The other command line ("/sAll /rs") makes the "Setup.exe" run silently. This adds your MST Transform file "Reader.mst" to the command line of the MSI as well as the patch. Then edit the "Setup.ini" that comes with it. The easier way is to download the entire Enterprise deployment and extract to a folder. Patch has to be a full path, can't be relative if I remember correctly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |