For ChromeOS devices in an AD environment, we recommend using cloud-based Chrome management and Kerberos. Note: ChromeOS device management with Microsoft Active Directory (AD) is no longer available for new users. You must be signed in as a super administrator for this task.

Let users choose to have a separate profile but forbid secondary managed accounts-Behaves the same as Let users choose to have a separate profile, except the newly created profile has no secondary accounts.

User don’t check the box-The existing profile continues to exist.

All existing browsing data is present in the new profile.

Users check the box-The existing profile data is associated with the managed account.

Local browsing data includes bookmarks, history, password, autofill data, open tabs, cookies, cache, web storage, extensions, and so on. When the profile is being created, users see a checkbox where they can choose to keep local browsing data and associate it with the managed account. The profile might also have secondary accounts.

Let users choose to have a separate profile-The managed account is the primary account.

Users can use their managed Google Account without having to create a separate profile. There is no restriction on managed accounts.

Do not force separate profile-This is the default.

When the profile is created, importing existing browsing data is allowed.

Force separate profile and forbid secondary managed accounts-The managed account is the primary account.

The newly created profile might also have secondary accounts. Force separate profile-The managed account is the primary account.Specifies whether users are required to create a separate profile when they sign in to their managed Google Account.Ĭhoose from one of the following options:

Available on Chrome browser for Windows, Mac, and Linux.

Google chrome cast in stores