When enabling new profile management programmatically, make sure to set the

chrome/browser/profiles/profile_window.cc

Index: chrome/browser/profiles/profile_window.cc
diff --git a/chrome/browser/profiles/profile_window.cc b/chrome/browser/profiles/profile_window.cc
index 1b52daa5a9485c5310493add0be105b251a5639e..51a171c47380e9900ff8e39dce6cb11ffc276724 100644
--- a/chrome/browser/profiles/profile_window.cc
+++ b/chrome/browser/profiles/profile_window.cc
@@ -321,11 +321,26 @@ void EnableNewProfileManagementPreview(Profile* profile) {
 #if defined(OS_ANDROID)
   NOTREACHED();
 #else
+  // TODO(rogerta): instead of setting experiment flags and command line
+  // args, we should set a profile preference.
+  const about_flags::Experiment experiment = {
+      kNewProfileManagementExperimentInternalName,
+      0,

[guohui, 2014/06/19 21:27:52]

nits: probably add comments to each argument with default empty values?

[Roger Tawa OOO till Jul 10th, 2014/06/19 22:42:46]

Done.

+      0,
+      0,
+      about_flags::Experiment::ENABLE_DISABLE_VALUE,
+      switches::kEnableNewProfileManagement,
+      "",
+      switches::kDisableNewProfileManagement,
+      "",
+      NULL,
+      3
+  };
   about_flags::PrefServiceFlagsStorage flags_storage(
       g_browser_process->local_state());
   about_flags::SetExperimentEnabled(
       &flags_storage,
-      kNewProfileManagementExperimentInternalName,
+      experiment.NameForChoice(1),
       true);
 
   switches::EnableNewProfileManagementForTesting(