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

Create a technical support case if you need further support.

Known issues in Deep Security 8.0

    • Updated:
    • 1 Mar 2016
    • Product/Version:
    • Deep Security 8.0
    • Platform:
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary

This article enumerates the known issues that you may encounter when installing the GM build of Deep Security 8.0.

Details
Public

Here are the known issues:

  1. Deep Security Manager cannot be installed on RHEL 5.4 on Xen x64.
  2. After a silent uninstallation of the Deep Security Manager from Linux with the Derby database, the AU, DSM, and Plugins folder will still be left.
  3. In certain cases on RHEL 6.x, attempting to use "dsm_s stop" to stop the Deep Security Manager services generates the error message: "Timeout. Daemon did not shutdown yet."

    This happens because dsm_s is based off of install4j whose timeout value is 15 seconds and cannot be changed. The Deep Security Manager may take longer to shut down. To ensure that the service is properly shut down, run the following command:

    ps –ef | grep DSMService

  4. When running nginx.exe, errors like “logs/error.log and conf/nginx.conf not found” appear in the Windows Event Logs. To prevent these errors, use this command:

    nginx -p "<DSADIR>\relay\" -c "<DSADIR>\relay\nginx.conf" -s stop

  5. If Deep Security Agent is installed on a machine, and Deep Security Manager with co-located Deep Security Relay is installed on the same machine, the Deep Security Relay’s folder will be that of the Agent's.
  6. When deploying and activating Deep Security Virtual Appliance for the first time, you may encounter this error message: “The product has passed invalid parameters to ActiveUpdate. Please contact your Trend Micro technical support provider.”

    If this happened, perform a "Clear errors/warnings" on the affected host and then do another component update. This will be fixed in a later update to Deep Security 8.0.

  7. Unable to download quarantined files from the Deep Security Manager web console using IE 9.
  8. There are instances when, after installing or upgrading the Deep Security Manager, the web console for the DSM cannot be accessed. To resolve this, restart the Deep Security Manager service.
  9. A fresh install of Deep Security Manager with Deep Security Relay can cause duplicate host entries when vCenter is added to the DSM. This happens when the DSM is on a VMware image on an ESX server and ESX is in a vCenter managed by DSM.

    An example of this is when a customer has DSM on one ESX in a vCenter and then wants to protect another ESX in the same vCenter. When the vCenter is imported, the DSM machine is added and you get a duplicate entry.

  10. If the component version on the Deep Security Agent is newer than the one on the Deep Security Relay updating it, the "Is Latest" field will still be "No". To resolve this, you need to update the Deep Security Relay.
  11. Deep Security Manager only supports the HTTP proxy server type; it does not support SOCKS proxy servers in the current build.
  12. If an ESX with an installed vShield Endpoint driver is removed from its vCenter, DSM will not detect the installed driver if the ESX is later re-added to the vCenter. This will cause any newly DSVA-protected VMs to not have anti-malware enabled. As a workarounds, you need to uninstall and reinstall the driver through the VSM.
  13. To upgrade to Deep Security 8.0 on Windows Vista, you must first install Microsoft Visual C++ Redistributable Package.

    After installing the packages, you need to reboot the machine. Failing to install will result to unsuccessful upgrade. To recover, you can install the package and re-run the installer.

  14. If multiple actions are applied to a machine on the DSM, not all status will display properly. Integrity Monitoring will be prioritized and displayed.
  15. When using Relay Groups, Linux relays will not update correctly if they use Windows Relays as update source. It is recommended that Windows and Linux relays be configured to update only from the Global Update Source or from relays of the same platform.

    *Fixed in Deep Security 8.0 SP1

  16. If you are upgrading from Deep Security Virtual Appliance 7.5 to 8.0 and are intending to use the Notifier, you must change the VMCI setting for the Virtual Appliance from Restricted to Unrestricted.

    To do this:

    1. Shut down the Virtual Appliance after the upgrade.
    2. In vCenter, right-click the image and select Edit Settings.
    3. In the Hardware tab, click the VMCI device and then click Enable VMCI between VMs.
    4. Click OK.
    5. Restart the DSVA.

    *Fixed in Deep Security 8.0 SP1

  17. When using Deep Security with iCRC mode, a DNS server must be available. If a DNS server is unavailable, the anti-malware feature of the Deep Security Virtual Appliance may not function correctly. This will be fixed in the future release of Deep Security.

    *Fixed in Deep Security 8.0 SP1

  18. Under heavy loads, some Windows 2008 Enterprise server installations lose network connection with DSA/DSR installed. This will be fixed in the future release of Deep Security.

    *Fixed in Deep Security 8.0 SP1

  19. Deep Security Manager will silently discard Web Reputation URLs that exceed 2000 characters in the block or allow fields.
  20. RHEL-based Deep Security Relays are unable to update components anymore after applying rollback twice.

    *Fixed in Deep Security 8.0 SP1

  21. Notifier may not start after a remote upgrade of the Deep Security Agent. To resolve this, manually restart the Notifier from the Start Menu or reboot.
  22. The default value for "whois" in Deep Security cannot be resolved properly. If you want to use the "whois" feature, you can modify the URL to sue an appropriate server.
  23. Deep Security Relay nginx access log fails to roll over when the server is under load. The relay still functions normally even with this issue. Only the access logging is disrupted. The only way to recover a new log is by stopping the relay server and then restarting it for a new log to be created.
  24. The DSM cannot correctly show the Windows Server 2012 R2 and Windows 8.1 (x86/x64) version information and OS build number on its console.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1060001
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.


Need More Help?

Create a technical support case if you need further support.