How do I deploy Adobe Reader DC without having it take ownership of the PDF file extension?

I'm trying to deploy Adobe Reader DC on workstations with Acrobat Pro on them. I want Acrobat to stay the default app. I've used Adobe's customization wizard, to no avail. It will utilize parts of the MST but when it comes to ownership, it forces DC. My current script looks like this:
msiexec /i <path>\AcroRdrDC1500920069_en_US\NoDefault\AcroRead.msi TRANSFORMS="<path>\AcroRdrDC1500920069_en_US\NoDefault\NoDefault.mst" LEAVE_PDFOWNERSHIP=YES REBOOT=ReallySuppress /qb

I've been researching and testing for days, I can't figure it out. Any help would be greatly appreciated. 

3 Comments   [ + ] Show comments
  • Have you tried running a repair of Acrobat after DC is installed? That may flip the bit back to Acrobat. Other than that, I'd try exporting the registry key which sets the default app and import it into the MST file. - vjaneczko 8 years ago
  • Hi Did you ever get this working? I am having a similar issue and would like to know if you got it working and if so how you did it? - CBT IT 8 years ago
  • Nope. The users had to manually change their default after the install. - marshal.anson 8 years ago

Answers (3)

Posted by: apptopack 8 years ago
Red Belt

LEAVE_PDFOWNERSHIP=”YES”  property is used to retain the PDF ownership with the existing application. Try using "" for YES in commandline.

You can also add this property inside transforms using ORCA.Add LEAVE_PDFOWNERSHIP with value Yes in property table and delete PDF_INTEGRATION Property.

Posted by: mjrichardson 6 years ago
White Belt

Update: After some trial and error I did figure out how todeploy Acrobat DC v17 and NOT make it the default PDF viewer.

Background – 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. 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.


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)




CmdLine=/sAll /rs







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.


This seemed to work fine initially but then it stopped workingonce I added the uninstall command back for removing Acrobat XI. 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?).  I thenadded the OWNERSHIP_STATE=0 command to my MSI /x command line: (see below)


/X {AC76BA86-1033-FFFF-BA7E-000000000006} /qnOWNERSHIP_STATE=0


It worked on a test machine where I didn't have anything butBB installed, but if my script uninstalled Acrobat XI first, then installed DC2nd, that same thing would happen. So, the end results was order ofoperation.

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.


Hope this helps someone as I spend way too much time onfiguring this one out. 

Posted by: apptopack 8 years ago
Red Belt

For 10.0 version you can use LEAVE_PDFOWNERSHIP property. If the version is 11.0 do not use it. Rather use OWNERSHIP_STATE=0

Link - http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/properties.html

  • Thanks, but that didn't work either. :( - marshal.anson 8 years ago
  • I've used the IW_DEFAULT_VERB, DEFAULT_VERB, OWNERSHIP_STATE, and LEAVE_PDFOWNERSHIP by themselves, all at once and every combination in between. I've tried editing the MSI with the Adobe Customization Wizard and when that didn't work, I used Orca to see if that would help. Nothing. grrrrr - marshal.anson 8 years ago
    • I am having the same issue trying to deploy DC v17. Did you ever identify the fix for this? - mjrichardson 6 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ