Video Screencast Help

Managed Software Delivery Policy with Multiple Software Resources for Office 2010 Cumulative Update for December 2012

Created: 08 Feb 2013 • Updated: 08 Feb 2013 | 2 comments
This issue has been solved. See solution.

I am trying to deploy the MS Office 2010 Cumulative Update for December 2012 to a large test group of Windows XP clients using SMP 7.1 Patch Management. The update is comprised of 13 individual hotfixes for the Office 2010 client. I am trying to find a simpler way to do this.

I created 13 individual software resources, one for each EXE. They all share the same applicability rule: Office 2010 is installed (except for Project 2010 which as its own rule). The detection rules vary depending on what version of a certain file is being updated as described in the hotfix details by MS.

What I ended up doing was creating an individual MSD policy for each and every package. It is not the best way to do it but it works.

There is a way to add multiple software resources to a policy. When I test it on a few machines they only get so far as to run the detection/applicability rules for the first 3 - 5 packages and then nothing happens. On some machines it goes farther but never enough to download. There is no download or execution. The detection and applicability rules work fine when the packages are in their own policies and so do the download and execution.

Here is a simplified explanation of what happens, if we had 3 packages instead of 13:

  • Detection check for firstupdate.exe - not detected
  • Applicability check for firstupdate.exe - not detected
  • Detection check for secondupdate.exe - unknown or not started
  • Applicability check for secondupdate.exe - unknown or not started
  • Detection check for thirdupdate.exe - unknown or not started
  • Applicability check for thirdupdate.exe - unknown or not started
  • Download package for firstupdate.exe - unknown or not started
  • Download package for secondupdate.exe - unknown or not started
  • Download package for thirdupdate.exe - unknown or not started
  • Execute install command for firstupdate.exe - unknown or not started
  • Execute install command for secondupdate.exe - unknown or not started
  • Execute install command for thirdupdate.exe - unknown or not started

This update is not in the Patch Remediation Center of the SMP console otherwise it would take 10 minutes to deploy.

Any ideas? Thanks in advance!
 

Comments 2 CommentsJump to latest comment

andykn101's picture

By default, if the Applicability rule of any Software Release in a Policy fails the Policy will stop.

A way round this is to go onto the Results based tab of Advanced options in the Policy for each Software Resource and change On failure from Abort to Continue.

But the proper way to do it is to create each Hotfix as a Software Update, not a Software Release. Go to the Dependencies tab of each and make it Update your Office 2010 Software Release. You shouldn't need an applicability rule, just a Detection rule for each. Then edit your Office 2010 Policy and you should have the option to select the Software Updates. Provided the office 2010 detection rule works you can apply that policy to the original target and it will just apply the updates where office 2010 is already applied.

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.

SOLUTION