Show-InstallationProgress -WindowLocation 'BottomRight' -TopMost $false # Show Progress Message (with the default message) Show-InstallationWelcome -CloseApps 'acrobat,acrodist,AcroRd32,AcroCEF' -CloseAppsCountdown 12600 -BlockExecution -MinimizeWindows $false 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): 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). At the moment, I will assume you have some familiarity with the framework, but feel free to ask questions. The following are some snippets of my PS App Deploy script.
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. I will also show potential msiexec examples instead of just the PS App Deploy version. Since Acrobat allows them to edit documents (and they do quite a bit), I can't just go around shutting their Acrobats down. I personally use the PowerShell App Deployment Toolkit to control the installer and give users to the opportunity to shutdown their Acrobat before continuing.
You may need to tweak some of the below to fit your environment. Our environment deploys Acrobat Pro to all users, though I would assume the steps would be similar for Reader.
0 kommentar(er)
