This document contains known issues for Acrobat DC not covered in the Acrobat and Reader documentation. Adobe identified the following issues at the time Acrobat DC was released. Separate help documents or release notes cover issues that arose since the release. If an update fixes an issue, the version number is noted. Acrobat Reader DC installation is a two-part process: The installer is downloaded, and then Reader is installed. How to download roblox on apple computer. Be sure to wait until both parts are complete. A progress bar displays the time remaining. When you see the confirmation message that the installation is complete, click Finish.
- Adobe Acrobat Reader Dc Pro
- Adobe Acrobat Reader Dc Versions
- Adobe Acrobat Reader Free Download
- Adobe Acrobat Pdf Reader Free
- Adobe Acrobat Reader Dc Installer
Acrobat products support post deployment configuration via GPO. The Windows Server Group Policy Objects (GPO) and the Active Directory services infrastructure enables IT to automate one-to-many management of computers. Administrators can implement security settings, enforce IT policies, and distribute software across a range of organizational units. With the software installation extension of GPO, you can provide on-demand software installation and automatic repair of applications.
When you need to further configure applications after deployment, you can use ADM templates to propagate the requisite settings across your organization. The Group Policy settings that you create are contained in a GPO. To create a GPO, use the Group Policy Management Console (GPMC), which is available for download from the Microsoft website at http://www.microsoft.com/downloads/details.aspx?FamilyID=0A6D4C24-8CBD-4B35-9272-DD3CBFC81887&displaylang=en.
Note
The product only supports per MACHINE installs. It does not support per-USER installs.
Tested environments¶
The procedures in this document were tested in the following environments:
Acrobat DC:
Client computers running on OS versions Windows 7, and Windows 8 (32 & 64-bit clients).
Server computers running Windows Server 2012 Enterprise Edition 64-bit.
Using an MST with GPO¶
If you've used the Wizard to create a transform MST file for a custom installation, you apply that MST while installing the application during deployment of the GPO package. At a high level, the steps include:
Create the MST file.
Select the MST via the Modification tab.
Complete the standard GPO package deployment
GPO deployments¶
Create an AIP.
Copy the AIP folder and rename it as the patch version; for example, 10.0.1.
Slipstream the patch into the 10.0 MSI.
Open a command prompt and CD to the patch version copy of the AIP.
Create the AIP via
msiexec/a[MSIfilename]/p[MSPfilename]
Add a new package to the original GPO in the standard way without moving existing packages.
Point to the new MSI.
In the Deploy Software dialog, choose Advanced to bring up the properties menu for the package.
On the Properties page's General tab, rename the package to
name+version>
to distinguish this package. This name will appear in the Add/Remove Programs entry of the client system when the update is installed.
Switch to the Deployment tab.
Optional: If you need to Uninstall this application when it falls out of the scope of management setting, select the Deployment tab and select that checkbox. This will uninstall the application and patch automatically when the scope of the GPO changes or the package is removed from the GPO.
Select the Upgrades tab.
Choose the current package (in this case 10.0).
Choose Add.
In the Add Upgrade Package dialog, do the following:
Select Current GPO.
Select the package you want to upgrade.
Select Package can upgrade over the existing package to ensure that this will be an upgrade instead of uninstall/reinstall.
Choose OK.
Review the summary.
Users under a GPO policy will now get the latest update after the group policy refreshes and a computer restart. This procedure can be repeated for all patches.
Assign the application to a computer:¶
Right-click Group Policy Objects. Diablo 3 free download.
Choose New.
In the New GPO dialog box, enter a descriptive name for the new policy.
Choose OK.
In the left-hand panel, expand Group Policy Objects.
Highlight the new policy name you just created.
On the Scope tab, choose Add in the Security Filtering section.
Choose Object Types in the Select User, Computer, or Group dialog box.
Choose Computers in the Object Types dialog box,
Choose OK.
Check the Enter the object nameto select text check box in the Select User, Computer, or Group dialog box.
Enter the name of the computer to which you want to deploy the software. (To browse available computer names, choose Advanced > Find Now.)
Note
Repeat this step for all computer names to which you want to deploy software. Assigning the install to users is not supported. You cannot use GPO installs with Control Panel installs.
Choose OK to close the Select User, Computer, or Group dialog box.
In the console's left panel, right-click the policy name that you initially created.
Choose Edit.
Expand Computer Configuration in the left panel n the Group Policy dialog box.
Expand Software Settings.
Right-click Software installation.
Choose New > Package.
In the Open dialog box, browse to the AIP you created.
Select the MSI file containing the installer you want to deploy.
Choose Open.
In the Deploy Software dialog box, do one of the following:
If you do not plan to apply transforms, select Assigned > OK.
If you plan to apply transforms during installation, select Advanced > OK.
In the Properties dialog box for the package you created:
Choose the Deployment tab.
Select Uninstall this application when it falls out of the scope of management.
If you plan to deploy in multiple languages, choose Advanced.
In the Advanced Deployment Options dialog box, choose Ignore language when deploying this package.
Choose OK.
On the Modifications tab, specify any modification transforms you want to apply when the package is installed by choosing Add and then opening each transform from its network location.
On the Security tab, verify the name(s) of any computer(s) to which you are assigning software.
Choose OK to close the Properties dialog box.
In the Group Policy dialog box, expand Computer Configuration > Administrative Templates > Windows Components.
In the Windows Components folder, select Windows Installer.
Select Always install with elevated privileges.
Select Properties.
In the Always install with elevated privileges Properties dialog box, choose the Setting tab > Enabled > OK.
Configure logging:
In the Windows Installer panel of the Group Policy dialog box, right-click Logging.
Select Properties.
Choose Enabled on the Setting tab.
Enter
iweaprcv
in the Logging text box.Choose OK.
In the Group Policy dialog box, choose File > Exit.
In the Group Policy Management Console, expand Forests and Domains.
Right-click the Acrobat OU to which you want to link the GPO that you created earlier in this procedure, and then select Link an Existing GPO.
In the Select GPO dialog box > Group Policy objects list > the GPO you created > OK.
The GPO must be propagated to the Active Directory Global Catalog and then to the individual computers. For this reason, allow 5-10 minutes before restarting the computers to which you are assigning the Acrobat software, or plan to restart the client computers twice before the system policies are synchronized.
Removing products via GPO¶
Removing Acrobat products by using GPOs requires unlinking the Active Directory OU from the GPO currently enabling the software to run.
To remove Acrobat products that are assigned to a computer, unlink the GPO from the OU, or remove the computer from the OU and GPO. The software will be removed the next time the computer restarts.
GPO registry template¶
Adobe provides two starter templates for Acrobat and Reader. These templates contain a few of the most important settings, but you can use the Preference Reference to extend them further.
DC Continuous Track
Classic Track 2020
Classic Track 2017
Template preferences fall into these broad categories:
General enterprise settings: Features such as disabling updates and setting the default PDF handler.
Security: Application security features such as enhanced security, sandboxing, and JS controls.
TrustManager: Trusting Windows OS security zones as defined in Internet Explorer.
Digital Signatures: Adobe Acrobat Trust List integration.
Creating GPO Templates¶
You can create GPO templates that will enable configuration of almost any feature as long as you conform to the Microsoft format. For more information, see:
Note
Populate the template fields with information from the Preference Reference.
Populate the template fields with information from the Preference Reference.
GPO template: for Accessibility
This guide describes how to deploy Reader DC via App-V so that the application is delivered on demand but runs as if installed locally. See the online step-by-step example.
For a useful 3rd party blog, see http://www.tmurgent.com/TmBlog/?p=2332.
Unsupported scenarios¶
User-publish
Roaming profiles.
App-V is not tested in Citrix environments.
System requirements¶
Microsoft Application Virtualization Sequencer Version 5.0 SP3.
Acrobat Reader DC MUI (either track)
Products sequenced on a 32-bit machine must be deployed on 32-bit clients and products sequenced on a 64-bit machine must be deployed on 64-bit clients.
Tuning for virtual envs¶
Tune the installer prior to imaging and deployment.
Tuning helps mitigate performance issues, simplifies the end user experience, and allows you to disable features and behaviors that should not be accessible to end users in an IT-managed environment.
Install the latest product.
Disable the updater.
Accept the EULA on behalf of all users by setting the appropriate registry key.
Use SUPPRESSLANGSELECTION on the command line at install time to disable user's ability to change the language.
If the product language should be different than the OS languages, set the language.
Supress registration (there are multiple ways: Wizard, cmd line property, PRTK tool).
Disable push notifications: Set bToggleNotifications to 0.
Disable the Help > Repair Acrobat Installation menu by setting:
32 bit machines:
[HKLMSOFTWAREAdobe(productname)(version)Installer]'Disable_Repair'
64 bit machines:
[HKLMSOFTWAREWow6432NodeAdobe(productname)(version)Installer]'Disable_Repair'
Scrolling performance
If scrolling performance is poor in graphic intensive documents, try the following:
Go to Edit > Preferences > Rendering.
Uncheck Smooth line art and Smooth images. Alternatively, you can set these preferences during pre-deployment configuration:
Distiller performance
In some environments, Distiller performance may suffer if the messages.log file becomes too large after a number of Distiller operations. Delete this file periodically. It is located at
ApplicationDataAdobeAcrobatDistillermessages.log
.Remove unused fonts from the Windows installation.
Folder permissions
Protected Mode will only work when the USERS group has the following permissions on the product installation folder: Read and execute, List folder contents, Read. For a default installation, the path might be C:ProgramFiles(x86)AdobeAcrobatReaderDC
.
Other settings
There are over 500 other registry preferences documented in the Preference Reference . Use the Wizard or manual/scripted methods to customer the product.
Preparing the environment¶
Prepare the sequencing machine per Microsoft's guidelines.
Note
Failure to adhere to the best practices and the following guidelines can cause errors in functionality. You may find it worthwhile to follow the MS example in Microsoft's Sequencing Guide.
Create the following registry DWORD entry with a value of 1 to see the option for selecting PVAD while sequencing:
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftAppVSequencerCompatibility]EnablePVADControl=1
Processes that normally run on your computer can slow down the sequencing process and cause irrelevant data to be gathered during sequencing. Because the Sequencer scans for these and other processes before creating a Virtual Application Package, the following programs should be stopped:
Windows Defender
Antivirus software
Disk Defragmentation Software
Windows Search
Microsoft Update
Any open Windows Explorer session
Creating an App-V Package¶
Create a template¶
Templates allow you to control what files become part of the package, and you should exclude unnecessary files. You may wish to create the template after sequencing as described below.
To create a template, start with the provided template, OR perform the following steps:
Launch the Microsoft App-V Sequencer.
Go to Tools > Options.
Choose the Exclusion Items tab.
Choose New.
Add the following folders to the Exclusion Items List:
[{Profile}]
[{AppData}]
[{LocalAppDataLow}]
Close the Options window.
Choose File > Save As Template…
Choose OK when the dialog appears.
Save the file as an .appvt file.
Exit.
Sequence Acrobat Reader¶
There are two ways to approach sequencing:
Use the Microsoft Sequencer UI, and create a template file after you create the package as described below. This method incorporates all the changes included the exclusion list as well as the configuration in the package editor's advanced tab window.
Create the Reader App-V package with powershell command below. Doing so replaces steps 1-21 but does not incorporate the settings in the last steps.
Manual steps
Start the Microsoft Sequencer.
Choose Go to File > Load Template… and select your saved template (.appvt).
Select Create a new Virtual Application Package > Create Package.
Choose Next.
If there are any warnings on the Prepare Computer screen, correct them.
Choose Next.
On the Type of Application screen, select Standard Application.
Choose Next.
On the Select Installer screen, enter the path to your product installation files (Setup.exe).
Choose Next.
In the Package Name screen, enter an application name (such as Acrobat Reader DC).
In the PVAD screen, enter the Reader installation path. Install to this location only.
During installation, do the following:
Install to the location that has been entered as PVAD in previous step. This can be done by clicking 'Change Destination Folder' Button in the Acrobat Reader DC Installer.
Follow the on-screen instructions and install the application.
Close the Installer to go back to the Sequencer.
After installation completes, select I am finished installing.
Choose Next.
After the Sequencer collects the system changes, review the Installation Report which detects common sequencing issues. Do not run any Application from the Configure Software screen.
Choose Next.
Choose 'Stop Now'
Choose Next.
Select 'Continue to modify package without Saving using the package editor'.
Choose Next.
Adobe Acrobat Reader Dc Pro
In the Package Editor Window, open the Advanced Tab and check the following checkboxes:
Allow COM Objects to interact with Local System.
Allow all named objects to interact with Local System.
Roblox sign up for free. Verify the files and folders excluded above do not appear in the package:
root>VFSProfile
root>VFSLocalAppDataLow
root>VFSAppData
Embed scripts¶
Download and unzip the required scripts.
Go to the Package Files tab in the Editor.
Navigate to Package > Scripts.
Right-Click the Scripts folder and choose Add to embed a new script into the package so that they can be leveraged on the client machine. Available scripts include:
Publish.ps1: A publish time script which suppresses the Reader updater and also appends the necessary registry keys to the App-V client's
PassThroughPaths
for correct functioning.Unpublish.ps1: At unpublish time this script removes the updater key which was created at publish time. The keys added to
PassThroughPaths
registry at the time of publishing are not removed since those keys also impact the functioning of virtual Acrobat if present on the client machine.Runtime.bat: This run-time script creates the parent registry of the pass-through entries in App-V. This script only works for the domain users and will throw error 534 if a local user tries to open the Virtual Reader DC App. Use the above script only when the package is published to the domain users.
Save the package and exit.
Post sequencing steps¶
Adobe Acrobat Reader Dc Versions
The DeploymentConfig.xml
file resides in the same folder as the .appv
file. Modify it as described below.
Create script extension points. It is recommended to publish the package globally. In this case, add the scripts inside the tag. The Publish and Unpublish scripts require arguments as shown below.
Set the COM integration mode
Set named object interaction. Change all tags to false:
Configure to add Runtime.bat so that it is triggered on the creation of the virtual environment for the package.
Deploying a client package¶
Prerequisites¶
Enable Scripting on client machines. The Reader Package contains scripts which are executed on the client machine in order to provide a feature rich experience to the end user. The scripts can be enabled via:
Optional: Enable FeatureLockdown on Clients. To suppress or lock certain features on the client, do one of the following: Overwatch download pc beta.
Manually create the FeatureLockDown keys on the client machine either by pushing policies from the server or by using publish time script for the Reader package.
Add the keys inside the package itself from the package editor window using the Registry tab. This requires removing the
HKEY_LOCAL_MACHINESOFTWAREPolicies
registry entry from the list of pass-through registry keys atHKEY_LOCAL_MACHINESOFTWAREMicrosoftAppVSubsystemVirtualRegistry
on the client machine. Since, the change is machine specific this will impact other virtual applications as well, hence, care must be taken while choosing this step.
Publishing¶
Publish the package globally: Extension points for the Reader App-V Package require machine-level installation. With App-V 5.0 SP2 or later, publishing globally automatically creates these extensions and Reader behaves like a native application.
Post-publishing verification¶
To help assure package functionality, verify the changes below appear on the client machine.
The following entries should be present in
[HKLMSOFTWAREMicrosoftAppVSubsystemVirtualRegistry]PassThroughPaths
. If they are not present in the registry, add them:HKEY_CURRENT_USERSOFTWAREAdobeAcrobatReader
HKEY_CURRENT_USERSOFTWAREAdobeAdobeAcrobat{2015|DC}DiskCabs
HKEY_CURRENT_USERSOFTWAREAdobeAdobeSynchronizer
HKEY_CURRENT_USERSOFTWAREAdobeCommonFiles
HKEY_CURRENT_USERSOFTWAREMicrosoftSpeech
HKEY_CURRENT_USERSOFTWARELotusNotes
Verify that the
[HKEY_LOCAL_MACHINESOFTWAREPoliciesAdobeAcrobatReader2015FeatureLockDown]bUpdater
registry entry is present with a value set to 0.Since, pass-through keys only work when their parent hives are locally available on the machine,
HKEY_CURRENT_USERSOFTWAREAdobeAdobeAcrobat{2015|DC}
must be present on the client system. Runtime.bat performs this work for all domain users on the first launch of Reader.
Note
Adobe Acrobat Reader Free Download
The Runtime.bat method does not work for local users. When such support is needed, do not to put Runtime.bat under tag in DeploymentConfig.xml; otherwise, local users would would encounter error 534 when Reader opens.
Unpublishing¶
Since the package creates extension points on system, it is necessary to stop the package before unpublishing and removing it from the client machine. The package should be unpublished globally as follows:
Patching¶
Adobe Acrobat Pdf Reader Free
Prerequisites¶
The original installer from which the Reader package was created.
An original Acrobat Reader App-V Package
The latest patch or update for the track that was originally installed.
The template that was created in the 'Create a template' section above.
Close the same processes that were closed when publishing the initial package.
Adobe Acrobat Reader Dc Installer
Pre-sequencing steps¶
The pre-sequencing steps are identical to those for creating an App-V Package.
Create a template¶
Use the template that was created during the Acrobat Reader Package creation guidelines above.
Sequencing a patch¶
Start the Microsoft Sequencer.
Choose File > Load Template… and select your saved template (.appvt).
Select Modify Existing Virtual Application Package. A popup will appear on the screen.
Choose the radio button Update Application in existing package.
Choose Next.
Browse to the .appv file of the Virtual Acrobat Reader application package that needs to be patched.
Choose Next.
After the sequencer is done loading the package, it will display the issues if anything is wrong with the machine. If there are no serious issues, choose Next. If there are issues, address those issues and repeat all the above mentioned steps.
Choose Select the installer for the application and browse to the .msp patch file that needs to be applied to the virtual package.
Choose Next. The patch is invoked automatically.
In case the Windows installer asks for the location of the MSI file, point to the location where application installer was copied.
Choose OK. Proceed normally while patching.
After the patch completes, close the patch installer.
Check 'I am finished installing' checkbox in the sequencer.
Choose Next.
Choose Next, after the sequencer collects the system changes.
Review the Installation Report which detects common sequencing issues during sequencing.
Choose Next.
Do not go to Configure Screen. Instead, choose 'Stop Now' and click Next.
From the Create Package screen, select Continue to modify using Package Editor.
Choose Next.
Choose Close. The Package Editor will open.
Select the Package Files tab and expand
Root>VFS
.Verify the following the following folders are not present in the package:
LocalAppDataLow
AppData
Profiles
Go to the Advanced Tab and check:
Allow COM Objects to interact with Local System
Allow all named objects to interact with Local System
The scripts and other files added while creating the package from scratch are lost during patching. Re-add them as described in Sequence Acrobat Reader above.
Choose Menu > File > Save.
Close the Editor.
Post Sequencing Steps¶
Modify DeploymentConfig.xml
as described above.
Known issues¶
Automatic updates or manual end user updates are not supported. App-V updates are pushed by enterprise IT.
On-the-fly switching of the default PDF handler (viewer) from within the application is not supported. Handler selection can occur at install time or prior to deployment.
PDF previews are not visible in Windows Explorer.
Opening a PDF inside Internet Explorer does not work on Win 8.1 and Win 10 when IE's Enhanced Protected Mode is turned on.