Start in elevated mode when creating a new managed user profile.

chrome/common/pref_names.h

Index: chrome/common/pref_names.h
diff --git a/chrome/common/pref_names.h b/chrome/common/pref_names.h
index 2e466cbf0d2d6ec7a86a9feff83f2967c2d4a890..8db2aef88a5b2c24ed840e6c4a86d0bacbb971b5 100644
--- a/chrome/common/pref_names.h
+++ b/chrome/common/pref_names.h
@@ -22,6 +22,7 @@ extern const char kDisableScreenshots[];
 extern const char kHomePageIsNewTabPage[];
 extern const char kHomePage[];
 extern const char kHomePageChanged[];
+extern const char kManagedModeHasSeenSetupDialog[];

[Bernhard Bauer, 2013/04/08 12:26:09]

I'm not very happy using "managed mode" in code (we have managed profiles, but
managed mode is deprecated), but I guess it would be better to change these at
once.

[Adrian Kuegel, 2013/04/08 14:31:04]

What prefix would you suggest instead? ManagedUser?
But I guess you are right, in order to have it consistent it should all be
changed, which should probably belong to a separate changelist.

[Bernhard Bauer, 2013/04/09 11:41:22]

Yes, ManagedUser (managed_user.X in the actual string) would probably be best,
but as the preferences get grouped by the dot-prefix anyway, it makes more sense
to do that separately.

 extern const char kManagedModeLocalPassphrase[];
 extern const char kManagedModeLocalSalt[];
 extern const char kManagedModeManualHosts[];