Meraki seems to have two minds when it comes to the Cloud Archive licenses; on the one hand, the total quantity of them and the number being used shows up on the Meraki dashboard along with the co-term date of that dashboard (in this scenario we're on a co-term dashboard model). Yet the licenses themselves have individual expiry dates that can vary between licenses depending on when they were first assigned to a camera. The Meraki documentation specifically says that the licenses are treated as per-device even when on a co-term dashboard (https://documentation.meraki.com/MV/Initial_Configuration/MV_Cloud_Archive😞
I have a customer whose dashboard expires in November 2023, but they have 7 x Cloud Archive licenses show an expiry of October 2023. They need to get 7 new Cloud Archive licenses a month before the co-term dashboard expires.
But this same customer has 10 x Cloud Archive licenses that don't expire until 2025. Presumably, we wouldn't need to purchase these until closer to their expiry date.
But in trying to come up with an order that will renew/add 7 new Cloud Archive licenses to replace the ones they need to update in October, the system resets the quantity of Cloud Archive licenses shown in the co-term license count, even though the CA licenses aren't co-term (or are they? Why does the documentation say they're not? Why does the Cloud Archive have individual expiry dates depending on their term and when they're assigned, if they're tied to the co-term date of the dashboard).
Meraki support is saying that they need to renew 17 x Cloud Archive licenses when they do a co-term renewal to keep the quantity of licenses in the dashboard the same as what they're using; but if the licenses are treated as per-device with their own expiry, why are they tied to the co-term dashboard and license count at all -- adding new devices to the dashboard doesn't affect the CA licenses' expiry date because they're not co-termed with the rest of the device licensing.
Does anyone know the answer to this?
