We're planning to move to a new RADIUS service for our corporate SSID.  On the Meraki side, this only involves updating the Radius Server list / PSKs on that one SSID.  My company wants to perform this update in batches, since we have over 1K locations.  All locations are on the same combined configuration template.    Originally, the plan was to clone the configuration template, update the Radius Servers on the new Template, then move networks to the new configuration template in batches.  The problem is, moving a network to a different configuration template unbinds the switch profile, and removes all network-level overrides. That last part is a non-starter, since a good portion of our switches have at least one switch port override for one reason or another, and all of that would get removed. Also, there doesn't seem to be a way to audit overrides at an ORG level, even if we wanted to commit to re-configuring a huge number of overrides.  So my only options seem to be: A: Update the existing template, which would update the entire org at once.  B: Split the combined networks into separate Switching and Wireless templates, cloning the Wireless template, then move networks to the new wireless template. I'm hesitant about option B, not sure of the risks there.   What's the best way to go about this, to update an ORG-wide SSID in batches, while preserving network-level overrides? ... View more