Chrome Enterprise yearly licensing difficult to coordinate in multi-office environment
Reported by
mlaga...@yelp.com,
Sep 14
|
|||
Issue descriptionVersion of Google Chrome (Wrench-> About Google Chrome): N/A Version of MSI (if applicable): N/A Using group policy settings? No We are planning on rapidly expanding our Chrome fleet and it will be difficult/unnecessarily expensive to buy enough of a license buffer to not have to worry about running into negative license counts. Currently we are ordering devices and yearly licenses 1:1, but this does not account for older systems being cycled out and inflating our license total. We have logistics teams at multiple offices retiring/ordering devices independent of each other. Having them need to coordinate on license counts would be too great a burden as we scale up this platform. Feature Requests, by order of preference: 1) A mechanism for automatic license purchasing with our designated reseller when count runs low 2) API access to Chrome license counts which would allow for us to build automation for this purpose 3) Email admin contact when license counts run low
,
Sep 19
Yes, great feedback thank you. +Lawrence, do we have any plans for any of these things?
,
Sep 20
LP should address a lot of this. But outside of that, I think something closer to the flex license model approach taken by G Suite might help the rapid expansion use case. We definitely have some of these pain points in our minds as we plan for future ideas around licensing. We are tracking some of this internally, but we very much appreciate the feedback.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by atwilson@chromium.org
, Sep 19