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

Create a technical support case if you need further support.

The pre-boot OS is unable to connect to the Active Directory (AD) server in SecureCloud

    • Updated:
    • 31 Mar 2015
    • Product/Version:
    • SecureCloud as a Service 3.7
    • SecureCloud On-Premise 3.7
    • Platform:
    • CentOS 5.6 32-bit
    • CentOS 5.6 64-bit
    • CentOS 5.7 32-bit
    • CentOS 5.7 64-bit
    • CentOS 5.8 32-bit
    • CentOS 5.8 64-bit
    • CentOS 6 32-bit
    • CentOS 6.1 32-bit
    • CentOS 6.1 64-bit
    • CentOS 6.2 32-bit
    • CentOS 6.2 64-bit
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - Red Hat RHEL 5 64-bit
    • Linux - Red Hat RHEL 5.6 32-bit
    • Linux - Red Hat RHEL 5.6 64-bit
    • Linux - Red Hat RHEL 5.7 32-bit
    • Linux - Red Hat RHEL 5.7 64-bit
    • Linux - Red Hat RHEL 5.8 32-bit
    • Linux - Red Hat RHEL 5.8 64-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - Red Hat RHEL 6 64-bit
    • Linux - Red Hat RHEL 6.1 32-bit
    • Linux - Red Hat RHEL 6.1 64-bit
    • Linux - Red Hat RHEL 6.2 32-bit
    • Linux - Red Hat RHEL 6.2 64-bit
    • Linux - SuSE 11
    • Linux - SuSE 11 64-bit
Summary

In computers with encrypted boot devices, the pre-boot OS is unable to connect to the Active Directory (AD) server. The pre-boot OS does not use the system “hosts” file.

If you connect to the Key Management Server (KMS) through AD, the pre-boot OS may be unable to request the device key. In this case, the operating system will be unable to start.

Details
Public
 
The workaround needs to be applied before you encrypt the boot device.

To resolve the issue:

  1. Create a hosts file that contains IP mappings. Format the hosts file as follows for each IP address mapping:

    10.1.123.123 ms.sample.securecloud.com

    SecureCloud supports up to 8 IPv4 and 8 IPv6 address mappings.

  2. Move the hosts file to the SecureCloud Agent "hosts" folder:

    Linux: /var/lib/securecloud/hosts
    Windows 32-bit: C:\Program Files\Trend Micro\SecureCloud\Agent\hosts
    Windows 64-bit: C:\Program Files(x86)\Trend Micro\SecureCloud\Agent\hosts

  3. Restart the SecureCloud Service so that the settings will be synced to the pre-boot OS.

    If the host mapping is not applied before pre-boot OS is started, it will fail to request key and need to setup the host mapping manually on console or using recovery tool. If this issue occurs, set up the IP address mapping manually on the VMware pre-boot console or by using the recovery tool.

Premium
Internal
Rating:
Category:
Configure
Solution Id:
1107774
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.