Two primary considerations come to mind. First, the purpose of a config template is for when all bound sites (devices) will have very similar configs. While you can do local overrides for configs that need to deviate from the template setting not every setting is available for overrides. The list of current available overrides is here. If you require variability per site and it's not an available override then templates would not be right for you. The other main factor is firmware upgrades. Firmware is set at the template level. So, when you perform a firmware upgrade it will apply to all bound networks. It will respect local timezone settings. So, if you set an upgrade for say 1am it will occur at 1am in the local timezone of the network. Just something to be aware of as this may sway you to go one way or another. With that said I've had great success with templates and find them helpful in large deployments. But sometimes unique requirements drive a customer to not use templates and instead manage at scale with API's or a UI+API overlay solution like Boundless. Interested in hearing from other users here.
... View more