Best Practices Question
Patch Detect Returns Unwanted Patches
I am starting to look into using our K1000 to apply patches to our machines on a schedule. I have been using patching for months now, but only for new computers as a one-and-done type thing. I just did a patch detect on my computer and don't quite understand the results. I see a few things such as a firefox update and a recommended Windows update that should not be in the list.
My detect schedule is set to only detect on the same patch labels that we use for our subscription settings. None of these labels include installers and every label specifies that the patch be of a critical impact. My computer does not have Firefox installed so I don't know why the detect thinks that I need that on my PC. It was my understanding that if you don't have the checkbox for application installers checked in the subscription settings, you would only get updates to applications already installed on that machine.
I also don't understand why the detect is showing me disabled patches. It thinks that I need the recommended Windows patch even though every one of my patch labels specifies that the patch must be critical. I even went to my patch listing and can't find that patch at all. When I go to the patch from the detect results I see a message saying that the patch is disabled because it doesn't match any patch subscription settings.
Does anyone know why these things are showing up during the detect? Would they actually be applied if I did a deploy? Any help here would be great!
Community Chosen Answer
There is a glitch in the latest patch released by Mozilla. If you dont have the program installed instead of patching it then it installs Firefox. The workaround is to place in a lable that excludes Mozilla if it isnt installed.