yes. I spoke to Meraki and they said the only way is to try to use the Interface name (ABC-vpn, company-vpn etc) in powershell when adding the static route in windows. The reason is command line does not take Interface name as valid and the IP address assigned is dynamic (so is the actual Interface number). I am trying that right now and will post the results. thanks
Update: Sure, making a single static route would work just fine for any particular PC (since the interface number value does not change), the problem is when you want to deploy the VPN client to multiple computers (in my case little less than 100). The only way to make a dynamic entry to the IF value (interface) in the route command is to use powershell value 'InterfaceAlias '(Windows 10: New-NetRoute command, still looking into windows 7). Still researching.
c80f0f1006