royans

One of the salient features of Chrome OS is its ability to do transparent updates with little or no interaction from the user. This not only ensures the user is always protected, it also improves performance and features over time. If you administer a fleet of chrome devices, I recommend you read  this support  on how to correctly configure this. It goes through all the autoupdate (AU) terminologies and suggests best practices which will help you in long run. How to check if AU is properly working in your network I'll strongly recommend to enable reporting using your admin console. This will allow devices to send its OS version to the reporting engine. Then use the  Admin SDK APIs to generate reports for devices in your domain, grouped by major version. I recommend you write your own scripts, but you can try third party tools like these to understand what the APIs are capable of. If you have lots of different networks, try to generate separate reports for devices in different net

One of the salient features of Chrome OS is its ability to do transparent updates with little or no interaction from the user. This not only ensures the user is always protected, it also improves performance and features over time. https://youtube.googleapis.com/v/QtavfiBOv_g&source=uds If you administer a fleet of chrome devices, I recommend you read  this support  on how to correctly configure this. It goes through all the autoupdate (AU) terminologies and suggests best practices which will help you in long run. How to check if AU is properly working in your network I'll strongly recommend to enable reporting using your admin console. This will allow devices to send its OS version to the reporting engine. Then use the  Admin SDK APIs to generate reports for devices in your domain, grouped by major version. I recommend you write your own scripts, but you can try third party tools like these to understand what the APIs are capable of. If you have lots of different networks, t