Adobe Acrobat Reader customizations for Windows

-

Adobe Acrobat Reader is an essential tool when working with PDF documents but is not the easiest tool deploy to a fleet of Windows devices. Adobe has made available a customization wizard however that can be used to modify the package for easier deployment.

Required items:

Note: The Customization Wizard only works in the multi-language, 64-bit version of Adobe Reader.

Step 1: Download required software.
Download both Adobe Reader and the Customization Wizard linked above.

Step 2: Install the Customization wizard

Step 3: Extract Acrobat Reader executable file into a folder

Step 4: Launch the customization wizard and open AcroPro.msi

Step 5: Modify the following items:

Personalization options:
  • Suppress display of End User License Agreement


Installation Options:
  • Make reader the default PDF viewer
  • Run installation Silently (no interface)
  • Suppress reboot

Online services and features
  • Disable upsell


Step 6: Go to File > Save Package to save the configuration updates

Step 7: Close Adobe Customization Wizard and run setup.exe to confirm that following changes were applied:
  • Install is silent.
  • Launching Acrobat Reader does not prompt the user to accept the license agreement.
  • “Try acrobat Pro” does not appear in the top right of the screen.
Step 8: Deploy package via Workspace ONE
This package can now be zipped up and deployed via the console as a zip package. The install command should be set to setup.exe and the install completion check should be set to the version of acrobat.exe



Comments

Post a Comment

Popular posts from this blog

Windows device lifecycle. Hands-off reprovisioning with Workspace ONE.

-
Image
There are multiple options available for onboarding a Windows desktop into Workspace ONE UEM. Different options are available depending on if the device is a Greenfield device (brand new out-of-the-box device) or a Brownfield device (currently used device, possible under a legacy device management system). But what about device recycling? How do you enroll a device that has been returned to IT? Typically, this is a hands-on approach and will involve multiple steps that will look something like: Re-imaging the device, via USB or Windows Deployment Services (WDS). Logging in as the staging account. Downloading Intelligent Hub. Enrolling as the staging user. Logging out. Handing the device off to the final end user, or placing it back into stock. Workspace ONE Tunnel (or other pre-auth VPN) if the device is to be domain joined. If testing using a VM, ensure that the VM has been assigned a serial number What if there was a better way? What if you could deploy a new image to a device and ha...
Read more

Deploying certificates to the Quest 2

-
Image
I spent some time working with the Workspace ONE XR Hub team (find out about HR Hub here ) and whilst it is very simple to install a certificate to a Quest enrolled in Workspace ONE, it's not that simple to install one on a non-enrolled device. Why would you want to install a certificate on an Oculus Quest you might ask? Well, I am a volunteer CS teacher for TEALS  and the school I was working with purchased some Quest 2 headsets for the students. Unfortunately, she was unable to connect them to the school network as the network was protected by securly an needed a certificate installed on the device before it was able to connect to the network. The schools IT team were unable to help and since I had experience with the Quest 2 while working with XR Hub team I was asked if I could help. The Quest 2 (like most VR/XR headsets) runs a version of Android AOSP  heavily customized by the OEM. If I could get to the underlying O/S, I would be ...
Read more