Disclaimer: This information is posted as-is and the content should be referenced at your own risk
Sophos Chromebook Security can be deployed using Sophos Central or Google G Suite. This is an overview of the steps involved. For further information about Sophos Chromebook Security please the Sophos Mobile admin guide at docs.sophos.com
Deployment via Sophos Central
Deployment via G Suite
Have an idea or suggestion regarding our Documentation, Knowledgebase, or Videos? Please visit our User Assistance forum on the Community to share your feedback! community.sophos.com/.../user-assistance-feedback
Yes, the Chromebook Security feature requires the Mobile Advanced or Intercept X for Mobile license. Therefore it will consume one of these licenses.
Following this Article, question of mine is after the chromebook appears in device list, it looks like it's using the Mobile Advanced license. Is this always true? For example, I was aiming to get the chromebook to use Mobile standard license but haven't been able to find an option that differentiates these two licenses mentioned in the License Matrix.
So I created this connection via API key a month ago and upon enrollment the force install of the SOPHOS app was working perfectly. Fast forward a month later to now, and new devices that I am enrolling are no longer automatically getting the force install. Any thoughts? I am unable to see the chrome OS gsuite connection in SOPHOS anymore for some reason.
You may re-validate your current configuration for auto-enrolment you can refer to this documentation and let us know.
Morning Glen! Thank you for the response. So I went ahead and created a new API type key and confirmed all of the settings were correct. I updated the new key in the app installation policy on the google admin side, but I am not sure if the devices will still get the install if they have already been enrolled while the policy was potentially not working at the time. Is there a way to manually push out the install if this is the case?