AlexE

Our environment deploys Acrobat Pro to all users, though I would assume the steps would be similar for Reader. You may need to tweak some of the below to fit your environment. I personally use the PowerShell App Deployment Toolkit to control the installer and give users to the opportunity to shutdown their Acrobat before continuing. Since Acrobat allows them to edit documents (and they do quite a bit), I can't just go around shutting their Acrobats down. I will also show potential msiexec examples instead of just the PS App Deploy version. If you are using the latest builds of ConfigMgr Current Branch, you could also use the built-in application detection/close function, though it is still not as feature rich as the App Deploy Toolkit. The following are some snippets of my PS App Deploy script. At the moment, I will assume you have some familiarity with the framework, but feel free to ask questions. Remember, if you are installing Acrobat/Reader fresh, you wouldn't need to worry about shutting down apps beforehand (and the installers may handle this automatically, but I like handling it myself). If you don't need to worry about user surprises or loss of work, you could just brute force shut down the relevant applications.For Full Installs (PS App Deploy Toolkit): Show-InstallationWelcome -CloseApps 'acrobat,acrodist,AcroRd32,AcroCEF' -CloseAppsCountdown 12600 -BlockExecution -MinimizeWindows $false ## Show Progress Message (with the default message) Show-InstallationProgress -WindowLocation 'BottomRight' -TopMost $false (SNIP Installation defaults from framework) ## Install base MSI with Transform Execute-MSI -Action Install -Path "$dirFiles\AcroPro.msi" -Transform "$dirFiles\AcroPro-SerialLicense.mst" -Parameters "REBOOT=ReallySupress /qn" ## Install patch Execute-MSI -Action Patch -Path "$dirFiles\AcrobatDCUpd1701220093.msp" -Parameters "REBOOT=ReallySuppress /qn" For Updates Only (PS App Deploy Toolkit): Just don't have the 'install base MSI with Transform Straight Up msiexec installs: (I personally would place this in a batch script or PowerShell script. If using PS, I would use Start-Process with an install variable for the 'ArgumentList') Remember, to use %~dp0, you must be using a batch script. msiexec /i AcroPro.msi /qn PATCH="%~dp0AcrobatDCUpd1701220093.msp" TRANSFORMS="%~dp0AcroPro-SerialLicense.mst" REBOOT=ReallySuppress You could also run the patch separately if you would like (mimics my above PS App Deploy scenario). msiexec /update AcrobatDCUpd1701220093.msp /qn REBOOT=ReallySuppress Regarding the transform not applying: I have seen this occur in our environment to a limited extent, but usually the only parts that do not apply properly are the registry policy settings I have created. To resolve this issue, I made a PowerShell script that removes the associated Policy Registry keys and then re-applies them directly. Our helpdesk can then fire this off across a Remote PowerShell session when a user runs into issues. Other customizations, such as whether or not to install features, usually apply correctly for me. Detection Method: I always detect on the MSI, such as '{AC76BA86-1033-FFFF-7760-0C0F074E4100}'. For fresh installs, I do not depend on the version. For Updates, I require the MSI to match the version I am installing. Hopefully this helps you figure out what is happening for your installs.