After clean installation of Operations Manager 2012 Beta with two Management Servers, this error still come up pretty often: Event 22406 - (1 each 10 min.) - for the first Management Server (not the second one) The PowerShell script failed with below exception System.Management.Automation.ActionPreferenceStopException: Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Exception calling "GetDisplayString" with "1" argument(s): "The requested management pack display string was not found." At line:18 char:41 + if (!$mp.GetDisplayString <<<< ($lang)) {$lang = "ENU"} at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context) at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context) at System.Management.Automation.AssignmentStatementNode.Execute(Array input, Pipe outputPipe, ExecutionContext context) at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context) Script Name: Discover Agent Configurations One or more workflows were affected by this. Workflow name: ManagementGroupDiscoveryAgentConfiguration Instance name: Operations Manager Management Group Instance ID: {6B1D1BE8-EBB4-B425-08DC-2385C5930B04} Management group: YYY AND The PowerShell script failed with below exception System.Management.Automation.ActionPreferenceStopException: Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Exception calling "GetDisplayString" with "1" argument(s): "The requested management pack display string was not found." At line:71 char:28 + if (!$mp.GetDisplayString <<<< ($lang)) {$lang = "ENU"} at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context) at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context) at System.Management.Automation.AssignmentStatementNode.Execute(Array input, Pipe outputPipe, ExecutionContext context) at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context) Script Name: AgentStateRollup.ps1 One or more workflows were affected by this. Workflow name: ManagementGroupCollectionAgentHealthStatesRule Instance name: Operations Manager Management Group Instance ID: {6B1D1BE8-EBB4-B425-08DC-2385C5930B04} Management group YYY

found the answer: https://connect.microsoft.com/OpsMgr/feedback/details/683310/powershell-script-failed-to-run

Shame the URL is now dead. We may never know!