We have two machines that are currently included in our patching Label, however ,there is a specific patch/update from Microsoft KB2698365 that prevents these machines from installing a program that is needed

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



If it's in your label then it will push. You can create a manual label for those two then create a new smart label with something like this.

Label Names = Orginal Smart Label Name

AND Label Names != Manual Label Name

Then use this new smart label for your patch schedules.

Answered 09/04/2012 by: dugullett
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity



You could also create a custom patch schedule that would include just those two machines and use the Rollback function to uninstall it from the computers. Just be sure to run the rollback schedule after the patching schedule and it should always remove the patch after it is installed.

If the patch can be reinstalled after the application is installed then I would probably just uninstall the patch manually, install the program and then let KACE reinstall the patch. If the patch is preventing the application from running then removing it after patching every time is a solution.

Answered 09/04/2012 by: chucksteel
Red Belt

Please log in to comment

If you're looking for a long term solution and this patch should never, at any future point be installed, then I would create some new smart labels.

A new label for all workstations, minus the names of the two you mention. Point your current patching schedules at this new smart label.

A new label for patches. Duplicate the current patch labels you're using and exclude KB2698365.

Create a new patch schedule. Point it at both of your special case workstations, and add the new patch labels you created.

This way, they are getting all other patches, but will never get KB2698365

Answered 09/06/2012 by: andibogard
Blue Belt

Please log in to comment

Thanks to the responders!!! It appears that Microsoft got infront of this issue fast enough to offer a fix to the patch LOL!!! Great suggestions, I am sure I will have to revisit this when another patch breaks something.

Answered 09/13/2012 by: Thundarr72
Senior Yellow Belt

Please log in to comment

What deployment tool are you using?

Answered 09/04/2012 by: jagadeish
Red Belt

Please log in to comment