Is Acrobat X Pro and Standard compatible with Windows 10? Our enterprise has a large number of licenses and we need to know if we need to budget for an Acrobat upgrade when we move to Windows 10.
↧
Is Acrobat X Pro and Standard compatible with windows 10?
↧
Problems Installing Adobe
Hello,
Just wanted to start off saying that you for reading. Now into my problem.
I am trying to install Adobe Acrobat Reader DC 17.009.20044 with SCCM 2012 R2.
i have tried around 20-30 different scripts to get this to install with no luck. I found an article of how to slipstream the MSP files into the MSI using command line and I am also using an MST.
I have a powershell script that copies the installation files from the share to a target folder on the C:\
I then have powershell run a batch file and that code is down below:
"C:\Source\AdobeAcroCleaner_DC2015.exe" /product=1 /installpath=Default /silent
msiexec.exe /i "C:\Source\AdobeInstallFiles\AcroRead.msi" PATCH="C:\Source\AdobeInstallFiles\AcroRdrDCUpd1700920044.msp" TRANSFORMS="C:\Source\AdobeInstallFiles\AcroRead.mst" /qn
Now when i ran the MSI through the adobe customization wizard it says i must use a setup.ini file so i created a blank one. On the adobe website it says I don't need a .ini for installation using command line and MSI. It specfically says that the .ini is used for .exe which I am not using. This has me very confused and I need some clarification.
Now I tried using my method but it keeps saying this:
(Note the uninstall of the pervious version of adobe works great with the cleaner. The only reason I am using the cleaner is because adobe will not install on top of another version and this seemed to be the only way to remedy that)
This is what my installation files look like. Hopefully everything looks correct.
Here is the setup.ini which the wizard forced me to generate.
(Note: I added in the MSI AND PATCH lines)
What am i doing wrong?
↧
↧
Re: Problems Installing Adobe
First, have you looked at the following KB documents?
Fix Windows errors that occur during Acrobat Reader update
Error 1321 or 1309 when installing Adobe Creative Suite 5.5, CS5, or CS4 on Windows
Second, have you simplified the script to see which lines work and which lines do not work?
For example, your first line of the script is:
"C:\Source\AdobeAcroCleaner_DC2015.exe" /product=1 /installpath=Default /silent
The syntax for the cleaner tool is:
AdbeArCleaner.exe /silent /product=<ProductId> /installpath=<InstallPath> /cleanlevel=<CleanLevel> /scanforothers=<ScanForOthers>
Question: Is this working to remove the product completely when this line is run on it's own? If yes, then continue.
Your second line of the script is:
msiexec.exe /i "C:\Source\AdobeInstallFiles\AcroRead.msi" PATCH="C:\Source\AdobeInstallFiles\AcroRdrDCUpd1700920044.msp" TRANSFORMS="C:\Source\AdobeInstallFiles\AcroRead.mst" /qn
You are referencing the patch file twice and the MST file twice? You shouldn't need to do that but then again you are using the MSI command line rather than the setup.exe command line so this should not make a difference. If you use the MSI command line then the setup.ini is NOT invoked.
Question: Is this working to remove the product completely when this line is run on it's own? If yes, then the only other thing that that I can think of to assist you in troubleshooting the cause of the issue is to create a verbose log for the installation. That would be something like this:
msiexec.exe /i "C:\Source\AdobeInstallFiles\AcroRead.msi" PATCH="C:\Source\AdobeInstallFiles\AcroRdrDCUpd1700920044.msp" TRANSFORMS="C:\Source\AdobeInstallFiles\AcroRead.mst" /L*v "C:\Source\AdobeInstallFiles\AcroReadInstall.log" /qn
I hope this helps
↧
Re: Is Acrobat X Pro and Standard compatible with windows 10?
It's not listed in the System Requirements documentation.
Adobe Acrobat system requirements
In the context of Creative Suite 6 it is listed as NOT supported but no issues found at that time.
Is Adobe Creative Cloud compatible with Windows 10?
"CS6 and Earlier on Windows 10
Windows 10 is not a supported operating system for CS6 and earlier product versions. Limited testing with CS6 revealed no issues. Adobe recommends customers do their own testing on a non-production partition to ensure new OS'es work with their hardware, drivers, and workflows. Current support for CS6 is limited to up and running assistance (installation, deployment, downloading, and licensing) until discontinuation of support on May 31st, 2017. See Adobe Support Policy for full details."
↧
Re: Why can't I activate my perpetual Acrobat Std. and Pro DC licenses without making the user create an Adobe ID?
Regarding the error "Error message: Offline exception grant process failed" there are a couple of possibilities.
- The machine that you are using is not connected to the internet. This is a requirement for getting an Offline Exception.
- The network firewall is blocking access to the licensing server that grants the Offline Exception.
There is endpoint documentation in the ETK for helping to configure firewall exceptions.
↧
↧
Re: Adobe Pro Usage Audit
There is nothing that does that kind of granular reporting in the product at this time that I am aware.
↧
Re: Adobe Reader Updates are disabled, yet users are being prompted for updates
Which bUpdater setting are you talking about? There are two bUpdater settings in the registry for Acrobat/Reader. The first one is for application updates and the second is for service updates.
| ||
| Data type | boolean: DWORD value > REG_DWORD | |
| Default | null | |
| Version # | 9.2 and 8.1.7+ | |
| HKLM Path | HKLM\SOFTWARE\Policies\Adobe\(product name)\(version)\FeatureLockdown | |
| Summary | Disables the Updater and removes associated user interface items. | |
| Details | This setting interacts overrides any bDeclined value.
| |
| GUI mapping | Setting bUpdater to 0 disables the user interface items Preferences > Updater and Help > Check for updates. | |
| ||
| Data type | boolean: DWORD value > REG_DWORD | |
| Default | 1 | |
| Version # | DC | |
| HKLM Path | HKLM\SOFTWARE\Policies\Adobe\(product name)\(version)\FeatureLockdown\cServices | |
| Summary | Disables both updates to the product's web-plugin components as well as all services. | |
| Details | For product versions after 11.x, this new preference replaces the now deprecated HKCU services master switch bEnableAcrobatHS . It disables both updates to the product's web-plugin components as well as all services without exception, including any sign-in screen. The setting is not the same as bUpdater which resides directly under FeatureLockdown and disables product updates. Possible values include:
| |
↧
Cannot get current Acrobat DC patch to deploy as part of silent MSI install
Hello,
In Feb 2017 I was able to successfully build a silent MSI install of Acrobat DC (AcroRdrDC1502320053_en_US) using the Customization Wizard and deploy the app via ManageEngine Desktop Central. My users could access the self server portal and fire up the install - and it would install perfectly - following all my specific customizations.
Now - I want to do the same with the current DC track installer (AcroRdrDC1700920044_en_US)
I expanded the exe archive using the correct command line (per the Enterprise admin guide) and I end up with the 6 key files. I then fire up the Customization Wizard and load up the acroread.MSI file from the new archive I just expanded. Then within the Customization Wizard - I choose Transform->Load Transform to get the settings previously built in Feb 2017. This loads correctly and I save the Package and deploy the files to the specific folder within my DesktopCentral environment
But when a user runs the install from the portal - the end result is not Version 2017.009.20044 - I get the old "unpatched" 2015 version that cam within the archive.
The Setup.ini file looks right - pointing the right patch within and my new transform file that was created:
[Startup]
RequireMSI=3.0
CmdLine=/sall /rs
[Product]
PATCH=AcroRdrDCUpd1700920044.msp
msi=AcroRead.msi
CmdLine=TRANSFORMS="AcroRead.mst"
But - I cannot get this package to actually install the latest patch?
What am I doing wrong here?
Appreciate any insights.
Cheers,
Bruce
↧
Re: Cannot get current Acrobat DC patch to deploy as part of silent MSI install
What is the command line that get's executed by your users when they install?
↧
↧
Re: Problems Installing Adobe
The log file helped me with my installation problem. It looks like some of the files were not copying down. I used robocopy over the copy-item cmdlet from powershell. This helped with bringing down the files the cmdlet was missing. I then used the log to verify what the exact issue was and then changed some syntax on the adobe cleaner tool and edited my setup.ini file. All of this in conjunction fixed my issue and now we have a clean installation of adobe across our 25K client machines.
Thank you for your assistance it was greatly appreciated.
↧
Re: Cannot get current Acrobat DC patch to deploy as part of silent MSI install
Steve,
I will need to see exactly how Desktop Central parses it's config file. There are a number of things going on when I set up a config file - it's not as cut and dry as a single command line that one would assume would be associate with a typical install
That said - my first package worked perfectly using the same method (unpack archive, use customization tool etc) and then create an install config using the files within Desktop Central.
Also - very odd - when I was reading the enterprise documentation on the Customization tool - it clearly stated that the AcroRead.msi file was updated as part of the customization process. If that is true - I would have expected to see the acroread.msi Modified Date to have changed when I view this file in Windows explorer. But even tho I specifically select/load this msi file into the Customization tool, make some changes and click the Save icon - the modified date of that msi remains unchanged. In my case - it has a file date of April 2015 or something similar.
I will report back when Ic an cobble together the actual execution commands that are being used by Desktop Central.
Cheers,
B
↧
Re: Cannot get current Acrobat DC patch to deploy as part of silent MSI install
Bruce,
There reason I ask is two fold.
1. If it's executing just the MSI file then it needs to use the "PATCH" Property in that command line. The MSI commands do NOT execute the modifications in the Setup.ini file.
2. If it's executing the Setup.exe then for some reason the patch file that is in the installation files is not getting run or fails. Then I would recommend running a verbose log command to see where it is failing.
There are two syntaxes that you can use depending on which method you use:
MSI Example
msiexec.exe /i "C:\\<PATH_TO_THE_FILE>\AcroPro.msi" TRANSFORMS="C:\\<PATH_TO_THE_FILE>\AcroPro.mst" PATCH="C:\\<PATH_TO_THE_FILE>\AcroRdrDCUpd1700920044.msp" /L*v "C:\\<PATH_TO_THE_FILE>\AcroProInstall.log"
Setup Example
Setup.exe /l /sAll
↧
Re: Cannot get current Acrobat DC patch to deploy as part of silent MSI install
Steve,
Much thanks for the update. I have attached a screen cap of what the install package looks like with Desktop Central:
Nothing is really exposed as far as what DesktopCentral is doing. But I am betting I need something within that MSI properties field. Note that MST file is already accounted for. So it may be as easy as adding this:
PATCH="\\SRV-DS01\SoftwareRepository\AdobeReaderDC\AcroRdrDCUpd1700920044.msp" /L*v
into that Properties field?
Again - when I built this package the first time - I do not recall ever putting anything into this field. Let me know what you think
Cheers!
B
↧
↧
Re: Cannot get current Acrobat DC patch to deploy as part of silent MSI install
You need to add the line with the correct path below to the "MSI Properties for installation:" field.
PATCH="C:\\<PATH_TO_THE_FILE>\AcroRdrDCUpd1700920044.msp"
↧
After updating Acrobat DC to latest release, prompted to sign in.
I have created a customization install disabling the prompt to sign in... Everything was fine until the last update release 15.006.30280. After installing that the Sign In Required prompt pops up. The only way I have found to get rid of that is to uninstall all of acrobat and reinstall it. I install the updates again, including 15.006.30280 and it works fine with no Sign In prompt. I don't really want to do it on 60 computers. Anyone experienced this? Is there an easier fix? Thanks.
↧
Re: After updating Acrobat DC to latest release, prompted to sign in.
↧
Re: Adobe Reader Updates are disabled, yet users are being prompted for updates
I would of provided a screen shot, unfortunately the user in question is not providing one and tbh I'm not convinced it is Reader demanding an update, in lack of evidence I am trying to investigate all possibilities, thanks for your reply anyways
↧
↧
Re: Adobe Reader Updates are disabled, yet users are being prompted for updates
Hi, it is the application update, I believe I am getting incorrect info from the user, I will mark this as the correct answer, thanks
↧
Re: Cannot get current Acrobat DC patch to deploy as part of silent MSI install
Steve,
Worked perfectly. Thanks for the help!
Cheers!
Bruce
↧
When will my users be able to download Acrobat straight from the Acrobat invitation
I send invitations to my users that require Acrobat Pro for their job responsibilities and lately I have gotten a "Currently unavailable" error after they setup their Adobe account and are ready to start the download. 
This is highly inconvenient when I have off-site users being sent invites and getting this error. The only way to start downloading Acrobat Pro after they finish creating their account is to go back to the Adobe home page and click Desktop downloads and then search through ALL of the apps to finally find Acrobat to get it downloaded. This has been happening for 3 weeks now and the first week I figured this issue would be resolved.
Instead of invite and forget, they have to put in a ticket, then once I am finished with my previous tickets I can finally send them the instructions to get to the correct webpage for the download. This is turning a 5 minute process into 30+ minutes depending on the ticket queue.
When will this be fixed? If not fixed, when will this be resolved to a more intuitive design for my users to accept the invite, create their account, and start downloading immediately after.
If you don't notice it, I have tested this in Chrome, FF, and IE to be sure it was not just a glitch in the Chrome browser.
↧