Hello everyone
I installed Adobe Acrobat on a Terminal Server. During the installation i choosed the language "German". Now every user has Adobe Acrobat in German.
Now i would check is there a language pack for adobe acrobat 8.0.0 in english so the user can set their own language to use adobe acrobat.
Is that possible or is there another good possibilty?
Thanks a lot for your help
Hi
Its start to be really complicated to install all my software for entreprise.
Last one we purchase is :
Acrobat Professional 2017 17.0 MLP AOO License FC
1) I fully install the software but had to connect at the end for activation ... i can undertsnad that. But is it possible to logoff from my adobe account and still use the software?
I have 1 adobe id, if i logoff, cannot use the software anymore.
Please explain to me how im supose to install/activate it.
Is there any place to contact support for entreprise? I try 2 hour to find on site and im not able to find any info.... just want an email caus im not able to speek fluid in english.
Everythimes i try, it end with chat support and it said that its not available.
Thanks for your time and have a good day
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!
My environment implemented strict UAC policies. This hinders users from Installing updates. Is it possible to centrally manage updates through WSUS. If not, are there tools to manage Adobe Updates centrally?
I am just rolling out Acrobat Pro DC. I had installed it on our 2008R2 Terminal Server but it kept asking users to Sign-in every two days. I spoke with Acrobat Support and we created a Custom installation using the Wizard however this won't install on Terminal Server. I keep getting Error:28000
Is there something new about installing on Terminal Servers?
Attempting to install the application via MSI was quitting immediately when ran silently. I removed the silent flag to see that the installer was complaining about not detecting VC++ 2013 x64 on my machine.
I checked and I have the latest version installed already (12.0.40660). I've attempted to uninstall/reinstall the VC++ 2013 x64 package as well as run the repair portion, but Acrobat still cannot detect it.
Any thoughts?
My company has a new serial number for my product and I need to link it to my Adobe ID - I don't see a place to do this on the website.
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 am getting ready to purchase a 20-user volume license for Adobe Acrobat Pro. Adobe only sells the 2017 version, but we need the XI version because it is one of the versions authorized for installation on DoD computers. Is there a way to download Acrobat XI Pro and use the volume license key I get when I purchase 2017? We will be using the Adobe deployment installation packager as the target computers are all offline.
Thanks.
Jim Norman
I created an installer using the Adobe installer customization tool and our corporate volume license key and tested it. Worked great. I wrapped it into our SCCM offline reimage task sequence and have started reimaging machines. So far 10 have been redone. This morning, 6 of the 10 have the Sign In With Your Adobe ID error and will not continue. The other 4 work fine. When I try to remove and reinstall the package, it says invalid license key. I know that isn't true because other machines still function properly. Any suggestions?
Acrobat DC TLP license has been rejected.
Reinstalling or erasing the registry value will not resolve the problem.
Is there a solution other than formatting?
We recently began using the Adobe Acrobat 11 SCUP catalogs to update existing installations of Adobe Acrobat Pro 11 . These installations were part of a system image that was manually updated to the version of Adobe Acrobat Pro that was current at the time which was 11.0.20.
It's been reported that several systems that previously had been Adobe Acrobat Pro 11.0.20 had received an 'upgrade', but were now being reported as having Acrobat 11.0.02. I've confirmed that this is the reported version seen in the SCCM audit and by direct query of one of the systems. However when I check file version on the system, the version of the Acrobat.exe file is 11.0.20.17. The install date on the systems with this issue was on 11/24 if that helps any.
It appears that there may have been an issue with the version detection. Do you have any information about this? I've pulled the updates until we can figure out what happened. We are using the Adobe Acrobat 11 Updates Catalog for SCUP available here: http://armmf.adobe.com/arm-manifests/win/SCUP/Acrobat11_Catalog.cab. Probably more important at this point, how do we fix this since it appears that we have mixed versions?
Thanks.
Where can I fid the files for Pro and STD 2018 Serial number install for new computers?
Hi,
We are unable to add Users as there is no '+' button to add them. I am logged in with full systemadmin access.
Any ideas? This is very frustrating.
Thanks
Hello all,
Via the Adobe Creative Cloud Packager version 1.13.0 build 59 I don't manage to build a working MSI file for Adobe Acrobat. For all the other packages like Photoshop I've no problems at all.
I've made a package with my admin account and so with my user account. Added the MSI in SCCM like always. Mostly it shows up in the Software Center as Installed but it isn't on my client.
Could someone helps me out?
Good day.
Do I need separate installs for Pro vs. Standard? I thought I could use one package and the license allocation identified via the web page would govern which version a user receives. I logged in on machine as someone with Standard and activated that way. I think rebooted and logged in with a different account which is licensed for Pro - I'm still getting Standard.
Am I way off-base?
Thanks
Karen
I am having issues with Adobe Reader DC compatibility for Windows 10 1607.
On newly imaged clients Reader crashes after ~30 seconds.
I think that this has to do with Microsoft Updates for Windows 10 pushed in the past couple of months.
It doesn't matter if the install files are pushed via SCCM or downloaded from Adobe Website.
Once the Reader is installed the only way to keep it from crashing is to turn off bProtecedMode DWORD Value or delete it out of Registry.
I can not do that due to STIGs.
This is a GPO that is pushed to all of the machines and is tattooed in registry due to security measures on our network.
Is there a fix for this issue without disabling Protected Mode?
Also, I have found that enabling the compatibility mode for the USER to Windows 7 fixes the issue, but enabling the compatibility mode for ALL USERS toWindows 7 doesn't fix the issue. I did this via GUI and Command Line.
Command Script that I used for Current User (WORKS)
REG ADD "HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "C:\Program Files (x86)\Adobe\Acrobat Reader DC\ Reader\AcroRd32.exe" /t REG_SZ /d "~ WIN7RTM" /f
Command Script that I used for Local Machine (DOESN'T WORK)
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe" /t REG_SZ /d "~ WIN7RTM" /f
Is there a reason why I'm experiencing this behavior?
Why does the Reader still crash when compatibility is enabled for all users, but works fine if it's enabled for current user? (Yes, I have sufficient admin privileges.)
The latest problem I am having is pushing this script via SCCM or GPO. The registry just will not take it.
It works just fine when I run the script or a .reg file from the desktop.
When it is pushed as a package via SCCM it shows installed in Software Center, but isn't showing up at all in the registry.
Same goes for a GPO. It will show up in gpresult, but it doesn't show up in registry.
Has anyone else encountered this issue?
Message was edited by: Izzy Mammadbayov
How can one enable protected view in Acrobat DC 2015 when Internet Explorer is running in Enhanced protected mode?
On a brand new Windows 7 install, followed with the installation of Adobe Acrobat DC 2015.006.30355, setting Protected View to All Files, and checking the box for Enable Enhanced Security, Protected View works in the browser as shown in the below screen shot.
However, after turning on Internet Explorer's Enhanced Protected Mode, protected view does not activate in the browser as shown in the below screen shot.
Please advise how this can be corrected for. Can anyone explain why this is happening?
I am just rolling out Acrobat Pro DC. I had installed it on our 2008R2 Terminal Server but it kept asking users to Sign-in every two days. I spoke with Acrobat Support and we created a Custom installation using the Wizard however this won't install on Terminal Server. I keep getting Error:28000
Is there something new about installing on Terminal Servers?