nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Update Views for 3rd party packages

FormerIdeaCreator

The WSUS console allows creation of Update Views, which are filtered lists of update packages based on various metadata attributes. There's no such feature in the Patch Manager Software Publishing system, but it would be very helpful for providing custom views of the third party packages. With the packages grouped only by publisher and with catalogs including many older packages, some folders can contain hundreds of packages. This often affects the performance of the console and makes it very difficult to find a specific package or to identify new additions.

I would like to suggest an Update View feature to create "virtual folders" that display specific packages based on metadata including vendor, publish date, publish status, source (SCUP catalog, custom, etc), product, classification, and so forth.

Find more posts tagged with

Status: None

Comments

LGarvin

While I do think there's merit to the ability to create user-defined folders under the Software Publishing node, the datagrids in the existing publisher nodes can be customized by grouping, sorting, and filtering content. I routinely configure the publisher nodes to group by product and sort by Creation Date so the newest package are always at the top of the list. (Be sure to use "Save View Layout" once you've set up your preferred viewstate for that publisher.)

Can you provide one or more specific examples where the existing datagrid capabilities are not meeting the need and a user-defined folder would provide a better experience? (Use cases are a major driving force in feature request evaluations.)

For legacy products you no longer want (e.g. Air v2, Flash for Mozilla or Opera), de-select them from synchronization and delete them from the package list.

I'd be interested in hearing more about the performance issues you're having loading package lists in a publisher node. The largest publisher node (other than HP and Dell) is the Adobe node, with 389 packages (today, not including Air v2 and the legacy Flash categories) and my notebook-based test environment loads that list in 6 seconds. The Mozilla node with 231 packages loads in 3 seconds.