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
I'm trying to create a deployment via SCCM of the latest version of Adobe Acrobat Reader DC for our organization, and I'm having some difficulty getting it to work properly. Here are the steps I've taken:
I'd really appreciate any help or advice.
Hello all experts,
Here are the steps that I've done. Please let me know where I did wrong
I downloaded from the adobe ftp a reader AcroRdrDC1800920044_en_US.exe and extract it to get the MSI file using a run command as:
AcroRdrDC1800920044_en_US.exe -nos_o"%homepath%\desktop\ReaderDC"
after the extract, I get a folder including the MSI file and a AcroRdrDCUpd1800920044.msp file.
I slipstreamed that msp file using: msiexec /qb /a acroread.msi /p AcroRdrDCUpd1800920044.msp
Then do the Adobe DC customization to get the transform mst file
Finally I rand msiexec /I Acroread.msi transforms="Acroread.mst"
and I get the error 1334. the file 'natives_blob.bin' cannot be installed because the file cannot be found in the cabinet file.
Can I anyone help?
Thank you very much in advance.
Best!
I am looking to use MS Intune or possibly Solarwinds for deployment. Has anyone been able to do this?
Many thanks,
Allan
Are there separate Classic 2015 and 2017 versions of DC Pro like there are for Reader DC?
I'm trying to find and download the installation files for the Acrobat DC Pro 2017, but I can only find Acrobat Pro 2017, which I assume is the Continuous track that auto updates..
Many users don't have admin rights to install updates, so I don't know if the automatic updating in Pro 2017 will work for them. If not, we need to disable updating and deploy the updates out via SCCM instead.
I use the customization wizard to create a acrobat 2017 package for rolling out on desktop machines. where do i place the last patch in the wizard for example its right now "Acrobat2017Upd1701130113.msp"?
I added it in the setup.ini but it will not be installed after the rollout.
This is my setup.ini actually:
[Startup]
RequireOS=Windows 7
RequireMSI=3.1
RequireIE=7.0.0000.0
Require64BitVCRT=1
CmdLine=/sall /rs /smur
[Product]
msi=AcroPro.msi
vcrtMsi=vc_runtimeMinimum_x64.msi
vcrtDir=VCRT_x64
vcrtCommandLine=VSEXTUI=1
Languages=1033;1036;1031
1033=English (United States)
1036=French (France)
1031=German (Germany)
PATCH=Acrobat2017Upd1701130113.msp;;
CmdLine=TRANSFORMS="AcroPro.mst"
[Windows 7]
PlatformID=2
MajorVersion=6
MinorVersion=1
[MSI Updater]
Path=WindowsInstaller-KB893803-v2-x86.exe
I am attempting to restore the integration between adobe and SharePoint 2013 for check in / out. I followed this post here [Sharepoint 2013 PDF check out and open option ] and installed the PDFFIX.js
I now receive and error while opening files.
I inspected the traffic with Fiddler 4
I see a 404 on /80/_vti_bin/Webs.asmx. The issue is that address doesn't exist. The forward slash '/' should be a collon ':' because it's port http://[mysite]:80/_vti_bin/Webs.asmx
When I use an AutoResponder rule in fiddler to find / replace --- SUCCESS!
This is as far as I got. I'm going to dig in further but maybe someone has some more information before I waste even more time.
We are using a stand alone version of Adobe DC Pro (15.006.30033.2205) (no other Adobe products). Windows 7 32-bit environment. I have used the Adobe customization tool to create a custom install package. I now need to update this package with the latest patch from Adobe to correct a recent security patch.
Ideally I'd like to make a new customized installer package as this allows us to disable the Adobe Sign-In feature, which our agency will never use.
I am trying to use: msiexec /i acropro.msi PATCH="Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst"
The .mst file was created by the customization tool. However, when I run this command, I get the error:
"This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package."
I have attempted uninstall and reboot and cleaning the registry of previous installation of Adobe DC Pro without any luck.
Can someone provide guidance on how to create a new customized install with the latest patch and still have the Adobe Sign-In option disabled?
Hello
Along with our Adobe Suites we have Adobe Reader DC and the ADOBE PDF Printer installed on a Terminal Server (Win2016).
The Catbuilder application requires "EVERYONE" to have permissions on that Adobe PDF Printer - set to "Manage Documents".
However, under the permissions Tab of the printer properties (I am logged on as Enterprise Admin) everything is greyed out - Impossible to change and permissions.
According to a blog I read, this may be due to Adobe installing in "PROTECTED MODE", but whatever the reason, I need to be able to set the required permissions.
I could not find any GPO which would help either.
PLEASE HELP.
I am testing new package deployments of Adobe Reader DC prior to releasing it.
I have used the customization tool for Adobe Reader DC to create a MST file so its a tailored install. The only thing it seems is, I can not alter or remove is the "add account" for Microsoft Share-Point.
At this time our organization does not have Share-Point and possibly not anytime soon.
How can I remove/disable that option? I would rather not spend the administrative overhead on training end user to ignore that it exists.
Jon
Hi,
We have Adobe Acrobat DC deployed to all of our users. We need to load the trusted root certificates from an Adobe Server. Clicking "Update Now" works, which is great because we get the certificates and our issue is resolved. However, we need to do this for all users.
To try and achieve this, I made 2 changes:
Computer\HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\DC\Security\cDigSig\cAdobeDownload - bAskBeforeInstalling
Changed from 1 to 0
Computer\HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\DC\Security\cDigSig\cAdobeDownload - bLoadSettingsFromURL
Changed from 0 to 1
The effect of these 2 Registry changes was to tick the box for "Load trusted root certificates from an Adobe server" and to untick the box for "Ask before updating". These settings are found in Adobe Reader under Edit > Preferences > Trust Manager.
These changes do not result in the certificates being downloaded though; but only seem to set the tick boxes as desired. So I'm wondering, how do we effectively click the "Update Now" for all users? Is there a Registry change that we can do for this as well?
Currently, we have just 1 Certificate under Edit > Preferences > Signatures > More (under Identities & Trusted Certificates). We get many, many more after clicking "Update Now".
Thanks to anyone who can offer any help/advice.
Fredrik
Good afternoon,
First post on Adobe forums and I couldn't find an answer to this anywhere.
We have Adobe Reader DC deployed to all of our users. We need to load the trusted root certificates from an Adobe Server. Clicking "Update Now" works, which is great because we get the certificates and our issue is resolved. However, we need to do this for all users.
To try and achieve this, I made 2 changes:
Computer\HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\DC\Security\cDigSig\cAdobeDownload - bAskBeforeInstalling
Changed from 1 to 0
Computer\HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\DC\Security\cDigSig\cAdobeDownload - bLoadSettingsFromURL
Changed from 0 to 1
The effect of these 2 Registry changes was to tick the box for "Load trusted root certificates from an Adobe server" and to untick the box for "Ask before updating". These settings are found in Adobe Reader under Edit > Preferences > Trust Manager.
These changes do not result in the certificates being downloaded though; but only seem to set the tick boxes as desired. So I'm wondering, how do we effectively click the "Update Now" for all users? Is there a Registry change that we can do for this as well?
Currently, we have just 1 Certificate under Edit > Preferences > Signatures > More (under Identities & Trusted Certificates). We get many, many more after clicking "Update Now".
Thanks to anyone who can offer any help/advice.
Chris
Hallo
nach erfolgter Installation erscheint immer ein Fenster "Anmeldung erforderlich", wie kann man das automatisieren oder per CommandLine-Parameter bei der installation mitgeben, so dass es nicht bei jedem Benutzer erscheint
Wie verteilen Software mit Microsoft SCCM R2
Hello family!
I am having a major issue with our Adobe Acrobat Pro DC! We are unable to sign any documents with our smart card. It does not recognize that there is a smart card plugged in at all. I have tried the trusted certificates, i have attempted to remove security (it's greyed out due to policy). We just got on windows 1709 win10 image and are struggling to get this resolved.
Here is the error:
The Windows Cryptographic Service Provider reported an error:
A device attached to the system is not functioning.
Error Code:31
We have tried several smart card readers, tried changing the certs. Nothing is working. I did notice that the certificate I normally use has a yellow exlamation mark but even when selecting a good certificate and go to sign the document it does not see any cards in the reader.
Thoughts?
Hi does anyone know how I can disable protected mode at startup in Adobe Acrobat Reader DC either using the customization wizard or using the registry? I have found articles for version XI and version 10 but not sure if these will work with DC.
Any help would be greatly appreciated.
Many Thanks
CW
IS there a way I can get .msi for Adobe reader DC, which can be pushed to all users via INTUNE
We would like to update Adobe Reader DC to the latest version via msp files via SCCM. Is there an easy way to deploy the msp updates via SCCM? What is the best practice for these updates deployments? What is the best way to install Adobe reader DC and its updates during OS deployment - software disstribution?
Good Evening,
I'm attempting to extract the latest 19.010.20091 reader DC exe for an SCCM application package. I've verified that if I just install the exe I get the correct 19.010.20091 version, but once I extract the MSI file using 7zip and install I'm getting version 15.007.20033 from that same exe.
Does anyone know what's going on? I really need to get that MSI to install the correct version.
Thank you for any assistance you can provide,
Robert S
For Adobe Reader, all the registry keys which are added with the Adobe Customization Wizard are automatically added to each user. Unfortunately, it is not the same with Adobe Acrobat Reader DC.
They registry keys have to be stored in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\2015\Installer\Migrate to be automatically added in the HKCU of the user at its first launch of the application. But they are stored in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\[RegistryHiveName]\Installer\Migrate, as we can see on the screenshot below:
The problem is probably coming from one of the custom actions. The variable RegistryHiveName is not translated. I didn't make a lot of research, but waiting on a solution from Adobe, I made a PowerShell script which move the registry keys to the correct place:
Move-Item -Path 'HKLM:\SOFTWARE\Adobe\Acrobat Reader\`[RegistryHiveName`]\Installer\Migrate\*' -Destination 'HKLM:\SOFTWARE\Adobe\Acrobat Reader\2015\Installer\Migrate' -force(PowerShell has to be executed in 32 Bits)
If Adobe can correct it in the next version, it would be nice !
I'm trying to create a deployment via SCCM of the latest version of Adobe Acrobat Reader DC for our organization, and I'm having some difficulty getting it to work properly. Here are the steps I've taken:
I'd really appreciate any help or advice.
