Hello Seshu,
I appreciate your reply.
This actually isn't a Windows limitation. Meraki is the only MDM that I know of with an agent that behaves this way. The development team should be able to fix this.
I've had cases with support with no success.
Do you have any examples of scripts?
Here's one that I have that works locally, but I haven't found a way yet to run on VPN clients because they don't have a normal startup or shutdown that triggers execution.
# Adds the new Meraki VPN connections.
Add-VpnConnection -Name "Connection Name Here" -ServerAddress "VPN Address Here" -AllUserConnection -TunnelType L2tp -L2tpPsk "Share Secret Here" -AuthenticationMethod PAP, CHAP, MSChapv2 -EncryptionLevel Required -Force -WA SilentlyContinue -RememberCredential