Posted on 01-31-2018 06:27 AM
Im trying to wrap my head around the best way of patching software outside Patch Management, with the familiar testing > production workflow.
Example: I have a static group called Install Endnote x8. Static group is scoped to a policy called Install Endnote x8 that installs Endnote x8 on machines in the group. The policy is set to ongoing and made available in Self Service. Endnote then releases an update. I download the update and import it.
Now, where do I go from here? Do I have a separate policy called for example Endnote x8 - Testing and scope to some test machines? Do I need another separate policy called for example Update to latest - Endnote x8 and scope it to machines to something like "Application Title IS Endnote x8 AND Application Version IS NOT x.x"
Whats the best way to deploy software that includes this testing and vetting approach while still minimizing the manual labour?
Grateful for tips!
Posted on 01-31-2018 06:30 AM
You need an EA that will store the version of endnote then build a smartgroup off of that. For example EndNoteVersion IS NOT 8.xxx where 8.xxx is the latest version, then scope a policy to run that installs the up to date endnote on machines in the out of date smart group and runs a recon.