- Adobe Customization Wizard For Mac Windows 10
- Adobe Customization Wizard For Mac Windows 10
- Adobe Customization Wizard 10
Configuration Options¶
During an Acrobat non-silent install, the installer displays a number of screens which guide the user through the process and allow for licensing as well as the customization of certain features. Since admins typically use silent installs for mass deployments, Adobe provides various methods for pre-deployment configuration, including common tasks such as:
- Licensing.
- Disabling registration.
- Granting activation exceptions for offline users.
- Selecting a language.
- Disabling the startup splash page.
- Setting a default PDF viewer when Acrobat or Reader is already present.
- Accepting the EULA on behalf of your organization.
In earlier versions of the Wizard there was a Wizard bug which required that bToggleWebConnectors be disabled manually via the registy. The web connector UI cannot be disabled with bUpdater. This bug was fixed in the January, 2015 release. Download the new MST (for Windows)/PKG (for Mac OS) for the new CCT Single App launch experience. (Optional) Customize the 11.0 installer bits using Customization wizard (Windows only). Install Acrobat 11.0.07 + MST using standard deployment steps on Windows / Mac OS. Disable product upsell¶. Products that don’t provide the full set of features by default provide the user the opportunity to upgrade. For example, Reader users can purchase additional tools and features, and Acrobat Standard users can upgrade to Acrobat Professional.
By performing these tasks ahead of time, you can simplify the end user experience when the product first launches.
Configuration methodologies
Configuration methods and tools include the following:
- Customization Wizard for Mac: Modify basic installer settings prior to deployment.
- Plist preferences for pre and post deployment configuration.
- The APTEE tool for serialization, suppressing registration, and accepting the EULA.
Feature | |||
---|---|---|---|
Language | No | Yes | Yes |
Splash page | No | Yes | No |
Default PDF Viewer | No | Yes | No |
EULA | Yes | No | Yes |
Licensing | Yes | No | Yes |
Registration | Yes | No | Yes |
Activation | Yes | No | Yes |
Wizard for Mac¶
The Acrobat DC Customization Wizard for Macintosh provides IT admins the ability to customize product installation settings prior to organization-wide deployment. Note the following:
- This Wizard version cannot be used to customize Reader or trial Acrobat installs.
- The product version and Wizard version must be identical. Thus, the DC Wizard can only be used with DC products.
Running the Wizard requires a writeable area, so do not run it from a DMG disk image. Copy it to a folder and run it from there.
Installation¶
- Download the Wizard DMG (all tracks)
- Mount the DMG.
- Copy
AcrobatCustomizationWizardDC.app
to/Applications
. - Run the application:
/Applications/AcrobatCustomizationWizardDC.app
Installer locations¶
Required
- Click the folder icon to the right of the Locate Installer field.
- Navigate to the installer and click it.
Licensing/Activation¶
Required
Product activation is required as described in the policy details at http://www.adobe.com/products/activation/.
Serialized licensing¶
While there is a grace period for online activation, it may be true that in some enterprise settings users are permanently or temporarily offline. In that case, you can grant an offline exception to the activation requirement.
Enter a serial number in the serial number input box to pre-serialize the package. The serial number should contain exactly 24 digits after stripping the dashes and spaces. Selecting Grant Offline Exception requires the use of a volume serial number.
Named user licensing¶
The serial number field is only used for serialized deployments where the machine is licensed. If you’re creating a non-serialized deployment and are using a named-user deployment where entitlements are managed via the Admin Console, leave the serial number blank. After deployment, users will be required to sign-in on product launch in order to activate the product. If the user signs out, the product is deactivated. Named-user deployments support Adobe IDs, Federated IDs, and Enterprise IDs.
Adobe Customization Wizard For Mac Windows 10
EULA acceptance¶
Optional
Check Accept End User License Agreement if the individual selecting the checkbox is accepting the EULA for all end users. When checked, end users will not be shown the EULA on product startup.
Note
You cannot set
EULAAcceptedForBrowser
in the plist. Using the Mac Wizard or APTEE is required.Registration¶
Optional
After providing a serial number, check Grant Offline Exception & Disable Registration to make the following UI changes on application startup:
- Users are not prompted to enter or create an Adobe ID.
- Sign-in dialogs do not appear (if services are disabled).
- The installer will not require online activation.
In this case, end users are not asked to validate the serial number or activate the product online. This option requires a volume serial number; otherwise, the Customization Wizard will fail with the error code 14.
The default workflow with Acrobat DC is that if the user doesn’t go online within first 30 days to validate the serial number and activate the product, the application stops working. A working internet connection is a pre-requisite for this option. By default, this checkbox is selected when the Customization Wizard is launched.
Browser Integration¶
Optional
Check Disable PDF rendering in browsers to disable browser integration. During UI install workflows, this integration is apparent in the Custom Install dialog where the browser plugin is checked by default. Disabling browser integration disables this option.
Installation type
Feature lockdown¶
Optional
Note
Recommended: Review Locking preferences before choosing this option.
Like Windows, feature lockdown allows IT to create settings that cannot be changed by end users. Since the Wizard modifies the installer, the embedded feature lockdown file is installed on all end user machines at install time. For features that have a user interface (UI), the UI is either removed from the product or disabled.
To lock preferences:
- Create a plist file named
com.adobe.Acrobat.Pro.plist
. - Check Enable Feature Lockdown.
- Browse to the plist file you created.
- Choose OK.
Adobe Customization Wizard For Mac Windows 10
Note
The Mac Wizard creates an identical file in
/Library/Preferences/
. If a plist already exists on a client machine at that location, it is replaced at deployment time.Saving installer changes¶
After configuration, save the customized installer:
- Choose OK when finished.
- When the save dialog appears, enter an output package name ending with PKG.
- Select an output location that is writable.
- Choose Save.
- When the Success screen appears, choose OK.
Note
The parent directory must be writable otherwise an error is thrown. If the file already exists, the file is overwritten.
If none of the optional checkboxes are selected, the output installer is pre-serialized using the provided serial number thereby avoiding the appearance of the serial number pane during the install.
Wizard logging¶
The Customization Wizard creates the log file at
~/Library/Logs/Adobe/CustWiz.log
. If log file creation fails, the log is dumped to the console. If the Grant Offline Exception is checked, logs are also created at /tmp/oobelib.log
.![For For](https://themacgo.com/wp-content/uploads/2018/12/Adobe-Photoshop-Lightroom-Classic-CC-2019-for-mac-free-download-themacgo.jpg)
Code | Description |
---|---|
1 | The Acrobat Installer Package could not be read. |
2 | The destination Installer package exists and is not writable. |
3 | The XML file generated for embedding inside the installer could not be read. |
4 | Invalid arguments passed to the script which modifies the package. |
5 | Could not expand the Input installer package to process. |
6 | Could not flatten the expanded input package into the output package. |
7 | Failed to embed the XML file generated into the package. |
8 | Could not remove the temporary expanded package. |
9 | The featurelockdown plist is not readable. |
10 | Failed to embed the featurelockdown plist into the package. |
14 | The APTEE tool called from within returned an error. See /tmp/oobelib.log for details. |
Language selection¶
Acrobat installers are multi-language (MUI) installers. By default, the product language is set to match the OS.
- There are no language-specific serial numbers.
- All languages are installed by default.
- The OS language will determine Acrobat’s language.
- Trials are available in all supported languages, although only a single trial language can be installed at any point of time.
You can modify the default behavior by modifying a plist preference. See
UseMUI
in the Preference Reference. Language configuration can be complex in some environments and may involve knowing:- The relevant locale and language codes for your serial number.
- What languages to install on the machine (one, several, or all).
- Whether or not the default language is that of the OS.
- Whether or not the user should be allowed to reset the language.
- Whether the language variant maps to a differently named base MST.
- If you need additional font packs which are available as separate installers.
Splash page¶
By default, a splash page appears on application startup. To disable this behavior, set
SplashDisplayedAtStartup
to 0.PDF ownership¶
When both Acrobat and Reader are present, PDF ownership settings must be set through the user interface.
Activation workflows¶
When offline and activation exceptions are required, use the tools in the APTEE.
Activation workflow details¶
Goal | Details |
---|---|
No activation exception | No activation exception employed. Every end user will have to be online to complete the serial number validation after successful silent activation ping. Offline grace period expires after 30 days. |
Activation exception via Wizard (other than an imaged OS) | Online access required. The Wizard validates the serial number and saves the exception inside the installation pkg. |
Activation exception via APTEE. Installer on a shared server. Install may be UI based. Required for an imaged OS. | Online access required. Run APTEE as described below. Final fantasy xv a new empire multiple accounts. |
Activation exception via command line. Installer on a shared server. Install may be UI based. | Use the Wizard or run APTEE as described below. |
Activation exception when installer runs on a DVD | Online access required. For retail and volume licenses, the Adobe Application Manager (AAM) displays the short code for an activation request. Users log in to the Adobe website with an Adobe ID and enter the serial number and request code. After validation, the activation service displays a response code. The user enters the code in the AAM screen. On success, AAM grants the activation exception. |
Command line trial install | Activation is required. After any deployment method, registration with an Adobe ID is required. All end users see a Registration dialog. |
License a trial install with activation | Serialize by running APTEE with administrator privileges on all user machines (run over command line with appropriate parameter set to S/N). |
License a trial install with activation exception | Online access required. Run APTEE as described in below. |
Activation exception (type 2)¶
You can create an activated production package and serialize post deployment using APTEE. This method is used when user machines are not going to be online. To do so,
- Run APTEE on an online machine to generate the prov.xml file.
- Deploy the product on each machine.
- Run APTEE with the prov.xml file on each machine.
This article explains how to deploy Adobe Acrobat if you are using Adobe Creative Cloud for teams Single App. It applies to both Acrobat Pro and Acrobat Standard.
Note:
If you have a Creative Cloud All Apps membership, use Creative Cloud Packager for deploying Acrobat. See this page for detailed instructions.
To deploy Acrobat as Creative Cloud for teams Single App, perform the following steps in sequence:
- Download Acrobat 11.0.07 chained installer bits.
- Download the new MST (for Windows)/PKG (for Mac OS) for the new CCT Single App launch experience.
- (Optional) Customize the 11.0 installer bits using Customization wizard (Windows only).
- Install Acrobat 11.0.07 + MST using standard deployment steps onWindows / Mac OS.
Adobe Customization Wizard 10
Note:
Currently, Acrobat Creative Cloud for teams Single App (purchased using VIP) is not supported/certified on streaming virtual environments like Citrix XenApp or XenDesktop. See Deploying Adobe Acrobat Purchased using the Adobe Value Incentive Plan (VIP) in a virtualized environment.
Before you download Acrobat XI, make sure that your system meets the requirements:
Windows | Mac | |
Acrobat XI Pro | Acrobat XI Pro - Windows | Acrobat XI Pro - Mac OS |
Acrobat XI Standard | Acrobat XI Std - Windows | n/a |
Note:
This installer is multilingual; it can install Acrobat in any of the languages Acrobat supports. See the installation section below for more details.
2. Download CCT transform (Windows) / installer (Mac OS)
This MST/DMG file enables a first launch experience that is optimized for Creative Cloud for teams Single App users. Users can simply sign in with their Adobe ID and use Acrobat.
Windows | Mac OS | |
Acrobat XI Pro | AcrobatCCTWorkflow.mst | AcrobatCCTWorkflow.dmg |
Acrobat XI Std | AcrobatStdCCTWorkflow.mst | n/a |
3. (Optional, Windows only) Use the Adobe Customization wizard XI
You can use the Adobe Customization wizard to further customize your Acrobat deployment. For more information, see the Adobe Customization wizard documentation (Windows).
Important: Use the Acrobat Customization wizard to load AcrobatCCTWorkflow.mst and add your customizations in this MST only. A separate MST is known to cause issues. Launch the Customization wizard for Acrobat XI and follow these steps:
- Choose File > Open Package and select Acrobat 11.0 MSI in Acrobat 11.0 installer folder – AcroPro.msi.
- Choose Transform > Load Transform, and select AcrobatCCTWorkflow.mst.
Note:
Acrobat is configured to automatically ping Adobe servers to determine if there is a new patch/update available. If you want to change it for your deployment, you can do that using the Customization wizard.
4. Install Acrobat 11.0.07 + MST using standard deployment steps on Windows / Mac OS
To install Acrobat on windows, do the following:
- Install Acrobat 11.0.07 using chained installer.
- Apply CCT Transform (AcrobatCCTWorkflow.mst for Acrobat Professional or AcrobatStdCCTWorkflow.mst for Acrobat Standard).
4.1.1 Command line mode
Navigate to the Acrobat XI folder in the command prompt and run the following command:
Syntax example:
Setup.exe /sl '[LangCode]' /sALL /msi TRANSFORMS=”[TransformPath]”
In the command above:
- [TransformPath] is the absolute path to AcrobatCCTWorkflow.mst (or AcrobatStdCCTWorkflow.mst for Acrobat Standard) transform.
- [LangCode] is the numerical Acrobat Launch language code based on the following data:
2052=Chinese Simplified
1028=Chinese Traditional
1029=Czech
1030=Danish
1043=Dutch (Netherlands)
1033=English (United States)
1035=Finnish
1036=French (France)
1031=German (Germany)
1038=Hungarian
1040=Italian (Italy)
1041=Japanese
1042=Korean
1044=Norwegian (Bokmal)
1045=Polish
1046=Portuguese (Brazil)
1049=Russian
1051=Slovak
1060=Slovenian
1034=Spanish (Traditional Sort)
1053=Swedish
1055=Turkish
1058=Ukrainian
1025=English with Arabic support
1037=English with Hebrew support
6156=French (Morocco)
For example, if you pass “1033” in [LangCode], Acrobat launches in English.
4.1.2 Installation through standard deployment methods
You can also follow usual deployment practices for Acrobat as mentioned in Acrobat ETK.
The following example shows Acrobat Deployment through SCCM:
Make sure that following files are copied in Acrobat XI Installer Binaries folder:
- Acrobat CCT Transform – AcrobatCCTWorkflow.mst (or AcrobatStdCCTWorkflow.mst for Acrobat Standard)
Now in the same Acrobat XI installer Binaries folder, open setup.ini and add the following entry in the [Product] category:
Cmdline=TRANSFORMS=”AcrobatCCTWorkflow.mst”
See the image below:
Use it to deploy Acrobat using SCCM. Follow the usual processes for creating a package for deployment in SCCM Configuration manager. Give the path of Setup.exe in the Create Program Wizard in SCCM.
Once you have deployed Acrobat, you can uninstall it using the usual process for uninstalling msi packages. Here is the command-line syntax for uninstalling the Adobe Acrobat 11.0:
Syntax example:
msiexec.exe /x <path to Acrobat msi file> /qn
To install Acrobat on Mac OS, do the following:
- Install the Acrobat 11.0.07 chained installer package.
- Install the CCT Workflow package – AcrobatCCTWorkflow.pkg.
Mac OS installers are .pkg type installers that provide the necessary user interface prompts to run. You can chain the above three installers into one installer (maintaining the order above).
You can use standard deployment practices on Mac OS (such as ARD) to deploy the chained package. More information is available in Acrobat ETK.
You can deploy Acrobat updates using standard deployment practices used in your organization. For more information about updates, see Patch release notes.
Deploy Adobe Acrobat purchased using the Adobe Value Incentive Plan (VIP) in a virtualized environment
Currently, Adobe Acrobat purchased using the Adobe Value Incentive Plan (VIP) is not supported or certified on streaming/session virtual environments like Citrix XenApp or XenDesktop. For Acrobat subscriptions on VIP, you do not get a serial number for licensing. Users authenticate into Acrobat desktop and “activate” Acrobat with their Adobe ID. If you are looking to deploy Acrobat on such environments, purchase an Acrobat plan that provides you with a serial number.
However, you can deploy Adobe Acrobat purchased using VIP on dedicated virtual desktops (also known as VMs). It is similar to deploying on a local machine, and users can sign in with their Adobe ID to access Acrobat.
However, you can deploy Adobe Acrobat purchased using VIP on dedicated virtual desktops (also known as VMs). It is similar to deploying on a local machine, and users can sign in with their Adobe ID to access Acrobat.