- #How to run adobe patch installer install
- #How to run adobe patch installer update
- #How to run adobe patch installer upgrade
- #How to run adobe patch installer full
- #How to run adobe patch installer software
If you need to customize your deployment, continue reading, otherwise open up GPO and deploy it via the software management policy under Computer Configuration.
#How to run adobe patch installer update
Make sure you update the AIP, not the msi you used to create the AIP! At this point you are ready to deploy. Msiexec /p "AdbeRdrUpd932_all_incr.msp" /a "\\INSERT SHARED DIRECTORY LOCATION HERE\AcroRead.msi" Msiexec /p "AdbeRdrUpd931_all_incr.msp" /a "\\INSERT SHARED DIRECTORY LOCATION HERE\AcroRead.msi" Change back to where you saved the msp files and run the following commands:
#How to run adobe patch installer install
Once the install is completed, the next step is to patch it with the Reader msp files. You will need to select a network share where "authenticated users" and "Domain Computers" have at least read access. Run the following command:įollow the on-screen prompts. For different instances and software, a different option may work better.Now, do an administrative install to a shared network location.Ĭhange directories to where you extracted the msi file, as noted above.
#How to run adobe patch installer upgrade
You could actually choose either of the last options, but it’s a little faster and more efficient to upgrade instead of uninstall and re-install. Select the Current GPO, the package you want to upgrade, and choose that the package can upgrade over the existing package. Click the Add… button to open up another dialog box. On the Properties page that opens up, switch to the Deployment tab and consider selecting the “Uninstall this application when it falls out of the scope of management” setting. This will bring up the properties menu for the package.
msi, choose the Advanced Deployment method. Leave the original package there and just add this package in addition to it. Step 4 Once the installer complete, you can copy this local copy of the deployment folder as a sub-folder into the server copy of the Adobe Reader 9.1 deployment folder.Īdd the new package to the same GPO like normal. msp into your local copy of the Adobe Reader 9.1 deployment folder. In this case, download the Adobe Reader 9.1.2 update. msp file for the version you want to go to. It can be copied anywhere locally, we just want to work on it locally as it’s a little more reliable that working on the server. Step 1 Make a copy of your Adobe Reader 9.1 deployment folder locally. Since we have 9.1 deployed, this one be a problem and we’ll just need to apply the. If you visit the update page for Adobe 9.1.2, you’ll see that it can apply to 9.1 or 9.1.1. You can also opt to get e-mails about updates and such.įollowing the instructions from the Adobe Customization Wizard post, you can deploy 9.1 as a standard package through Group Policy using the. It only takes a few minutes to request an agreement and get an answer back shortly. Yes, even the free ones and internally to your building. You’ll need an agreement with Adobe on file to distribute their software.
#How to run adobe patch installer full
You can find the Adobe Reader 9.1 as a full installer (.msi) and 9.1.1 and 9.1.2 updates as incremental patches (.msp) at the Adobe Reader update site. Now we need to deploy those updates to the machines that we remotely loaded with Adobe Reader 9.0. Unfortunately, Adobe had to release 9.1, 9.1.1, and 9.1.2 versions to deal with the Javascript exploit that was possible in malicious PDFs and other bugs. You can discern the original deployment of Adobe Reader 9.0 from this article on the Adobe Customization Wizard. For something licensed like Acrobat, I just deploy the software to select computers by adding specific computers to a security group in the Active Directory and restrict the number of deployed instances to the number of licenses we have available.įor this article, we’ll be using Adobe Reader 9 to discuss updating the deployed software. This works well enough for deploying software.
When I have to upgrade hundreds of computers from one version to a new version, it is not plausible to walk around and install the latest version manually. In hopes of establishing manageability, greater security, and efficiency through centralization, I’ve been successfully adding more and more applications to those which are deployed via Group Policy.
0 kommentar(er)
