I made acrobat reader a dependency for pro, then stage my pro installs-so they always stay version equal as we have a software that will ALWAYS die if they aren't, and it lets me use the pro machines as my beta test for reader. Then monthly I just swap the msp and update the detection rule.
We have a TON of apps that require adobe and some that require only reader and some that require only pro and so some machines need to coexist with both.įor the last 8 months or so I've been using a PSADT script to install the base msi (only applies on new installs) and then pushes the msp on top of it, then adds our specific reg fixes and such. Historically we used the old 2015 msi as a base install and added the new msp, with a transform, and this has usually worked. I've reengineered our acrobat packages several times. I personally use edge as PDF reader but that is sadly not an option for everyone at the company. So even if we could remove it from 50 % of the users we would still deal with the software for the remaining clients. We are at stage where we seriously consider removing the app from production, but we have a lot of users who have a dependency on some of the features in this software. I was wondering how you deal with the software? Anyone of you had success looking elsewhere for another type of PDF reader like Foxit or similar? So far it seems to be the most stable with PMP but there are still issues. We have had issues with the product for years now and tried patch management through several automated third party patch vendors such as flexera and PatchMyPC. Eventually we find a custom fix to solve it but it takes a lot of effort and time to investigate each time.
Almost every time a new patch for Adobe Acrobat Reader DC has been released and deployed we see some sort of issues with the patches.
0 kommentar(er)
