- Q1: What is the Trend Vision One Agent platform compatibility?
To check platform compatibility, refer to Trend Vision One Endpoint Security agent requirements.
- Q2: Why are Cloud One / Deep Security agents not seen in Endpoint Inventory App?
Cloud One / Deep Security agents do appear in Endpoint Inventory if the managing Deep Security Manager or Cloud One management console is connected to Trend Vision One. Installing Trend Micro Endpoint Basecamp (a.k.a. XBC) is no longer required, though highly recommended.
- Q3: Is there an MSI installer for Endpoint Basecamp?
Trend Vision One does not provide an MSI installer for now but this will be an upcoming feature.
- Q4: How do you configure proxy for Endpoint Basecamp?
Proxy settings are located in Endpoint Inventory under "Global Settings". See more details here: https://docs.trendmicro.com/en-us/documentation/article/trend-vision-one-global-settings-endpoint-inventory
It is possible to use the deployment script or CLI to force the installer to use a proxy, but the agent will only use that proxy for installation. The agent will pull the “Run-Time” proxy settings from Endpoint Inventory. Deployment instructions can be found in the deployment guides.
- Q5: How do you check the proxy Endpoint Basecamp currently being used?
You can view this information in the Endpoint Inventory table columns.
- Q6: How do you reset the proxy setting which is set from the Endpoint Basecamp command line?
Proxy settings are handled by Global Settings in Endpoint Inventory.
The commands below can still be used, but the agent will pull the proxy settings from Trend Vision One Endpoint Security.
Use the command line on different platform with parameter to remove the proxy setting which is set from the command line before.
- For Windows
EndpointBasecamp.exe /proxy_server_port :
- For Linux
$ ./tmxbc config set --proxyURL ""
- Q7: What are the details on OS support policy for Trend Micro Vision One agent?
Refer to the KB article, Trend Micro Vision One agent Operation System (OS) support policy.
- Q8: Will XBC Agent support Solaris OS?
No, but customer can connect a Cloud One / Deep Security agent to their Server & Workload Protection Manager; or connect their Deep Security Manager to Trend Vision One to view Solaris deployments in Trend Vision One Endpoint Security.
- Q9: How do I know if XBC version is up to date?
Customer can view what agent version is deployed to an endpoint in Endpoint Inventory. Version details and manage update policies can be found in Version Control Policies.
- Q10: What common error codes are found in XBC agent log?
Checkpoints:
If the problems mentioned above are resolved, trigger the Endpoint Basecamp agent downloaded from Endpoint Inventory console again to get the missing endpoint to appear.
- "Error 10000" indicates that the endpoint cannot get the correct response from our backend.
Resolution: Make sure the endpoint is able connect to all the FQDN listed in the OLH. - "Error 10001" indicates that the endpoint cannot download the target file.
Resolution: Check the log before 10001 and find the tool download link. Be sure the endpoint is able to download the package via the browser. - "Error 10005" indicates that the endpoint cannot validate the signature of our binary.
Resolution: Download XDR Endpoint Checker tool to inspect and import missing certificates for Trend Micro Vision One agent. - Error "register_device" indicates that the agent got HTTP 401 in the same request and that the system time is shifted.
Resolution: Correct the system time for the endpoint.
- "Error 10000" indicates that the endpoint cannot get the correct response from our backend.
- Q11: How do I handle "Cannot Install - System Compatibility Error"?
- Q12: How do I handle handle "Cannot install - System compatibility error
Installation not initiated. Trend Micro Deep Security Agent self-protection is enabled using an authentication password. Disable the password and try again."
1. Please disable DSA self-protection first on C1 console or via CLI command.
Disable self-protection on C1 console:
To disable self-protection via CLI command( (1: enable, 0: disable)):
- For Windows Platform:
C:\Program Files\Trend Micro\Deep Security Agent\dsa_control --selfprotect=0 -p <password>
- For Linux Platform:
sudo /opt/ds_agent/dsa_control --selfprotect=0 -p <password>
2. Execute V1ES installer again
