When you first F12-build a Windows device, Acrobat Reader is included with the build. It allows users to open, view and print PDF files and even fill in PDF forms. But many staff users in particular need the ability to edit PDF files and create their own forms or portfolios. In order to do this, the Adobe Acrobat DC package needs to be installed on the computer. For school-owned computers, this can only be installed as a push-request from UDM by the school's ICT Coordinator or TSO. As one of the most-commonly deployed programs, Acrobat DC can also be one of the more frustrating to deploy. Many schools have used UDM to deploy it, only to find it installs on some devices but not on others, even after waiting days. All UDM deployments are completely silent and run in the background, even while a user is logged on. There are no prompts for the user and there is no indication of success, apart from the desired program suddenly appearing on the target devices, ready for use. But because it is silent, there is also no notification of a failed installation. So it's important to understand what could cause a failed install. Acrobat DC wants to install plugins, so it will fail if any of the following are open and in use:
- Any Microsoft Office program (eg. Word, Powerpoint, Excel)
- Any Internet browser (eg. Chrome, Edge, Internet Explorer, FIrefox)
Once the install has failed, it may or may not retry the install at a later time, and this is dependent on the reason it failed. If Acrobat DC is not there within two days, it's safe to assume it failed. UDM installs are usually successful when the device is turned on, but not logged on. Or, logged on, but not being used, with Office and browsers closed. For this reason, it's best to negotiate when to deploy it with each user.