Please see the user help center for a list of user-specific issues.

Description:

We are currently experiencing an issue with some Chromebooks not reporting their recent activity to the Control Panel. If a device is affected, you’ll notice that within Settings > Chrome OS > Devices, the Last Activity field is blank for an enrolled Chromebook that has been powered on or logged into.

Note: Please ensure that the Chromebook not updating ‘Last Activity’ is enrolled to your domain (at the bottom left corner of the Sign-in page, you should see ‘Managed by ’ after the OS version if the device has been enrolled).

How to resolve:

You’ll want to first ensure that your Chromebook has been updated to at least the most recent stable channel version (which should be Chrome 17 or greater). For detailed instructions on Updating, please see the Check for updates instructions.

If you have confirmed that the Chromebook is enrolled to your domain and has been updated to the current version, but the Last Activity field is still not updating, you’ll need to wipe the device and re-enroll.

If after wiping the Chromebook and re-enrolling you still do not see the Last Activity field update, please contact support through your Enterprise Support Portal.

Report this issue

When you're searching for a Chrome device by serial number, make sure the serial number ends in a number. If the serial number found under the device has a letter at the end, remove this letter and search again.

Report this issue

When users are signing in to their Chrome devices for the first time, they can be blocked from properly applying policies if Require a change of password in the next sign in is set on their account.

To ensure the policies are correctly applied, you should do either of the following:

• Have new users sign in to https://accounts.google.com/ to set their password before using a Chrome device for the first time.

OR


• Instruct your users to sign in to their Google account at https://accounts.google.com/ using guest mode on a Chrome device.

This ensures the user has updated their password as required, and the user policies will be set as expected. Future sign-ins for that user on any Chrome device should work as intended, and your organization's policies in Chrome OS should be enforced on their device.

Report this issue

Description:

Sync error appears on a user's device after updating to version 25 of Chrome.

How to resolve:

Please check if Google Talk has been disabled for the affected user. If it's been disabled, please enable Google Talk to get Chrome Sync working again. We're working on making this dependency more clearly documented in the Admin Control Panel.

Report this issue

Description:
Chrome devices are currently unable to capture a system time update when using a proxy, which prevents the enrollment of the device. To work around this issue, either allow www.google.com traffic to bypass the proxy or use an unrestricted network during device enrollment.

Provide information on your Issue:
We're actively working on this issue and will update this page as soon as a fix has been released.

If you would like to report your experience with this issue, please click the Report button below and submit feedback as follows:

1. Log in to your Chromebook either with a user account or as a Guest.
2. Click the settings icon in the top right (below the battery icon) and select Report an Issue...
3. Choose Network connection from the first pull-down and input the following descriptor in the Tell us what is happening field:
   Google Chrome device can't enroll over proxy connection
4. Please ensure the Send system information box is checked as this ensures a copy of your devices' Wi-Fi logs are sent to our team.

If you would like to get in touch with our Google Enterprise Support team to further discuss your issue, please submit a ticket through your Enterprise Support Portal.

Report this issue

We are investigating a known issue with enrolled Acer C7 Chromebooks when a device-level network policy is set in the Management Console. When an existing user on the device signs in to their device, the network should connect.

If you are experiencing a similar issue on a different managed Chromebook model, please open a support ticket through the Enterprise Support Portal.

Report this issue

Google Chrome Management is now available as a service, and it has been enabled for Google Apps for Business and Education domains that have opted into receiving new services automatically. Users in suborganizations that had user settings applied on Chrome Devices will see these same settings on their browsers when they sign in to Chrome.

If you do not wish to have these settings on some or all of your Chrome users at this time, please use one of the following workarounds.

• Change the user settings back to default for the relevant suborganizations. You can collect a list of what policies are on the Chrome browser by typing about:policy in their Chrome address bar. You can then find the corresponding policy and change it to the default setting in your Admin panel by going to Settings > Chrome > User Settings. Please keep in mind that this will also change the Chrome device settings for the users you specify.

• If you have a subset of users who you do not wish to manage on either Chrome or Chrome Devices, you can move them to a separate suborganization. In the Admin panel, go to Organization & Users > Services and disable Google Chrome Management. The users can then delete and recreate their Chrome profiles. Future policy changes will not affect these users until you re-enable Google Chrome Management and apply settings.

• Chrome policies pushed from the Admin panel can be overridden by Group Policies applied locally to corporate-managed devices. Use this mechanism if you want your user experience on Windows computers to be different than on Chrome Devices.

Report this issue

Some users with Mac OS X 10.7 and later have experienced technical issues connecting to network resources with Chrome for Business 22 and later. More information on this issue can be found at https://code.google.com/p/chromium/issues/detail?id=167140.

Report this issue

Chrome and Chrome devices currently do not support "Chrome Sync" with SAML Single Sign-On (SSO). We have plans to support this with Chrome sometime in the future.

Report this issue

Domains which have Single Sign-On (SSO) enabled and have their users' passwords synced with Google currently can’t sign in to Chrome Sync using Chrome 26 (browser) and later. We are actively working on resolving this issue.

Report this issue

Chrome and Chrome devices currently do not support Chrome Sync with SAML Single Sign-On (SSO). We have plans to support this with Chrome sometime in the future.

Report this issue

Currently, if Google Chrome Sync is disabled for a domain, users may mistakenly see an authentication error ("Sync Error: Sign in again..."), instead of a notice that Chrome Sync has been disabled. We are working on resolving this.

Report this issue

When a domain administrator disables Google Chrome Management under Users > Services in the Google Admin panel, Chrome does not delete or disable the policies it applied to users in the domain. To remove these policies, you need to remove the Chrome profile from the local computer and create a new browser user profile.

Report this issue