Yes, that is correct. When you install the Wazuh agent on an endpoint, if you do not specify the agent name during installation, it will use the hostname of the endpoint as the agent name. When using GPO for agent deployment, it automatically takes the hostname of the endpoint, which helps avoid agent duplication issues. You can refer to the Wazuh blog for guidance on deploying the Wazuh agent using GPO.
Additionally, you can refer to the Wazuh agent installation documentation for manually deploying the agent.
Note: - To change the agent name, you need to reinstall the agent, as the name is assigned only during the agent enrollment process.
Hi,
For configuring Wazuh agents remotely, I recommend using the Wazuh centralized agent configuration method to update the ossec.conf file on endpoints remotely.
In Wazuh, you can configure the agents remotely using centralized agent configuration. To do this, you first need to create an agent group in the Wazuh dashboard and apply your custom agent configuration to that group.
For creating an agent group, you can refer to the Wazuh agent grouping documentation.
After creating the agent group, refer to the Wazuh centralized agent configuration documentation for configuring the Wazuh agents remotely.
Note: When setting up remote commands in the shared agent configuration, you must enable remote commands for agent Modules. This is enabled by adding the following line to the /var/ossec/etc/local_internal_options.conf file on the agent: