No, I created an all-in-one installer (security product, agent, certificate, server address, port).
The software has been updated but the agents still tries to connect to the non-existing local ESET PROTECT instead of our MSP console.
The correct server and port are configured in the all-in-one installer. Seems like the existing agent on the remote PCs was updated but the server address and port were not overwritten.