Tools that "silently install" patches often require the same amount of work that I'd put into writing a script to install the patch anyway. Tools that do "snapshotting" aren't actually capturing the logic in an installer, and could do the wrong thing under circumstances different than when the snapshot was taken. Patch management tools that claim to automate the patching process have always given me a bit of pause. I've never used a third-party patch management tool, so I can't comment. I disable the updater as a transform to the MSI for Adobe Reader. Users don't have "Administrator" rights on their computers and can't install any updates themselves anyway. I need to be able to centrally control the deployment of updates such that I can test the update prior to deployment.
Having the client computers download patches themselves via the built-in updater functionality in Adobe Reader is useless to me. (If you've got the money to pony-up for Microsoft's System Center Configuration Manager, you can use the built-in System Center Update Publisher to deploy these types of updates.) If they do go to EXE-based updates, I'll write scripts to deploy them silently via computer startup scripts.
(Hopefully they'll stick to a Windows Installer based patching regime from here on out. If Adobe decides to start distributing EXE-based patches, then I've got a problem and have to begin writing scripts. This recent Adobe Reader patch (9.1.2) is MSP-based, so I'm able to deploy it in my usual manner. I don't particularly like doing things this way, but it's the least labor-intensive method I can see.
I've been applying MSP-based patches to my Adobe Reader installation points and then instructing client computers to reinstall via the "Redeploy." functionality in Group Policy. Relevance 4 exists regapp "acrobat.exe" whose (version of it = "15.0.0" AND it < "15.006.I install Adobe Reader via Group Policy and software assignment. Relevance 3 (exists key "HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\2015" of it) of registry
The items I modified were the files to the classic updates and the following relevance: (For update, I'm updating and testing the update) I modified some parts of your fixlet and was able to detect Adobe DC Pro and Standard (Classic) and apply the classic updates, and it's been applying to both.ĭo you produce a fixlet for the 'classic' version or would you want me to upload the one that I modified while giving you credit cdh? Thanks for the comments - and though I was thinking I was going to be able to test it, but I found that my clients are running the 'classic' version of Acrobat Standard, purchased through the Adobe licensing site.
0 kommentar(er)
