1 of 1 people found this helpful
1 - shavlik has a list of the non-OS/Microsoft applications they patch. when the docs maintenance is done we can find the link to it. eg firefox, office (terminal servers for example), sharepoint, etc. they get patched just like the os patches - catalog, patching job, deploy jobs.
2 - asset core = ?
3 - sure. i mean, why not ? it's automated. how else would you do it ?
1. Can application patching be automated in the same way that OS patching can? Surely there are a ton of considerations around applying a patch to, say sharepoint, that rule out an automated update? If not, fine.. we can just pull out the list we see in Shavlik and say we patch these applications on Windows.
2. Just had an update on this: Asset core can pull in from Shavlik but not from the Unix vendors, which kind of rules that option out.
3. Ok. I usually highlight the things we can do around the patch (start/stop services, etc) but worry about the additional effort. Customer has two WebSphere servers.. would they want to create a package in BSA each time a new patch is released, etc?
1 - yes, if it's part of the shavlik meta. it will be a 'filter' option when you create the catalog and work just like the windows patching works. note this is only true for windows. for unix it needs to be in the OS repository or you must create a custom repo and the software has to be registered in the OS'es package database. meaning bsa will not automatically detected and patch a custom-compiled version of apache w/ the 'patching' functionality.
3 - yes - get the silent install/upgrade instructions for websphere and create a package and job to deploy. if you want to get fancy you can use a component template to detect websphere, and the version then push the update as remediation for the downlevel version.
Thanks as always Bill.
I had no idea we could create a custom repo. Good to know.