![]() ![]() Given the extreme frequency and perceived lack of changes (to your average end user), this anecdotally seems to be what most people do. In that case, the placement of the 'OK' button implies that it is the default action, meaning most users will just ignore the update. Or, alternatively, 'OK' may simply just close the dialog without taking any action, as that is common in informational popups in many pieces of software. The two buttons 'OK' and 'Download' are implied to have the same effect, indicating the user has no real choice. Other notable examples of companies who use update managers include Google and Sun/ Oracle, with the latter being also mentioned in the title text. In fact, the general necessity of such update managers has often been questioned, as they require the user to "download software in order to download other software". Would you like to update the Adobe Updater now? The Adobe Updater must update itself before it can check for There is an actual message that a specific version of these updaters display: In this case, the comic is saying that you must update the program before it can actually check for updates, something it already seems to be doing. The frequency of software changes (and changes in the way Adobe allows users to download new software) could result in confused users. In addition, these updates are downloaded automatically by default, but the operating system might install them only if a user allows it to. These software increments might either be technical (to fix compatibility or security issues), or they might add new features that would go unnoticed. The comic makes fun of Adobe Systems software that delivers new versions of Adobe products to users' computers, such as Adobe Updater (which replaced Adobe Update Manager) and Adobe Download Manager (which replaced Akamai). This comic was probably a reaction to the installation service Ninite removing Adobe Flash Player from their free version the previous day. Task using Windows Task Scheduler: "%CommonProgramFiles%\Adobe\Updater6\Adobe_Updater.Title text: ALERT: Some pending mandatory software updates require version 21.1.2 of the Oracle/Sun Java(tm) JDK(tm) Update Manager Runtime Environment Meta-Updater, which is not available for your platform. There are two sections which could be interesting for you. This article was very useful to me in deploying Adobe Acrobat Reader: As such, I'm dubious of the effectiveness and reliablity of "patch management" tools over using software assignment, "Redeploy.", and hand-written scripts to deploy patches. 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. I install Adobe Reader via Group Policy and software assignment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |