↧
Re: Devactivate Acrobat XI on 1 of a 2 user License
↧
Customized Acrobat DC Installation for named user licensing
Hello,
I've struggeling at the Acrobat DC installation with a customized package.
We've named user Enterprise licensing.
So I've downloaded the Acrobat package from our portal and customized it as needed.
Problem now is, that when I try to install this package it won't create the required regkeys for named users.
As per Common Deployment Options — Enterprise Administration Guide these keys should exist.
[HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Licensing\UserSpecificLicensing]"Enabled"="1"
[HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Identity\UserSpecificIdentity]"Enabled"="1"
The command I'm using is this one:
msiexec /i "AcroPro.msi" IGNOREVCRT64=1 TRANSFORMS=AcroPro.mst ROAMIDENTITY=1 ROAMLICENSING=1 /qn /L*v C:\Temp\AcroDC.log
Thanks for you help
↧
↧
Install acrobat pro on Appstack
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
↧
Re: Installing Pro DC and DC Reader - Make Reader default Viewer for all users
There are two ways you can address setting the default PDF Handler at install.
- Install order. In your case, install Reader second and it will be the Default PDF Handler.
- Use the Adobe Properties in the Command Line or in the Setup.ini file in your deployment package so that the second install does not take ownership of the PDF file type.
Adobe Properties — Enterprise Administration Guide
| PDF Ownership | 11.0 & later | OWNERSHIP_STATE | New for 11.0. Windows 8.x only. Specifies whether to take ownership of any file type the product recognizes (pdf, fdf, etc.).
Note: This property is deprecated on Windows 10 machines and DISM-GPO configuration methods must be used. |
| PDF Ownership | 10.0 & later | LEAVE_PDFOWNERSHIP | For new installs. YES prevents the new installation from taking over PDF ownership. NO allows the new install to own opening PDFs. May interact with IW_DEFAULT_VERB for some versions. It is often used for silent installs where the user should not be asked to select a default PDF viewer. For example, the following is the behavior of the Acrobat and Reader installers used with this property:
|
| PDF Ownership | 10.0 & later | IW_DEFAULT_VERB | Use this property when you need to change the default viewer for existing installs.
|
↧
Re: Install acrobat pro on Appstack
Deployment via AppStack is an unsupported workflow, but that only means that 3rd party software and deployment method is untested. Hopefully someone in the community might be able to help.
↧
↧
Re: Customized Acrobat DC Installation for named user licensing
Are you deploying via an imaged OS?
↧
Re: default settings Adobe Acrobat DC Reader
Default what? As the default PDF viewer when Acrobat is also installed or something else?
↧
Re: default settings Adobe Acrobat DC Reader
Use the Adobe Properties in the Command Line or in the Setup.ini file in your deployment package so that the second install does not take ownership of the PDF file type.
Adobe Properties — Enterprise Administration Guide
| PDF Ownership | 11.0 & later | OWNERSHIP_STATE | New for 11.0. Windows 8.x only. Specifies whether to take ownership of any file type the product recognizes (pdf, fdf, etc.).
|
| PDF Ownership | 10.0 & later | LEAVE_PDFOWNERSHIP | For new installs. YES prevents the new installation from taking over PDF ownership. NO allows the new install to own opening PDFs. May interact with IW_DEFAULT_VERB for some versions. It is often used for silent installs where the user should not be asked to select a default PDF viewer. For example, the following is the behavior of the Acrobat and Reader installers used with this property:
|
| PDF Ownership | 10.0 & later | IW_DEFAULT_VERB | Use this property when you need to change the default viewer for existing installs.
|
↧
Re: default settings Adobe Acrobat DC Reader
We use in our Company Foxit PDF Reader as default PDF Viewer. many Departments just use Foxit and Adobe. when we install Adobe by SCCM, he set`s himself as default. The Foxit should continue to remain the standard PDF viewer.
↧
↧
Re: Customized Acrobat DC Installation for named user licensing
So far I was testing the installation on a regular client computer OS.
But if everything is prepared I will use imaged OS deplyoment for productive environment.
↧
Re: Acrobat Reader DC and Adobe Acrobat DC Cleaner Tool has stopped working...
This is not really a solution.
We have various versions of Adobe Reader DC in our enterprise and working with the uninstall codes is not an option. There are too many variables for that. The cleaner tool was an excellent solution for this but since Windows 10 1709 it keeps crashing at the end.
And it crashes at every event mentioned here.
↧
Re: default settings Adobe Acrobat DC Reader
The DISM function dosn´t work. The GPO policy also not work.
Can you say me how to set the OWNERSHIP_STATE please.
↧
Re: default settings Adobe Acrobat DC Reader
I make this in this line:
msiexec /i "AcroRead.msi" EULA_ACCEPT=YES, OWNERSHIP_STATE="0" /qn /l* C:\Temp\Install_AcrobatReaderDC.log
↧
↧
Re: default settings Adobe Acrobat DC Reader
That line "should" work, unless you are on Windows 10. Windows 10 requires that the User determine the file type ownership. Installers cannot make that determination. The DISM and GPO Policy "should" work either way as long as your machines exist on a domain.
↧
Re: default settings Adobe Acrobat DC Reader
Yes, we use Windows 10 but bad to know. We have use DISM and GPO and both should. But somehow the GPO does not work for the Acrobat DC Reader.
In our GPO Foxit is set as the default.
↧
Re: Acrobat Reader DC and Adobe Acrobat DC Cleaner Tool has stopped working...
The cleaner tool on LABs is not a replacement for the uninstaller and should not be used that way. If there is some reason you can't use the standard uninstall methodologies, post why and perhaps found issues could be fixed.
↧
Re: default settings Adobe Acrobat DC Reader
Here's the doc on this subject: Setting the Default PDF Viewer — Enterprise Administration Guide
↧
↧
Re: Customized Acrobat DC Installation for named user licensing
Hi EddyH,
When you execute the command line, do you launch the command prompt with admin access?
Since you logging the installation process as per your command line, have you search the log for this key? If not, try searching the log and check if there is any error or message.
-Tariq Dar
↧
Re: default settings Adobe Acrobat DC Reader
Yes, I`m looking at that. But this doesn't work.
↧
PDF Printer redirection in Citrix 7.5 not working
Good morning.
Our health authority recently switched to Adobe Acrobat XI Pro, and one of the apps that our users have been using is now hosted in Xenapp 7.5 (running on Windows Server 2012) and the majority of our clients computers as Windows 7 with a rolling technology refresh that will eventually see all devices replaced with Windows 10 but completion of that is years out and our users can't wait that long. For some unknown reason, the printer that is created with this version of Acrobat does not want to redirect in the users Citrix session when using Xeanapp 7.5. If we host the program in Xenapp 6.5 (Server 2008), the Adobe printer redirects using the Universal Print Driver with ease.
Acrobat is installed on the clients computer and is not delivered via Citrix.
I have read that redirected printers will only be created if the host has a driver that is appropriate for the client's printer.
We've tried installing the Citrix Universal PDF driver with no success, and regressing to Citrix 6.5 is not an option. I've spent two days searching for an answer only to find way too many unanswered questions and no definitive resolution. We've also tried doing a manual install of the printers drivers going through the long list one by one to see what installed, what didn't, and there was never any change when we launched the Citrix 7.5 sessions.
My server and Citrix admins have verified that no GPO's are present on these servers that would prevent PDF printer creation, and third party PDF creators redirect with no issue. If RDP to a Windows 10 virtual machine, the Adobe PDF printer redirects and uses the Remote Desktop Easy Print driver, and if we connect to the Citrix app from the Windows 10 VM the Adobe PDF printer redirects and is usable in the Citrix session.
I'm out of ideas and patience with this and would appreciate some answers from others that might have been able to tackle and fix this issue.
Cheers.
↧