There will be a change to Non-Critical baseline content on VMware Update Manager starting vSphere 7.0 Update 3q, async drivers will not be added automatically to the Non-Critical baseline.
Existing vSphere 7.x Customers (prior to 7.0 U3q) using non-critical baselines will have all the latest async drivers updated automatically in their environment. However, starting vSphere 7.0 Update 3q, Customers need to explicitly pick and choose the async driver updates that are needed. This behaviour is similar to 8.x versions.
VMware started hosting partner content (async drivers) to fulfil vLCM requirements in vSphere 7.0. These content were also pulled into system generated (predefined) baselines, especially Non-Critical baseline. In vSphere 7.0 various issues were observed during the remediation of such baseline where in wrong obsoletions, invalidations and re-validations were observed during the compliance check of this baseline. As a result, the compliance status of Non-critical baseline have been very inconsistent based on the host state. Recent updates to 3rd party/async drivers into VMware online portal lead to potential patching issue in multiple environments.
Create Custom Baselines with the non-critical async components as per the requirement. However, VMware recommends NOT to create a baseline as similar to earlier Non-Critical baselines (that includes all async drivers) to avoid any inconsistent state.
Steps to create Custom Baseline:
Refer the Document for more details on creating Custom baseline.