How to remove disabled patches from "Not Patched"
A little background information about my current situation. When setting up the K1000 during our trial period, the Kace support people had checked the box for "Include Software Installers." I found this to very quickly be a terrible idea and found that Kace was trying to install every single one of these Software Installers. For example, take adobe AIR for example, Kace was trying to install 20 different versions of Adobe AIR alone. I had not realized they had checked that setting and on my first test patch schedule I had an unpleasant surprise.
After disabling Software Installers, the "Not Patched" for these disabled patches are still showing up. It has made troubleshooting or trying to manage actual real failed patches a nightmare. My reports are absolutely flooded and overwhelmed by these patches that were never deployed due to an improper setting during setup. The issue did not start to really show itself until later when trying to set patching reports to determine failed or waiting to be deployed patches.
Here is an example of just one application from a Report on Patches waiting to be Deployed.
4 AIR2.0.2.12610 Adobe AIR 2.0.2.12610 for Windows (Full/Upgrade) (All Languages) 4 1 3 0
5 AIR2.0.3.13070 Adobe AIR 2.0.3.13070 for Windows (Full/Upgrade) (All Languages) 4 1 3 0
6 AIR2.6.0.19120 Adobe AIR 2.6.0.19120 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
7 AIR2.6.0.19140 Adobe AIR 2.6.0.19140 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
8 AIR2.7.0.19480 Adobe AIR 2.7.0.19480 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
9 AIR3.1.0.4880 Adobe AIR 3.1.0.4880 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
10 AIR3.2.0.2070 Adobe AIR 3.2.0.2070 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
11 AIR3.3.0.3670 Adobe AIR 3.3.0.3670 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
12 AIR3.4.0.2540 Adobe AIR 3.4.0.2540 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
13 AirWin3.4.0.2710 Adobe AIR 3.4.0.2710 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
14 AirWin3.5.0.1060 Adobe AIR 3.5.0.1060 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
15 AirWin3.5.0.600 Adobe AIR 3.5.0.600 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
16 AirWin3.5.0.880 Adobe AIR 3.5.0.880 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
17 AirWin3.6.0.5970 Adobe AIR 3.6.0.5970 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
18 AirWin3.6.0.6090 Adobe AIR 3.6.0.6090 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
19 AirWin3.7.0.1530 Adobe AIR 3.7.0.1530 for Windows (Full/Upgrade) (All Languages) 5 0 5 0
20 AirWin3.7.0.1860 Adobe AIR 3.7.0.1860 for Windows (Full/Upgrade) (All Languages) 4 0 4 0
21 AirWin3.7.0.2090 Adobe AIR 3.7.0.2090 for Windows (Full/Upgrade) (All Languages) 7 2 5 0
22 AirWin3.8.0.1430 Adobe AIR 3.8.0.1430 for Windows (Full/Upgrade) (All Languages) 7 2 5 0
23 AirWin3.8.0.870 Adobe AIR 3.8.0.870 for Windows (Full/Upgrade) (All Languages) 7 2 5 0
24 AirWin3.9.0.1210 Adobe AIR 3.9.0.1210 for Windows (Full/Upgrade) (All Languages) 7 2 5 0
25 AirWin3.9.0.1380 Adobe AIR 3.9.0.1380 for Windows (Full/Upgrade) (All Languages) 13 8 5 0
If I run the "Installation Status of each enabled patch" report, these still show up even though they are disabled.
Is there any way to correct this issue?
1 Comment
[ + ] Show comment
-
I was also troubleshooting a replication share recently and I was unpleasantly introduced to a new issue caused by this. These disabled patches are still being downloaded and replicated to all of my replication shares. - gerane 9 years ago
Answers (1)
Please log in to answer
Posted by:
nickbaldwin86
9 years ago
Create and save a "Advanced Search Label"
Each time you go in to review patches just select the search label and apply, it will remove any unwanted items.
Comments:
-
I don't have an issue when viewing patches from there. The disabled patches are properly filtered out there. It is when viewing inventory directly and when running reports. I need to be able to run reports for compliance. Currently, I cannot run a report because they are all overwhelmed by thousands of disabled patches that were accidentally ran and promptly cancelled during the setup process when in the demo phase. I did not realize this issue until later when starting to setup Reporting. - gerane 9 years ago