Content Views

Latest response

We are in the process of migrating from our current 6.7 Satellite to a new 6.12 version. We've not been in the habit of using content views effectively. Monthly security patching cycles, etc. I'm looking for some ideas on how to craft our new servers content views to account for the RHEL servers we are migrating and then publishing security errata going forward.

I.e. how would I publish a content view that would take into account a RHEL 8.4 server being migrated, but I don't want to upgrade it past 8.4, but want it to see security errata going forward. If that makes any sense.

Responses