![]() I've set the detection method to look for the latest version number, but I don't think this is a detection based problem, Intune tends to be very clear when that's the case. I'm not really sure where to go with this one. That error code keeps bringing me back to articles around Windows Update failures, so not really much help. The problem is, Intune is reporting that the install failed with a "Fatal error during installation (0x80070643)" If the package fails on Windows 8.1 or earlier, this might be due to the installation of kb2919355 (which is a dependency of this package) if your system is not. The installer updates the old version and, at some point during the process, updates itself to the very latest version. The new customised version is actually two major versions out of date (why? because if I use the latest version I can't test the auto-update feature immediately). Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. I packaged the MSI and all the associated files as a Win32 App, set it up in Intune with the transformation files referenced in the installer string and.it works great. I don't believe that current deployment enables auto update. We already have a version of Reader installed from the end of last year. One of the flags I ticked was to allow the app to update itself. So I used the Adobe Customisation tool to create a deployment of Adobe Reader DC (the free one).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |