Any body knows how to script/package Acrobat Reader DC version 2017.009.20044 for Windows 10 ver.1511?
After Reader is installed I would like the pdf file association to default to the Reader instead of Microsoft Edge without having any user interaction.
Any ideas tricks would be greatly appreciated.
Thanks,
Guillaume
Deployed updates are now failing. When will the updated install certificates be available?
Where can I find the Acrobat Customization Wizard DC for version 2017
It's the same as the one for DC/2015. It's here:
Read this entire page of the ETK. It covers both Windows 8.1 and Windows 10 Default PDF Viewer discussion: Setting the Default PDF Viewer — Enterprise Administration Guide
By the way if you search for the special character it's ALT+255. Therefore, you get "Acrobat Reader DC.lnk". The special character is between the words Reader and DC. Now, with the latest msp we get a space (ALT+32) between the same two words. The problem that we all have now is which version will Adobe keep in the following updates?
Are there any other supplied solutions. In our circumstance using GPO’s is not convenient due to our deployment method. SCCM is used to distribute different products of Adobe to different devices depending on the user needs so having different subset of GPO’s pushed to these devices to control file association would not be very convenient and as for using DISM seeing that Acrobat is not incorporated in our base I can’t see it being helpful.
Isn’t there a reg key that could be implemented during the install of a Adobe product that could make the required file association?
Thanks,
Guillaume
But the deployment still fails with this version.
Can you give us a complete tutorial on how to unpack and prepare the AdobeRader? Im just hitting errors here, like saying "Please check if the transformation path´s are valid" and so on.
I cant get any further.
Unfortunately, no. This is a Default File Type Owner setting is one that is enforced by the Windows OS. The User has to choose what application is the default owner of a Filet Type if there are more than one application that can open/own it.
When I sent invite to my NY Teams, they are not receiving the Invite from Adobe its' been blocked.
Thanks,
Jackie
We have deployed adobe acrobat reader AcroRdrDC1500720033_en_US.msi with the AcroRdrDCUpd1500820082.msp. We are now unable to update through sccm scup. The msi cites its missing a non existent msp file or an mst file, and throws error 1603 in sccm scup. If we install interactivly it gives the error 1328. We need some assistance in figuring out how to update the adobe reader DC to the current patch level of 17.x.
We purchased a volume license and installed Acrobat to several workstations. When Acrobat is launched all the users are able to access 'My Account' for the Adobe ID linked to the installation. Anyway to remove access to this?
We ran Acrobat DC in a trial which worked well so we bought licences.
Now we need to install Acrobat DC on our XenApp provisioned image. Where does the prov.xml file need to be located after it's generated by the tool?
I have run adobe_prtk.exe --tool=VolumeSerialize --generate --serial="<ENTER SERIAL #HERE>" --leid="<ENTER LEID #HERE>" --regsuppress=ss --eulasuppress and adobe_prtk.exe --tool=VolumeSerialize --provfile=<ENTER PATH OF PROV.XML FILE> --stream.
Thanks in advance
We have virtual machines environment, where user doesn't have certain computer on which he works. Not all users need Adobe DC PRO, but the number of machines we have in virtual pool is bigger than DC Pro users. So we can't install and activate it on all machines. Is there any ways of install DC Pro in such situation? Maybe we can purchase server license distribution if Adobe have this option?
The path to the prov.xml file can be anywhere you want to put the file. Just be sure that you put that absolute path in the command when you execute it.
Two more questions:
1. Would you happen to know if Adobe offers an ADMX file to control some of their options/settings via GPO?
2. If I understand correctly if using GPO's to control the file association then seeing I have multiple different Adobe products in our environment then I will need to have multiple GPO's targeting different devices depending on what adobe product they have (ex: Adobe Reader, Adobe Acrobat etc...) If so, Adobe will need to find a solution to this inconvenience as this will be a total nightmare to implement and to manage.
Hey,
We've got an issue on a 2008 R2 terminal server where signing documents using Adobe Reader is causing app lockups.
I've found that disabling the "Modern User Interface" (in Preferences > Signatures > Creation & Appearance (More…) ) fixes the issue - however I have been unable to find a way to control this via group policy. I've tried running registry / file monitoring software to find the appropriate key / place to control this from with no luck.
As per this blog post - Digital signatures simplified | Adobe Content Corner - it states this can be controlled via Group Policy.
-----
“From Preferences > Signatures > Creation & Appearance (More…) you can uncheck the “Use modern user interface…” option to turn off the new experience and return to the old one. This preference is active by default and can be controlled by means of Registry (Windows) and Plist (MacOS) preferences, so it is suitable for a custom configuration with automated deployments of Acrobat.”
-----
I have searched through the online guide in the enterprise toolkit (Acrobat Customization Wizard DC for Windows) and have not been able to locate the relevant registry key / setting to disable the “Use modern user interface for signing and Digital ID configuration”.
Would anybody be able to point me in the right direction on how to achieve this via group policy?
Thanks
Leigh