HOME




© 2015 Adobe Systems, Inc. All rights reserved.

Updated Jun 07, 2017.

App-V Deployment: Acrobat DC

This guide describes how to deploy Acrobat DC via App-V so that the application is delivered on demand but run as if they were installed locally. Available downloads include:

MSI Downloads

Named user deployments

In additional to traditional, serialized licensing, DC products provide the option for admins to use named-user deployments and thereby leverage existing enterprise and federated IDs. The Adobe Admin Console provides a central location for managing your Adobe entitlements, including specific users and groups, across your entire organization. It also provides other tools for managing software, users, and devices and supports license management for all Adobe products. For more information, see:

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 be configured by IT prior to deployment.
  • PDF previews are not visible for the PDF Files 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.
  • Conversion of .vsl files does not work with App-V Acrobat via Context Menu Handlers. For details and a work around, see https://helpx.adobe.com/acrobat/kb/pdf-conversion-of-visio-files-through-context-menu-in-app-v-envi.html
  • App-V Acrobat crashes while performing Send for Signature if App-V Reader is present on the same machine and not previously launched by the user. For details, see https://helpx.adobe.com/acrobat/kb/send-for-signature-crashes.html.

DC system requirements

  • Microsoft Application Virtualization Sequencer Version 5.0 SP3 or 5.1 installed on the machine.
  • Acrobat DC (either track)
  • Product system requirements
  • 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.

Preparing the environment

Prepare the sequencing machine following Microsoft’s guidelines.

  • Create the following registry DWORD entry with a value of 1 to see the option of selecting PVAD while sequencing: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Sequencer\Compatibility]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

In order to assure unnecessary files does not get carried inside the package, do the following:

  1. Launch the Microsoft App-V Sequencer.

  2. Go to Tools > Options.

  3. In the pop-up, go to Exclusion Items tab.

  4. Choose New.

  5. Add the following folders to the Exclusion Items List:

    • [{Profile}]
    • [{AppData}]
    • [{LocalAppDataLow}]
    • [{Common AppData}]\Adobe\SLStore
    • [{ProgramFilesCommonX86}]\Adobe\PCF
    • [{ProgramFilesCommonX86}]\Adobe\SLCache
    • [{ProgramFilesCommonX86}]\Adobe\Adobe PCD
    • [{AppVPackageRoot}]\Acrobat\Browser\nppdf32
  6. Close the options window.

  7. Choose File > Save As Template…

  8. Choose OK when the dialog appears.

  9. Save as an .appvt file.

  10. Exit.

Optional configuration

  • Suppress the EULA via one of the following:

    • Open setup.ini, and add the following line to the [Product] section: - CmdLine=EULA_ACCEPT=YES
    • Use Customization Wizard to suppress EULA for Acrobat Installer.
    • Perform a custom install using a modified command-line as discussed in “Sequence Adobe Acrobat”.
  • Use the Customization Wizard to further customize the product.

Sequence Adobe Acrobat

  1. Start the Microsoft Sequencer.
  2. Choose Go to File > Load Template… and select your saved template (.appvt).
  3. Select Create a new Virtual Application Package > Create Package.
  4. Choose Next.
  5. If there are any warnings on the Prepare Computer screen, correct them.
  6. Choose Next.
  7. On the Type of Application screen, select Standard Application.
  8. Choose Next.
  9. On the Select Installer screen, enter the path to your product installation files (Setup.exe). For custom installs, check Perform Custom Installation.
  10. Choose Next.
  11. In the Package Name screen, enter an application name (such as Adobe Acrobat DC).
  12. In the PVAD screen, enter the Acrobat installation path. Install Acrobat to this location only.
  13. When the installer appears in the Sequencer Screen, select “Trial and subscription mode”. Note: Licensing options appear in subsequent sections.
  14. Install to the location that has been entered as PVAD above using the “Customize” button in the Installer.
  15. Follow the on-screen instructions.
  16. Choose Close (do not choose Launch Now). If you have chosen Custom Installation Option, nothing will happen on the machine.
  17. To install Acrobat via a command-line and suppress the EULA:
  1. Open a command window in admin mode.
  2. Go to the Acrobat installer location.
  3. Verify Acrobat is installed in the PVAD location.
  4. Run the following:
Setup.exe /msi EULA_ACCEPT=YES INSTALLDIR=<Path given as PVAD> <additional installer options>
  1. After installation completes, select I am finished installing.

  2. Choose Next.

  3. Do not run any Application in the Configure Software screen. Choose Next.

  4. After the Sequencer collects the system changes, review the Installation Report which detects common sequencing issues.

  5. Choose Next.

  6. Choose Stop Now.

  7. Choose Next.

  8. Select “Continue to modify package without Saving using the package editor”.

  9. Choose Next.

  10. In Package Editor window, open the Advanced Tab and check the following checkboxes:

    • Allow virtual applications full write access to virtual file system.
    • Allow COM Objects to interact with Local System.
    • Allow all named objects to interact with Local System.
  1. Verify the files and folders excluded above do not appear in the package:

    • <Package root>\Acrobat\Browser > nppdf32.* (any files starting with that string)
    • <Package root>\VFS\Profile
    • <Package root>\VFS\Local\AppDataLow
    • <Package root>\VFS\AppData
    • <Package root>\VFS\Common Appdata\Adobe\SLStore
    • <Package root>\VFS\ProgramFilesCommonX86\Adobe\SLCache
    • <Package root>\VFS\ProgramFilesCommonX86\Adobe\Adobe PCD
    • <Package root>\VFS\ProgramFilesCommonX86\Adobe\PCF
  2. Select “Merge with local Directory” option for the following folders.

    • <Package root>\VFS\ProgramFilesCommonX86\Adobe
    • <Package root>\VFS\CommonAppdata\Adobe
  3. Add the necessary files to the Scripts folder.

    • C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\P7\dispatchtable.xml (Available on the sequencer machine)
    • adobe_prtk.exe (Available as part of APTEE 9.0 as a download from the Licensing Website)

Embed scripts

  1. Go to the “Package Files” Tab in the Editor.
  2. Navigate to Package > Scripts folder.
  3. Right-Click the Scripts Folder and choose Add to add embed a new script into the package so that they can be leveraged on the client machine.
    • Publish.ps1: A PowerShell script to identify the location of App-V Acrobat on system, deploy Acrobat App-V in various Licensing modes, and suppress the Updater on the client.
    • Unpublish.ps1: An un-publish script to remove Adobe Acrobat activation as well as remove the Updater and the location entry created by Publish.ps1.
    • (Optional) prov.xml: To volume serialize Acrobat on the client machine, include prov.xml in the package scripts. Generate this XML File on the sequencer machine using adobe_prtk.exe, running the APTEE Command from an elevated command prompt. Registration suppress is optional argument to be given here if admin wishes to suppress registration.
adobe_prtk.exe --generate --tool=VolumeSerialize --leid=<LEID> --serial=<Volume Serial No> [--regsuppress=ss]
  1. Save the package.
  2. Close the editor.

Post sequencing steps

The DeploymentConfig.xml file resides in the same folder as the .appv file. Modify it as described below.

  1. Create script extension points by adding the script calls inside the <MachineScripts> tag. The Publish and Unpublish scripts require arguments as follows:

    • Channel name: Either 2017 or 2015 or DC. 2015 is the default value.
    • The Package ID: Copy it from the <DeploymentConfiguration line. For example, PackageId="dcc25ced-6e2e-4a44-8ef3-4afe3e3fbde8"
    • Product path: Copy it from the <Application Id line in the <Applications> tag. For example, <Application Id="[{AppVPackageRoot}]\Acrobat\Acrobat.exe" Enabled="true">
<MachineScripts>
        <PublishPackage>
                <Path>powershell.exe</Path>
                <Arguments>-f "[{AppVPackageRoot}]\..\Scripts\Publish.ps1" <Package GUID copied from PackageID> "[{AppVPackageRoot}]\Acrobat\Acrobat.exe" [-ChannelName {2015|2017|DC}] [-Serialize]</Arguments>
                <Wait RollbackOnError="true" Timeout="240"/>
        </PublishPackage>
        <UnpublishPackage>
                <Path>powershell.exe</Path>
                <Arguments>-f "[{AppVPackageRoot}]\..\Scripts\Unpublish.ps1" [-ChannelName {2017|2015|DC}] </Arguments>
                <Wait RollbackOnError="false" Timeout="120"/>
        </UnpublishPackage>
</MachineScripts>

Note

the Publish script takes -Serialize as an optional argument to volume serialize the product. Otherwise, Acrobat is deployed in trial mode on the client machine.

  1. Set the COM integration mode:
<COM Mode="Integrated">
        <IntegratedCOMAttributes OutOfProcessEnabled="true" InProcessEnabled="false" />
</COM>
  1. Set named object interaction. Change all <Objects> tags to false:
<Objects Enabled="false">
  1. Disable virtual fonts subsystem. The required fonts would be locally registered on the client machine by our supplementary App-V installer.
<Fonts Enabled="false">
  1. (OPTIONAL) Hide unnecessary extension points. Configure <Applications> to hide “AcrobatInfo” application from being seen in the list of recommended programs when users try to change the default PDF viewer. This application also has the name “Adobe Acrobat”; however, as a default application for .pdf files, it does not perform anything and so should not appear.
<Application Id="[{AppVPackageRoot}]\Acrobat\AcrobatInfo.exe" Enabled="false">
        <VisualElements>
                <Name>Adobe Acrobat</Name>
                <Icon />
                <Description />
        </VisualElements>
</Application>

Deploying a client package

Prerequisites

  • Enable scripting on client machines. The Acrobat 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:
Set-AppvClientConfiguration -EnablePackageScripts $true
  • Publish the package globally: Extension points for the Acrobat App-V Package require machine-level installation. With App-V 5.0 SP2, publishing globally automatically creates these extensions and Acrobat behaves like an installed application.

  • Apply the hotfix to the App-V 5.0 SP3 Client See http://support.microsoft.com/kb/3039022. This hot-fix fixes the problems of the application crashing while performing an OCR, editing a PDF file and opening a shared review PDF file.

  • Optional: Enable FeatureLockdown on Clients. To suppress or lock certain features on the client, do one of the following:

    1. Manually create the FeatureLockDown keys on the client machine either by pushing policies from the server.
    2. Add the keys inside the package itself from the package editor window using the Registry tab. This requires removing the HKEY_LOCAL_MACHINE\SOFTWARE\Policies registry entry from the list of pass-through registry keys (at HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\AppV\Subsystem\VirtualRegistry 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

  1. To publish the package globally, run the following Power-Shell command:
Add-AppvClientPackage [Path_to_AppV_Package] -DynamicDeploymentConfiguration
[Path_to_DeploymentConfig_xml_File] | Publish-AppvClientPackage –Global |
Mount-AppvClientPackage
  1. To leverage all of Acrobat’s features, install the supplementary App-V MSI Downloads on the user’s machine which contain Acrobat’s integration points for applications such as:
  • MS Office Integration - Context Menu and In-App Acrobat Ribbons.
  • Mails Integration - MS Outlook and Lotus Notes will start showing Acrobat Features.
  • Adobe PDF Printer - Allows the user to print any file to Adobe PDF.
  • Web Capture - Allows the user to be able to convert a webpage to Adobe PDF inside the Browser.
  • Registers necessary fonts on the client which will be used by the virtual application.

Unpublishing

If you have installed the MSI at the time of publishing the package, then it is recommended to uninstall it before unpublishing or removing the package from your system. Since the Acrobat 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:

  1. Stop the package.
  2. Verify adobe_prtk.exe is in the same directory as the package.
  3. Run the following:
Get-AppvClientPackage -Name "*Adobe Acrobat *" | Stop-AppvClientPackage |
Unpublish-AppvClientPackage -Global | Remove-AppvClientPackage

Patching Acrobat

Prerequisites

  • An existing Acrobat App-V Package
  • The installer from which the actual Acrobat Package was created.
  • The latest Acrobat patch or update of the same channel from which the original package was created.
  • The template that was created in the “Create a template” section above.
  • Close the same processes that were closed when publishing the initial package.

Pre-sequencing steps

The pre-sequencing steps are identical to those for creating an App-V Package.

Sequencing a patch

  1. Start the Microsoft Sequencer.

  2. Choose File > Load Template… and select your saved template (.appvt).

  3. Choose Modify Existing Virtual Application Package. A dialog appears.

  4. Choose Update Application in existing package.

  5. Choose Next.

  6. Browse to the .appv file of the virtual application package that needs to be patched.

  7. Choose Next.

  8. 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 the previous steps.

  9. Choose Select the installer for the application.

  10. Browse to the .msp patch file.

  11. Choose Next. The patch is invoked automatically.

  12. If the Windows installer asks for the location of the MSI file, point to the location where the application installer was copied.

  13. Choose OK.

  14. After the patch completes, close the patch installer.

  15. After installation, select I am finished installing.

  16. Choose Next.

  17. After the application collects the system changes, choose Next.

  18. Review the Installation Report which detects common sequencing issues during sequencing.

  19. Click Next.

  20. Do not go to Configure Screen. Instead, select Stop Now.

  21. Choose Next.

  22. Select Continue to modify package without Saving using the package editor.

  23. Choose Next.

  24. Choose Close. The Package Editor will open.

  25. Move to Advanced Tab and check the following:

    • Allow virtual applications full write access to virtual file system.
    • Allow COM Objects to interact with Local System.
    • Allow all named objects to interact with Local System.
  1. Verify the files excluded from the package (above) are not present inside the package.

  2. Select “Merge with local Directory” option for the following folders.

    • <Package root>\VFS\ProgramFilesCommonX86\Adobe
    • <Package root>\VFS\CommonAppdata\Adobe
  1. The scripts and other files added while creating the package from scratch are lost during patching. Re-add them as described in “Sequence Adobe Acrobat” above.
  2. Save the package and move on to Post Sequencing Steps in the following section.

Post Sequencing Steps

Modify DeploymentConfig.xml as described above.