Thanks for the feedback. Effectively Installed Patches are always a place to split hairs. Some of our community agree with you as EI patches are something they definitely see as separate as they are typically replaced by newer patches. Some of the community also sees this as valuable audit data. It all comes down to the way you are trying to represent data to stakeholders. That being said here is what I can offer today:
Immediate Solution: Do not include EI patches in your assessment that you plan to report on. If it clouds your reports filter it out of your typical assessment and only run a scan including EI patches quarterly or something along those lines.
Interim Solution: In the next release of Shavlik Protect (9.1) we will be including a number of reporting views that will allow admins to create custom reports through RDL reporting tools, Excel, etc. This would allow you to create customized variations of the reports you are using today to allow for more flexible filtering and customization of reports.
Long Term Solution (roadmap disclaimer) I am always reluctant to share too much about longer term roadmap plans as they are always in flux. We are an agile development team and as we receive feedback from our customers and the market we can change direction to react. That being said, my long term vision today is as follows:
Continue to expand on reporting views to allow for flexible reporting structure (we have a lot of SQL savvy customers who just want the ability to create their own reports with the confidence that upgrade will not break them). Change from in product 'canned' reporting to RDL driven reports that can be imported from the community or custom built reports you have created in house. Have a legacy report pack (again RDL) that you can continue you import and use. Provide a community discussion area for our users to discuss and share their own creations. Drive more common report request in periodic RDL report releases. Ratings would be community based and allow our community to identify the highest priorities and drive priority for our content teams to create new reports.
Shavlik Protect Team, LANDesk