Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Deep Security Manager (DSM) console displays "Anti-Malware: Not Capable" or "Anti-Malware Ready: No" status

    • Updated:
    • 29 Jun 2017
    • Product/Version:
    • Deep Security 10.0
    • Deep Security 9.0
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • Windows 2003 Enterprise Server
    • Windows 2008 Enterprise Server
Summary

Users have installed the vShield Endpoint driver, prepared the ESX host, deployed Deep Security Virtual Appliance (DSVA) and activated it successfully. However, the DSM console shows the status of the ESX host as "Anti-Malware Ready: No" and the status of the VMs as "Anti-Malware: Not Capable".

Server0.log shows the following exception:

Mar 9, 2011 11:13:08 AM com.thirdbrigade.manager.core.virtualization.vmware.VSMRequest parseVSMError  INFO: Parsing VSM error for https://vcenter-hostname.dummy-domain.local/:  Mar 9, 2011 11:13:08 AM com.thirdbrigade.manager.core.virtual.VirtualSync syncHost  WARNING: Failed to query for LKM  com.thirdbrigade.manager.core.virtualization.vmware.exceptions.VSMErrorResponseException:  HTTP Response Code: 404

When the DSM queries for the LKM to determine if the ESX is Anti-Malware ready, we are getting an HTTP 404 (Not Found) error. The VSM URL you see "https://vcenter-hostname.dummy-domain.local/" is a vCenter hostname and NOT the vShield Manager hostname. This is justified in debug.xml (vShiel Manager Properties) as shown:

<ServerAddress>vCenter-hostname.dummy-domain.local</ServerAddress>  <VShieldMgrAddress>vCenter-hostname.dummy-domain.local</VShieldMgrAddress>
Details
Public

To resolve this issue, configure the "ServerAddress" to use the vCenter host, and the "vShieldMgrAddress" to use vShield Manager host:

  1. On the Deep Security Manager consoler, right-click the Computer tab and select vCenter.
  2. Click Properties, and then select vShield manager tab.
  3. In the vShield Manager Server, change the Manager Address to:

    vShieldMgr-hostname.dummy-domain.local

  4. Save the changes that you made.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy
Solution Id:
1058399
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.