@TonySmith when you enter the code there is a checkbox to trust this device for 30 days.  If you click that it is a lot easier ... View more

It gets worse, logging today I had to deal with this as well ... ... View more

There's one exception to this rule, that I'm aware of and it relates just to the original virtual MX 'devices'  (VMX100 in Azure, AWS etc.)   The licences for these are, in effect, also the devices - and you can no longer buy them (they are End of Sale, replaced by more capable and flexible VMX-S/M/L).   When your co-termination date arrives, therefore, you cannot include them in a Dashboard renewal.   If you do just renew - even if you include (say) a VMX-M (functionally equivalent, scale-wise, to VMX100) - your Dashboard will show:    VMX100   License limit 0   Current device count 1 (or more) and you will be non-compliant, licensing-wise - and thus, into your 30-day grace period.   If you have VMX100s, you need to plan to deploy new VMXs (small, medium or large, cloud-platform dependent) and a migration of remote peers from one to the other, in advance of your co-term renewal. ... View more

Meraki have explicitly told me that this latest three year licence is 1095 days. "The new date has been calculated 1095 days from March 11 2021 (start date of new license)" ... View more

That's confirmed from Meraki.  Their suggestion is to open up the home network for access from the Internet, and make the connection that way.  That's not really practical. The only sensible solution seems to be to a connection from the home router to the LAN side of the Z1, and static routes pointing that way.  ... View more