A library vCenter certificate is untrusted when NSX Manager tries to add it as a compute manager, so clusters and VMs never appear for security grouping. What should the administrator fix in the install workflow?
Select an answer to reveal the explanation.
Short Explanation
NSX cannot inventory library VMs if it does not trust vCenter's ID badge. The compute-manager add step is where that trust is accepted. Tweaking DFW syntax or Carbon Black cert checks will not make clusters show up.
Full Explanation
Registering vCenter as an NSX-T compute manager is a named preparation step so clusters, VMs, and tags become available for security groups and Distributed Firewall. An untrusted vCenter certificate blocks that registration. The fix is to establish trust in the add-compute-manager workflow. Distributed Firewall IP-only workarounds, Carbon Black sensor certificate settings, and Workspace ONE Access connectors do not register vCenter with NSX Manager.