Summary
In the Computers tab of the DSM console, you noticed that Base Policy is assigned to ESX/ESXi hosts under the Policy column. As shown by the screenshot below, Base Policy appears instead of N/A.
This should not be the case because security profiles or policies cannot be assigned directly to ESX/ESXi hosts.
Details
The problem may be caused by a UI issue which existed in the previous version. This UI issue was inherited when you upgraded to Deep Security 9.0. However, this does not have any effect on your product.
To resolve the issue:
- vMotion all virtual machines (VMs) from the affected ESX/ESXi host to another ESX/ESXi host.
- Remove the affected ESX/ESXi host from vCenter.
- Synchronize vCenter and DSM
- Go to the DSM console.
- Click Computers tab.
- Right-click vCenter and then click Synchronize Now.
- Add the ESX/ESXi host back to vCenter.
- Repeat Step 3.
The DSM console will now show N/A under the Policy column.
