Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, February 12, 2018 10:33 PM
I am deploying Adobe Reader DC 2018 via SCCM but cannot make the PDF file association to be Reader over Edge.
Adobe has a procedure "https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/pdfviewer.html#solution-2-gpo-policy" and I have tried this and created the XML file (see below) and deployed via GPO as per the procedure but Edge still is the default (post gpoupdate /force , relog on etc etc)
<?xml version="1.0" encoding="UTF-8"?>
<DefaultAssociations>
<Association Identifier=".pdf" ProgId="AcroExch.Document.DC" ApplicationName="Adobe Acrobat Reader DC" />
</DefaultAssociations>
The strange thing is the file assoc on my Windows 10 v1703 (Corp image don't say just update to 1709) is pointing to Reader:
H:\assoc .pdf
.pdf=AcroExch.Document.DC
But if I go into the file association GUI this points to EDGE and I can manually change this and it works but I have 1800 PC's to do this on.
Any directions? I have tried naming the xml file to a txt file as per a forum I read but still not working. This is such a simple thing but SO frustrating !!!!!
Liam
All replies (4)
Tuesday, February 13, 2018 7:17 AM | 1 vote
Several items should be changed, please export the xml files after configure the default PDF reader as Adobe, and then do things in this guide to force association configuration:
http://eddiejackson.net/wp/?p=15400
Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, February 23, 2018 7:38 AM
I must say that I have this on Windows 10 build 1709 since applying KB4058258. Interesting enough the DISM syntax also has changed, see also this post. And when I change the PDF association through the Windows 10 settings app, it does not change when I export the file associations - it remains pointed to Edge.
Friday, February 23, 2018 5:09 PM
I used the steps in the Adobe procedure (solution 2) for Acrobat DC and it is working like it is supposed to. The only difference is the xml file that was created during the export command has a few more lines that change the file association with other Acrobat file types. This is what my xml file looks like but it is for Acrobat DC and not Reader DC. Hope this helps with your situation.
<?xml version="1.0" encoding="UTF-8"?>
<DefaultAssociations>
<Association Identifier=".pdf" ProgID="Acrobat.Document.DC" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".pdfxml" ProgID="Acrobat.pdfxml" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".acrobatsecuritysettings" ProgID="Acrobat.acrobatsecuritysettings" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".fdf" ProgID="Acrobat.FDFDoc" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".xfdf" ProgID="Acrobat.XFDFDoc" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".xdp" ProgID="Acrobat.XDPDoc" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".pdx" ProgID="PDXFileType" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".api" ProgID="Acrobat.Plugin" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".secstore" ProgID="Acrobat.SecStore" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".sequ" ProgID="Acrobat.Sequence" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".rmf" ProgID="Acrobat.RMFFile" ApplicationName="Adobe Acrobat DC" />
<Association Identifier=".bpdx" ProgID="AcrobatBPDXFileType" ApplicationName="Adobe Acrobat DC" />
</DefaultAssociations>
Tuesday, September 3, 2019 12:15 AM
Just what I was looking for thankyou
Dism /Online /Export-DefaultAppAssociations:c:\defaultassociations.xml