Migrating ACC agents from an old MID Server to a new one without reconfiguring/redeploying packages?

[Howard6]

We have built a new MID server because the old one was on an older Windows Server version than our new standard.  We have migrated schedule jobs to the new server (Horizonal Discovery, LDAP queries etc) but all the ACC agents still connect to the old MID Server.  I know we could just repackage the ACC agent for Windows, Linux, and Mac but I was hoping that this can be done from the server by telling the agents to change which MID server to use. Obviously we would still need to update the packages for new devices, but it would save us from having to redeploy the existing agents.  

Is it even possible to do it from the instance instead of deploying newly configured packages?

[Severin Launiau · Accepted solution]

@Howard6: are the agents still connecting successfully to the legacy MID? If so, you can enable the Auto MID Selection if it isn't already, add the new MID + MID web server, wait for the agents to pull the new list of active MIDs (or execute the scheduled job that normally runs every 12 hours) and retire the old MID once all your agents have refreshed their list.