Update & Upgrade Problems

How to Deploy an Acrobat 2017 MSP Update Through Group Policy

Anum MushtaqAnum Mushtaq Nov 5, 2026 871 views

Question details

The user needs to apply an Adobe Acrobat 2017 MSP patch update to existing installations via Group Policy without creating an Administrative Installation Point.

How to Deploy an Acrobat 2017 MSP Update Through Group Policy
Product
Adobe Acrobat 2017
Device & OS
Windows
Scenario
Deploying an MSP patch update across multiple network computers that already have the baseline software installed.
Observed behavior
Requires a reliable method, such as a startup deployment or scripted msiexec command, to push the update silently to client machines.
Before you start

Ensure that the .msp update file is stored in a shared network folder with read permissions for 'Domain Computers', and verify that all target machines already have the baseline Acrobat 2017 installed.

Solution 1Recommended

Deploy the MSP Update Using a Startup Script in Group Policy

Use a scripted msiexec command within a Group Policy startup script to silently apply the patch to matching client installations over the network.

Instead of using an Administrative Installation Point, you can directly patch existing installations by deploying a batch script through Group Policy. This method ensures the update runs with the necessary administrative privileges before the user logs in.

1
Create the deployment script

Open Notepad and create a batch script with the following command: msiexec /p \\YourServer\Share\Acrobat2017Upd1701130188.msp /qn /norestart. Save this file as 'deploy_update.bat' in your designated network share.

2
Open Group Policy Management

Press Win + R, type 'gpmc.msc', and press Enter. Create a new Group Policy Object (GPO) or edit an existing one linked to the Organizational Unit (OU) containing your target computers.

3
Navigate to Startup Scripts

In the Group Policy Management Editor, go to Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown).

4
Assign the script

Double-click 'Startup', click 'Add', and browse to select the 'deploy_update.bat' file from your network share. Click 'OK' and apply the policy.

Pilot Testing Recommendation: Always test the GPO deployment on a pilot computer before broadcasting it broadly to ensure that the installed product code, language, and patch prerequisites perfectly match the MSP file.
Free Microsoft Office alternative

Simplify Enterprise Deployments with WPS Office

Managing complex patch deployments for heavy PDF and document software can create significant IT overhead. WPS Office provides a lightweight, all-in-one suite featuring Word, Excel, PowerPoint alternatives, and a powerful PDF editor. It is incredibly easy to deploy across enterprise networks via Group Policy.

  1. 1. Download the enterprise installer: Obtain the lightweight MSI installer from the official WPS Office website.
  2. 2. Deploy via Group Policy: Use your standard Windows Server GPO settings to silently push the WPS Office MSI to your network client machines.
  3. 3. Manage effortlessly: Enjoy automated, headache-free updates and high compatibility with all your enterprise documents.
Lightweight installation package reduces network strain during mass GPO deployments.Fully compatible with Microsoft Office document formats and standard PDFs.Built-in professional PDF editor for seamless reading, converting, and editing.Cost-effective solution with a familiar UI that minimizes employee training time.
microsoft office alternative - wps office

Frequently Asked Questions

Why does the MSP update fail during Group Policy deployment?

Failures typically occur if the target machine lacks the required baseline software, if there is a mismatch in the installed language or product code, or if network share permissions prevent the computer account from reading the .msp file.

Do I need an Administrative Installation Point (AIP) to apply this patch?

No. While AIPs are used for certain deployments, you can apply this MSP patch directly to existing client installations using a scripted msiexec command via a GPO startup script.

What do the /qn and /norestart switches do in the msiexec command?

The /qn switch instructs the Windows Installer to run silently without displaying a user interface, and /norestart prevents the system from automatically rebooting after the installation completes, which is crucial for background deployments.