Summary
In certain circumstances, a computer joined to a Windows domain is unable to start after you enable boot volume encryption.
Details
This issue occurs when the SecureCloud Agent connects to the on-premise SecureCloud server that has an AD self-signed SSL certificate. In this case, the SecureCloud Agent may not be able to validate that particular SSL certificate.
Before you enable boot volume encryption do the following:
- After configuring and registering the agent, stop the setup wizard and SecureCloud Agent service.
- Go to the agent installation path and open config.xml. The default installation path of SecureCloud agent:
- In 64-bit Windows computer: %programfiles(x86)%\Trend Micro\SecureCloud\Agent\
- In 32-bit Windows computer: %programfiles%\Trend Micro\SecureCloud\Agent\
- Change the value of ignore_ssl_error to:
ignore_ssl_error=True
- Start the SecureCloud Agent service and enable boot volume encryption normally.
If you already enabled boot volume encryption, contact Technical Support to resolve the issue.