When manually installing some agents I found that a previous Kaseya installation was present although not active. I downloaded and installed the agent from our kserver from a package created for this customer but the agent continues take the settings from the previous install.

I uninstalled the old agent rebooted AND deleted the Kaseya folder. It still would take settings from the previous agent and point to the wrong server. Any hints on how to deal with this as simply as possible?


Legacy Forum Name: Agent connects to wrong server,
Legacy Posted By Username: JPoz