Yes - changes made in a Template are automatically pushed to all Networks bound to that Template. Bear this in mind, when organizing your Dashboard;   where might you need to test a planned change, in a limited way, before you push that change to all sites...?   There are, however, a number of settings that cannot be locally overridden.   It should become obvious to you what these are, by loooking at 'Configure' on a Network bound to a Template.   https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates#Local_Overrides   What do you need to change, per Network?   Remember there are essentially no limits to the number of Templates you can use.   If something needs to be locally over-ridden for a subset of sites - maybe you need more than one Template?   If Templates are ultimately not flexible enough for you, that's where the Dashboard API comes in, for automating changes at scale. ... View more

Hi @nikmagashi    Indeed you figured it out: Shared secret field: it the shared secret to be configured on Windows VPN Client as well Secret field in Radius section: it the PSK/Secret to configure with Radius client on NPS server   Regarding the IP Address to associate with the Radius Client on NPS Side, this meraki KB is really helpful and explains the different cases https://documentation.meraki.com/MX/Client_VPN/Configuring_RADIUS_Authentication_with_Client_VPN#Add_MX_Security_Appliance_as_RADIUS_clients_on_the_NPS_server   On an intranet, If your MX uses a static route to reach out the NPS Server, you will have to use MX IP of network segment used by this route. If your MX relies on VPN tunnel to reach out NPS, use the MX IP of the highest-numbered VLAN Interface set "in VPN"   I hope it helps ... View more