Hello,

we're deploying Adobe Reader DC though GPO (MSI form AIP).

Until now updates was disabled, now I want to enable continouus updates.

I set the necessary registry keys to enable it but updates fail stating Error 100600 "updates have been disabled by your system policy".

How ever, this occur even on a manual installation without any mst or other restrictions. Just double clicking the MSI and go through the installation.

Updates are successfull if I install from exe.

Is it possible to do an initial installation through GPO and then continue with automatic updates?

Regards,

Hermann

I am trying to deploy Adobe Reader XI to our Windows 10 computers using SCCM 2016. I am using the following command in my package

"AcroRdrDC1801120035_en_US.exe" EULA_ACCEPT=YES /qn and while the deployment works and installs Reader, the EULA acceptance doesn't. While

it's only a minor inconvenience, we don't want our users to have to accept the agreement, especially if there is a way to automatically accept it. Can someone please

help me? thanks

Hi Everyone,

I've seen threads on here for other people that are having this issue, but can't find anything current so I guess I have to ask. Is the FTP site still active for downloading the Adobe Customization Wizard? Every time I try to get to it I just get the Google Sad Face: I also get similar messages in other browsers.

One post did mention that the site needed to be accessed via an FTP client. That also resulted in a failure. Clonezilla returned the message: "Error: Could not connect to server"

One thing that also does happen is I get asked for a credential login (makes sense, it is FTP after all). However, Adobe doesn't mention needing any credentials on the Customization Wizard documentation. Are there credentials that need to be entered? Or, better yet, does Adobe have a link where this can be directly downloaded?

Thanks all for any help!

Have all day to install Acrobat DC on my Mac with Mojave with a new SSD. All other CC app are working, but not Acrobat. Error 1.

Have uninstalled all CC apps and config files, and reinstalled several times. Even tried direct downloads of Reader and DC, but installation stops at 75%.

Even used CC Cleaner tool twice.

Please help!

Hello,

    I have to hand it to Adobe - I've never come across and application that sells 2 separate versions, with a cost difference of over $100, that they intentionally made it nearly impossible to distinguish between one another.

We use SCCM, and from what I can tell, Adobe Acrobat DC Pro & Standard both have the same GUID, version number, and display name.  How in the world are we supposed to accurately track our licenses?  We use ServiceNow's Software Asset Management module, integrated with SCCM, to manage software licenses.  It can't tell a difference, and even I as a human, and a 10 year IT Pro, can't either.

Can someone please tell me how I am to accurately manage my Acrobat DC software licenses?

Thank you

Hi all,

I want to get your advice about how to manage the following settings.

By default we have implemented through GPO the configuration of Adobe Reader DC that we want to keep on the registry but we are having some issues.

All of them are set to Update and as a REG_DWORD

bEnhancedSecurityInBrowser  HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bEnhancedSecurityInBrowser  HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

bEnhancedSecurityInBrowser  HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bEnhancedSecurityStandalone  HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bEnhancedSecurityStandalone HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

bEnhancedSecurityStandalone HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bProtectedMode HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bProtectedMode HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

bProtectedMode HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

iProtectedView HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

iProtectedView HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

iProtectedView HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

This configuration leaves the Reader with the following configuration

Some users are having issue with this configuration so we have decided to let the users modify the settings.

But other issue appears.

How to reproduce:

Start adobe reader – settings – security (enhanced)  uncheck “Enable Protected Mode at startup”

No problem so far, then force a GPupdate /force – this then activates the settings

Protected View:  “Files from potentially unsafe locations”   and keeps the “Enable Protected mode at startup “ un checked = this setting is a Unsupported configuration (https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/protectedmode.html)

That situation will cause the error below. As soon a pdf file is launched from a potential unsafe location. (= any pdf file from the Internet)

I believe we should ensure that we cannot fall into a unsupported configuration =

When  “Enable Protected Mode at startup” is unchecked – then Protected View:  must be set on Off

This issue will only be experienced when a User is unchecking “Enable Protected Mode at startup” but once this is done and the next GPO Update appears these Users will have an error.

Any advice will be welcome.

Thanks in advance.

Best Regards.

Hi,

I have logged in to Admin Console and went to packager to create an Adobe DC package with Adobe Creative Cloud.

I have downloaded the package and tried to run setup.exe --silent but get an error message that setup doesn't accept arguments.

I have tried to create a package in SCCM from the MSI in the Build folder but when i deploy the package only Adobe Creative Cloud is installed

I also found there is another set of setup.exe and msi under Build\Setup\APRO18.0\Adobe Acrobat so I am not sure which one I should use for creating my SCCM package, the doc says to use the one from the Build folder, but SCCM reports a successful installation while no Acrobat DC is present on my test computer

I need to track which computers have which version for Licensing and update purposes. I use Dell K1000 for tracking and updating. With Acrobat XI, Pro and Standard had different uninstall registry keys so I was able to track them with a simple check for which registry key was on the computer. They would also show up separately in Dell Case stating Pro or Standard. However, With Acrobat DC the uninstall keys are the same and they both only show up as Acrobat DC in Dell K1000. How does Acrobat DC determine which version is installed and how can I duplicate it so I can count used license and install the correct updates?

Using Custom wizard for Acrobat professional DC by enabling remove Reader DC Not working(Reader DC still retains on machine)

REMOVE_PREVIOUS_READER= YES property is added to MST

on top of it , while installing Acrobat Pro DC, even Reader DC is getting upgraded to latest version.

Hello,

We have had a user report an issue where DC is not rendering at all unless using the top menu bar the user select full screen mode. Otherwise no windows will appear, this includes opening it using a PDF, opening it from the applications folder and creating from screenshot.

We have tried updating to the latest version of OSX and reinstalling the Acrobat DC, As we are using Creative Cloud it wont let us predate the version

Thanks

Hi Folks,

I'm trying to deploy Acrobat XI Pro with Group Policy to Windows 7 64 bit desktops on our domain.

It appears the GPO installed it on my test box but Acobat launches a 'Register Your Product' splash screen when it starts.   Have I missed something in the Adobe Customization Wizard XI?   I've entered the serial number and surpressed the EULA option.

Thanks

Rice

I'm trying to customize a deployment of Acrobat 2017 Standard.

Specifically, I'd like to remove all cloud storage functionality (like the Dropbox integration) for DLP purposes.

I see lots of documentation surrounding the customization of DC deployments but no mention of Acrobat 2017 Standard (or Pro).

Could someone point me to the appropriate downloads and documentation?

Targets for this install will be Windows 10 1703.

Ideally the customized installer would be in a format that can be installed silently.

Thanks!

I have been trying to build a new install of Adobe Reader DC (17.012.20095) for deployment to our PC's using the customisation wizard and am experiencing a number of issues.

The first issue is that the customised install continuously throws errors when launched about chrome_elf.dll not existing, a full unaltered install places this file in C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroCEF

I assume something in my customisation removes this from being installed but how do i stop Reader from looking for it?

The only workarounds seem to be building in something to copy the file or by deleting RdrCEF.exe and RdrServicesUpdater.exe from the directory which will both resolve the issue but would i rather Adobe fixed the underlying issue with the installer or customisation tool.

The second issue relates to adding in HKCU entries into the customisation wizard and them not working and ending up in  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\[RegistryHiveName]\Installer\Migrate

This same issue was reported in 2015 but still does not seem to be fixed?

[Acrobat Reader DC] HKCU registry keys are not replicated for each user as for Adobe Reader

I have a couple of subscription licenses for Acrobat Pro DC. Our notes on the computers they were assigned to were misplaced. We think we have a good sense of which computers have them, but is there a way to confirm remotely, i.e., via a Registry Key or .XML file or similar on the computer, without having to connect to the computer and launch the software?

I am trying to deploy Adobe Reader XI to our Windows 10 computers using SCCM 2016. I am using the following command in my package

"AcroRdrDC1801120035_en_US.exe" EULA_ACCEPT=YES /qn and while the deployment works and installs Reader, the EULA acceptance doesn't. While

it's only a minor inconvenience, we don't want our users to have to accept the agreement, especially if there is a way to automatically accept it. Can someone please

help me? thanks

Hi there,

We have installed Acrobat Reader DC v. 2017 2017.012.20093 on WIn2k8 R2 servers. Many users who are connecting the server with remote desktop/Citrix Xenapp get the 103:103 error when launching Acrobat Reader. All the internet is talking about blanking the "Enable Protected Mode at startup" setting in the 'Security (Enhanced)' panel. The fact is that when doing that, it's not possible to launch Acrobat Reader anymore.

The same happens with newest DC version.

Any idea about that?

Many thanks!

Hi all!

We've recently started using Manage Engine as a replacement to WSUS for Windows and 3rd party patches.

One particular patch that we can't install is a critical one for Adobe Reader DC.

We get something along the lines of "Error 1328. Error apply patch to file ****. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your software vendor."

Ok - so it needs to be installed and updated via the same method - Manage Engine.

So, rather than manually uninstall on 700+ PCs, I attempted to utilize Manage Engine to uninstall from just my PC as a test and got:

"The file system does not support atomic changes to the lock type"

Anyone have any ideas?

Thanks!

Hi all,

I want to get your advice about how to manage the following settings.

By default we have implemented through GPO the configuration of Adobe Reader DC that we want to keep on the registry but we are having some issues.

All of them are set to Update and as a REG_DWORD

bEnhancedSecurityInBrowser  HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bEnhancedSecurityInBrowser  HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

bEnhancedSecurityInBrowser  HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bEnhancedSecurityStandalone  HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bEnhancedSecurityStandalone HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

bEnhancedSecurityStandalone HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bProtectedMode HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

bProtectedMode HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

bProtectedMode HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

iProtectedView HKEY_LOCAL_MACHINE SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

iProtectedView HKEY_CURRENT_USER SOFTWARE\Adobe\Acrobat Reader\DC\TrustManager

iProtectedView HKEY_LOCAL_MACHINE SOFTWARE\Wow6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown

This configuration leaves the Reader with the following configuration

Some users are having issue with this configuration so we have decided to let the users modify the settings.

But other issue appears.

How to reproduce:

Start adobe reader – settings – security (enhanced)  uncheck “Enable Protected Mode at startup”

No problem so far, then force a GPupdate /force – this then activates the settings

Protected View:  “Files from potentially unsafe locations”   and keeps the “Enable Protected mode at startup “ un checked = this setting is a Unsupported configuration (https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/protectedmode.html)

That situation will cause the error below. As soon a pdf file is launched from a potential unsafe location. (= any pdf file from the Internet)

I believe we should ensure that we cannot fall into a unsupported configuration =

When  “Enable Protected Mode at startup” is unchecked – then Protected View:  must be set on Off

This issue will only be experienced when a User is unchecking “Enable Protected Mode at startup” but once this is done and the next GPO Update appears these Users will have an error.

Any advice will be welcome.

Thanks in advance.

Best Regards.

Considering the terrible way Adobe is reachable for support, I will try it this way with hopefully some results.

Our users have started getting errors using Adobe Reader X after the installation of Adobe Acrobat DC. They are getting the message “Acrotray.exe has stopped working”.

We have paid licenses so would like to request support on this matter seeing it’s AcroTray.exe, component of DC, that generates the error. I will elaborate our environment.

We have a customer with 50+ users who all log in on four Windows 2008 Standard x64 Terminal Servers. On this server they have multiple application like Office,

Adobe Reader X, and many more.

The customer requested to install Adobe Acrobat DC on all four servers next to the existing Adobe Reader X installation. After the deployment of DC, the users were getting

random Acrotray.exe error messages. Some get it when they log in to Windows on the Terminal Server and others get it when generating PDF.

We can’t reproduce the error using a test account on the same server as the users, this test user is a copy of a normal user.

Here are two examples of the Windows Eventlog: Applications.

Eventlog server 01 (05-mar-2016 18:17:24)

Faulting application name: acrotray.exe, version: 15.6.30060.15959, time stamp: 0x5595fe57

Faulting module name: ntdll.dll, version: 6.1.7601.23338, time stamp: 0x56a1c6e6

Exception code: 0xc0000374

Fault offset: 0x000ce843

Faulting process id: 0xf34

Faulting application start time: 0x01d17702e19a0cfc

Faulting application path: D:\Progs\Adobe Acrobat DC\Acrobat\acrotray.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: 202e502c-e2f6-11e5-9594-005056964fb8

Eventlog server 03 (07-mar-2016 10:11:12)

Faulting application name: AcroTray.exe, version: 15.6.30060.15959, time stamp: 0x5595fe57

Faulting module name: ntdll.dll, version: 6.1.7601.23338, time stamp: 0x56a1c6e6

Exception code: 0xc0000374

Fault offset: 0x000ce843

Faulting process id: 0x40cc

Faulting application start time: 0x01d178514ac5c12e

Faulting application path: D:\Progs\Adobe Acrobat DC\Acrobat\AcroTray.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: 8914298e-e444-11e5-9e85-0050569654e0

Does anyone have any experience in this and maybe can tell how to solve this issue?
Thanks!

Hi, we are working on a virtual desktop. Horizon isntant clone, non-presisten desktops.

We are also deploying applications with Appvolume/Appstack, and i have problems with the installation of Acrobat Pro on an appstack. If i install it straight on my provisioning client, it works well, but when i provision my appstack, it fail. With error: "Error 1603: A fatal error occurred during installation."

I have installed several applications with appstack, and it is working perfect, but with Adobe Acrobat Pro, it doesn't work.

When i had a chat with an Adobe support assistant, he told med that it was supported.

Have some of you guys figured it out and have a apstack that works with Adobe Acrobat Pro?

BR