Video Screencast Help

Manage Software, Software Updates

Created: 20 Nov 2012 • Updated: 20 Nov 2012 | 1 comment
This issue has been solved. See solution.

There are a lot of guides and other information out there on how to create Software Resources but little to none on how to create Software Updates. We don't use Patch Management, so I am looking to use this feature along with managed software delivery policies to deploy point release patches to non-microsoft software in msp format (patching Adobe Acrobat X from 10.1 to 10.1.4 for instance). What should one include in the package for the update? The full msi and associated software install and the msp file or just the msp? How should the detection rule work? Any help or pointers to existing online resources I may have missed would be appreciated.

Comments 1 CommentJump to latest comment

andykn101's picture

You'd do it the same way as any other piece of software, except when you import the 10.1.4 msp remember to assign it the "Update" Software type, not "Software Release".

"install" Command Line Type, msiexec /p...

Detection rule would be something along the lines of acrobat.exe=10.1.4 or maybe look in the add/remove section of the registry.

Applicability rule would be something like acrobat.exe >= 10.1.0 AND acrobat.exe <10.1.4.

Under Associations, Updates Adobe Acrobat 10.1 & 10.2 etc.

Then create a Policy to apply it.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.