User Settings on CrOS now shows the managed banner for enrolled devices.

chrome/browser/ui/options/options_util.h

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_BROWSER_UI_OPTIONS_OPTIONS_UTIL_H_
 #define CHROME_BROWSER_UI_OPTIONS_OPTIONS_UTIL_H_
 #pragma once
 
 #include "base/basictypes.h"
 
 // An identifier for an Options Tab page. These are treated as indices into
 // the list of available tabs to be displayed. PAGE_DEFAULT means select the
 // last tab viewed when the Options window was opened, or PAGE_GENERAL if the
 // Options was never opened.
 enum OptionsPage {
   OPTIONS_PAGE_DEFAULT = -1,
 #if defined(OS_CHROMEOS)
   OPTIONS_PAGE_SYSTEM,
   OPTIONS_PAGE_INTERNET,
-  OPTIONS_PAGE_ACCOUNTS,

[Mattias Nissler (ping if slow), 2011/06/15 15:02:59]

Why do you remove this? I thought we need it to persist which page should be
shown when the user next opens the settings dialog (at least that was the case
with the old native settings dialogs).

[pastarmovj, 2011/06/15 15:57:07]

This is only needed for the OptionsManagedBannerHandler. To distinguish between
which prefs should influence the banner on which page. No other references in
code exist to that enum that I could see.

 #endif
   OPTIONS_PAGE_GENERAL,
   OPTIONS_PAGE_CONTENT,
   OPTIONS_PAGE_ADVANCED,
   OPTIONS_PAGE_COUNT
 };
 
 class OptionsUtil {
  public:
   // Try to make the the crash stats consent and the metrics upload
   // permission match |enabled|, returns the actual enabled setting.
   static bool ResolveMetricsReportingEnabled(bool enabled);
 
  private:
   DISALLOW_IMPLICIT_CONSTRUCTORS(OptionsUtil);
 };
 
 #endif  // CHROME_BROWSER_UI_OPTIONS_OPTIONS_UTIL_H_