After deploying the Wazuh agent for Windows it is not automatically started

[DProvinciani]

Description

After doing some testing on the Wazuh cluster and agents deployment with Puppet, we identified an issue in Windows agents. Basically, when the agent is deployed, the service is not started and the user should start it manually.

In addition, the service was in disabled state so, we had to manually set the service as enabled to then start it.

[okynos]

Hello!

After test the 4.2.6 version with a simple manifest

node "win-60e1afm9cn4.home" {
  class { 'wazuh::agent':
    wazuh_register_endpoint => "xxx.xxx.xxx.xxx",
    wazuh_reporting_endpoint => "xxx.xxx.xxx.xxx"
  }
}

We can conclude that there is some setting that perform the service to not start. An specific variable that changes such behaviour is manage_client_keys https://github.com/wazuh/wazuh-puppet/blob/4.3/manifests/agent.pp#L485
This variable manage the daemon start or not in addition with the agent registration through the manager. So if you used such variable or changed its value it is an expected behaviour.

We have tested the default procedure with service started and running as a normal installation.
4.2.6 started and working

4.3.0 started and working

In another part of the test we have detected some syntax error that we will describe here #473