Hope this helps someone as I spend way too much time onfiguring this one out. I had to install the DC Reader first, with the custom MSTfile and edits to the Setup.ini and then move the Uninstall command after and Igot the result I wanted. ![]() So a user will have Adobe Acrobat Reader DC 19.012.20034 for example. So, the end results was order ofoperation. 1603 is a generic MSI error that says little more than something went wrong. It worked on a test machine where I didn't have anything butBB installed, but if my script uninstalled Acrobat XI first, then installed DC2 nd, that same thing would happen. I thenadded the OWNERSHIP_STATE=0 command to my MSI /x command line: (see below) For whatever reason,when you run the MSI /x command to remove a previous version of Adobe, it tooresets the default PDF viewer (in this case with only BlueBeam left on the machine,it changed it to Chrome? Why?). ![]() This seemed to work fine initially but then it stopped workingonce I added the uninstall command back for removing Acrobat XI. I then just needed to run the setup.exe with out anyswitches and all the custom setting from the MST and Setup.ini files whereapplied as expect. ![]() I used the Customize Wizard to create the MST file for thesettings that the GUI allows you to modify (such as disable AutoUpdates, etc).I then edited the setup.ini file to include the silent switches and the Transformfile and OWNERSHIP_STATE=0 command: (see below)ĬmdLine=TRANSFORMS=AcroRead.mst OWNERSHIP_STATE=0 However, we have several machines that use a third-partyapplication (BlueBeam 2016) that we do not want to over write the ownership forand allow it to install Reader DC but keep BlueBeam as the default PDF viewer. Update: After some trial and error I did figure out how todeploy Acrobat DC v17 and NOT make it the default PDF viewer.īackground – We have several systems that have Acrobat X1Stn installed that are not being used and to reduce the number of license weneed to maintain, we want to deploy Reader DC to replace it and uninstallAcrobat XI.
0 Comments
Leave a Reply. |