Hello.
This situation is quite common where agent IP addresses are under NAT and with a DHCP server where they change constantly. When updating the manager, certain restrictions may be applied that were not previously taken into account. I propose that you manually register agents experiencing these issues through the command line of each agent.
In case the IP address of the laptop changes, the Wazuh agent will be connected to the Wazuh manager, as the manager's IP did not change, but the manager will not recognize the Wazuh agent.
In case you want to handle this manually, I would recommend you to take a look at this [documentation](
https://documentation.wazuh.com/current/development/client-keys.html). To manage this, you have to change the `client.keys` config and specify the new IP address of the Wazuh agent. Then, restart the Wazuh manager executing the `systemctl restart wazuh-manager`
Another alternative is to use the `agent-auth` tool. In the agent, execute the command `/var/ossec/bin/agent-auth -m <manager_IP> -I any [-A <agent_name>]`. It's important to include the 'any' keyword since it allows the agent to change its IP. It might be a good idea to specify a unique name to every agent as well.
Hope it helps. Regards.