Hi Adobe
I have recently deployed Acrobat Reader DC to my company and we have Protected View set to All files by default however, the end user is able to modify that setting. I have been exploring the possibility of controlling this setting by a registry key via Group Policy which is easy enough. But I haven't been able to find anything that defines what "Files from protentially unsafe locations".
Are you able to provide me with what a potentiall unsafe location is please?
As the title suggests, I'm curious to know if Privileged Locations configured via the Acrobat Customization Wizard DC supports environment variables.
For example, will it work correctly/as expected if one uses pathing such as, but not limited to:
Many thanks in advance.
I am currently building a custom package for Adobe Reader 2017 (classic track), using the Adobe Acrobat Customization Wizard DC (2015).
My goal is to have protected mode enabled for all files, except those I designate. In this case, I want the logged in user's desktop and documents to show up as trusted, as well as an file that is launched from within our fileserver. Sounds pretty simple right?
Here are the settings:
After doing some digging, it seems that the system variables are not support, so question 1 is how can I allow only those two folders within the user's profile to be listed as trusted, while not having their downloads folder or any temp cache folder being included? I have 5000 or so users, all with unique user names, so manually setting them is not feasible
Once I installed the application, I went to security settings, and this is what was listed:
It was originally blank, so I added the local user's documents folder. However, none of the hosts or trusted folders were listed. Based on this, I assumed that the settings that were set in the custom wizard were not applied, so I went to the registry to see what it said, with this results, taken from the HKLM registry hive:
and
So it looks like the settings applied properly, however the application isn't applying them or even listing them as trusted sites within the app. Is this a bug in Adobe Reader 2017, and if so, how does it get fixed?
I did look and the locally created settings, and they were saved in the HKCU section:
With the settings manually entered, the settings did apply as appropriate. Documents opened from within that folder were not opened in protected mode, while those that were opened from my file server were opened in protected mode (as were all pdfs that were opened not from the documents folder).
I've looked at Security — Acrobat Customization Wizard DC for Windows and Trust Methods — Acrobat Application Security Guide and based in everything I am reading, I am doing it correctly, yet the settings aren't applying properly; in fact, it doesn't look like the HKLM registry keys are applying at all, which is what the customization wizard uses.
So my second question is, Does anyone know a fix for this? EnterpriseHelp
Hello,
we are trying to install Acrobat Pro via Adobe Customization Wizard on a Terminalserver environment. Installation works fine, however we have some users which use the German language pack, and others using English. I'm trying to achieve Acrobat to ask users, for the first time they start the client, which language they would prefer. Currently it always selects German as default, since this is our system language.
Is there any solution for this via Customization Wizard or registry, to force Acrobat displaying the language selection popup?
I would appreciate any help.
Kind regards,
Morris
I am looking to use MS Intune or possibly Solarwinds for deployment. Has anyone been able to do this?
Many thanks,
Allan
I have looked over this site and have found ways to manually remove the software. Is there a way to silently remove it from a MAC?
Thanks,
NC
Hello everybody.
Where can I disable the chrome extension installation request in Acrobat Customization Wizard DC?
I've been banging my head on this problem for a few days now, and can't seem to find a resolution. I'm moderately familiar with packaging and scripting installs, so there is a possibility my issue lies with my understanding of patching MSI files with MSP's.
I'm trying to create a custom installation of Acrobat Reader DC 2017 using the Acrobat Customization Wizard DC. The downloads I'm starting off with are:
AcroRdrDC1701220093_en_US.exe
Which contains:
abcpy.ini
AcroRdrDCUpd1701220093.msp
AcroRead.msi
Data1.cab
list.txt
setup.exe
setup.ini
CustWiz1502020039_en_US_DC.exe
Step 1: Extract files from AcroRdrDC1701220093_en_US.exe using 7zip to a folder called Reader
Step 2: Install Acrobat Customization Wizard DC
Step 3: Launch ACW, load AcroRead.msi from Reader folder
Step 4: Modify the settings, including a few custom HKLM and HKCU registry keys I got from here:
Step 5: Save transform file as "AcroRead.mst" to the Reader folder
Step 6: From a virtual machine, run the installation files like this:
msiexec -i AcroRead.msi TRANSFORMS=AcroRead.mst /quiet
Step 7: Launch Acrobat Reader DC
What I found was some of the settings in the ACW did not propagate to the installation . Mostly, none of the custom HKCU settings replicated to the user's registry. I found a bug report with Acrobat Reader DC 2015 where the registry keys weren't migrating over properly at launch of Reader
[Acrobat Reader DC] HKCU registry keys are not replicated for each user as for Adobe Reader
Supposedly a fix was released in the 2017 branch of Reader.
What I discovered above is that in step 2, I was creating a transform file using the 2015 version of Acrobat Reader DC, but using the 2017 version of the ACW. This might have been where some of my problems were coming from, so my next goal was to patch the MSI using the AcroRdrDCUpd1701220093.msp, and then re-create the transform file from scratch. This is where I'm getting a little lost.
I read that an 'Administrative Installation' needs to be created, and then patched. So I ran the command msiexec /a acroread.msi /p AcroRdrDCUpd1701220093.msp and then installed to a different folder called "Administrative Installations\Adobe Reader DC". I then ran msiexec -i acroread.msi TRANSFORMS=acroread.mst /quiet from the original READER folder (because the MSI seems to have been updated) and I get all sorts of missing files errors.
All I'm trying to do is configure a transform file from the latest version of Acrobat Reader DC (2017) and then install the package, including the transform, to a virtual workstation for testing. Can someone point out what I'm doing wrong? Tnx.
We are deploying the Acrobat Pro DC VIP (Value Incentive Plan) package using SCCM but after starting Acrobat the user is given the option to 'Sign In Later', which allows them to continue using Acrobat with the 'Free Trial' option.
Is it possible to disable the 'Sign In Later' button, leaving only the 'Sign In' option as we don't want the 'Free Trial' to be available to the end user?
Wir nutzen Acrobat Pro 2017 im Rahmen einer Volumenlizenz. Im Rahmen der Installation wird bei jedem Anwender gleich die eingescannte Unterschrift hinterlegt. Wenn man die Software danach bei einem anderen Anwender installiert, wird automatisch die Unterschrift des vorherigen Anwenders installiert. Wie kann man das verhindern?
My steps are simply:
Using base MSI from Acrobat 2017 Release (Classic Track base release) — Release Notes for Acrobat DC Products I create GPO to deploy the package. This works just fine. But when I want to do an upgrade:
I tried various MSPs with the same result. One curious issue is that patching with the MSP creates additional folders 'Common', 'Program Files', 'System32'. Does the MSP patching actually work at all? Is there a way to just get an updated MSI without the problematic MSP fiddling?
Greetings.
I'm trying in vain to stop adobe showing the eula and welcome screen every time a network user runs the program. I've used profile manager to set manual plist changes (com.adobe.Reader.plist) under the DC branch however nothing I seem to do works. I've even tried running the program,setting it up, copying the created plist, uploading it into profile manager and using those settings, still no joy. Please can anyone help as to where I am going wrong.
Thanks
So here's the huge problem - I want to deploy a patched Adobe X1 via group policy
NOt exactly ground breaking stuff ist it. And yet this complex procedure is fraught with problems.
Firstly I really struggle with Adobe's not simply doling out MSI's for any update. It really complicates things no-end.
Anyway, Here's what I understand the procedure to be.
1 Download the msi, - ftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.00/
2 Msiexec -a it extract it to a folder
3 Download the patch - ftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.22/misc/
4 msiexec -a -p tpatch.msp to patch msi in step 2
5 Run customisation wizard against the patched msi from step 4
6 Copy transform to folder
7 Point GP at a share and deploy using the transform from step 6
Fails on step 4.
The upgrade patch cannot be installed by the windows installer service because the programme to be upgraded may be missing or the upgrade patch may update a different version of the programme. Verify the program to be upgraded exists on your computer and you have the correct upgrade patch
So try another patch
This folder ftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.21/misc/ has 2 msp files.
Redo steps 1- 4 with this AdbeRdrUpd11021_MUI.msp- which failed to patch.
Redo steps 1 - 4 with AdbeRdrUpd11021.msp which seemed to patch ok,
However I fail on step 5 - Setup.ini is missing apparently.
Created an empty ini file and redid steps 1 -5 , but no joy. Still missing an ini file.
Can someone detail the correct procedure to get a usable msi that I can run the customisation wizard against so I can deploy this.
Thank you.
Hello,
We currently use Nitro Pro sitewide in our environment. We are considering switching to Acrobat Pro but before we do so we would like to a couple of users to trial it.
Googling 'acrobat pro trial' takes me to a consumer web page where I get a trial for only 7 days and have to enter credit card details for a subscription for after the trial expires. I don't want this because we would pay for it via a reseller with bulk pricing, single key etc..
How do I get the enterprise equivalent of the trial?
Thanks
Hi all,
I've recently inherited the task of administering Adobe Acrobat 2017 Licenses for my organization. I've been trying to sort through our installs vs purchased licenses count. We use the TLP license type. I've been told that before we transitioned to the Adobe TLP, there were several boxed retail versions of Adobe Acrobat 2017 purchased and installed. My goal is to sort out which copies are using our TLP serial number, to make sure we stay in compliance with the total number purchased.
Is there any way I can look for this information on my network, or get Adobe to check their systems for this information? I really don't want to wait until we hit the limit and get denied an install, or worse go over that limit and be out of compliance with Adobe. I'm not sure what information adobe keep in regards to mapping a serial number to a device, but ideally a way to track which machines the specific key is on is what I'm looking for. Any assistance would be much appreciated.
-Zach
In an enterprise environment we should be able to control the software version that we deploy to our systems. With Adobe Reader everything works fine but this Adobe Acrobat 2017 Pro is a little bit stubborn and decided to update himself even that the Adobe Acrobat Update service is disabled. Can you please provide us a solution to this issue? We want to disable automatic updates for Adobe Acrobat 2017 Pro. Thank you.
I purchased adobe acrobat 2015 or XII and i have been using the same software since years now i am trying to move to another machine but the serial key is not able to validate or activate the software.
Hi,
I was looking here:
Document Cloud Product Tracks — Enterprise Administration Guide
And I was wondering what path we should choose. We would like to lock down patches ie: we don't want it to update automatically, as we'd like to do some testing really. The fact that only the latest update is available doens't matter too much, if it means that we can schedule it as and when we please, and so that we can check the general firmware.
Also, I'd imagine you can just patch over whatever we've got already, instead of re-installing Adobe reader every time, and recustomising it every time?
Thanks
Hi
We operate on a Windows 2012 terminal server environment and although there is potential for approx 80 or so users to be logged on via Remote Desktop, only 8 or so users would actually need to use the software. I'm not really wanting to install software on local machines but no point in licencing for 80. Is there anything you can advise please to solve the problem?
Thanks
I am trying to deploy adobe professional 2017 out to users via SCCM and need to have it not ask for a login upon launching the application. I have used the Acrobat Customization Wizard DC to modify the package and add the serial number in and grant offline exception but it still ask for login. I have tried it with the boxes checked for "allow standalone Acrobat deployment with CCE serial and "Suppress display of EULA with no luck. Any help would be appreciated.