A duplicate WindowsAgent is created when validating the connectivity for a SQL Server agent.
The WindowsAgents were deployed using the fully qualified host name. When the V188.8.131.52 SQL Server connectivity is validated and the settings are saved a Windows Agent with the short name is often created. This results in two WindowsAgent being deployed to monitor the same host.
When the SQL Server cartridge determines if a WindowsAgent needs to be created it retrieves the host name from the SQL Server instance and then executes nslookup with the host name. If nslookup can't resolve the host name the name retrieved from the SQL Server instance is used. If there is not already a WindowsAgent using the host name, then a new WindowsAgent is created with the name returned by nslookup or the name retrieved from the SQL Server instance.
Many of the SQL Server instances were configured using the short host names. The short host names were not resolving to the fully qualified host names, and sometimes could not be resolved at all using nslook.
Either configure the SQL Server instances to use the desired host name or make sure that the host names configured for the SQL Server instances resolve to the desired host names.