System Center Operations Manager 2012 R2 - System Center Management Health Service Unloaded System Rule(s) - Windows Server 2003/2008 (non R2) missing PowerShell 2.0

I know its been awhile since the last post, so here it goes...

Issue:

This week we are dealing with a specific error that caused multiple agents to throw the alert monitor, System Center Management Health Service Unloaded System Rule(s) with the following description.

The System Center Management Health Service ????????-????-????-????-???????????? running on host <computername> and serving management group with id {????????-????-????-????-????????????} is not healthy. Some system rules failed to load.

This caused the agents to go into a "grey" state.  Review the Operations Manager log on an affected agent computer and look for errors with event id 4513 with the following description.

The callback method DeliverDataToModule failed with exception "Could not load file or assembly 'System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=????????????????' or one of its dependencies. The system cannot find the file specified." in the module Microsoft.EnterpriseManagement.Modules.PowerShell.PowerShellProbeActionModule.

Workflow: Microsoft.IntelligencePacks.Types.HealthServiceProxyConfiguration 

The common factor among the affected computer agents was all Windows Server 2003 and Windows Server 2008 (non R2) which were missing Powreshell 2.0.

Solution and workaround:

The solution is to override the Advisor Proxy Setting Rule or install Powershell 2.0.

It was not until after I had called Microsoft Support which were quick to find the cause and provide a solution to this issue, that I found this issue being discussed on the TechNet Forum - Grey Agents after New Management Pack with id:"Microsoft.IntelligencePacks.Types", version:"7.0.9781.0" received. - and the Microsoft Azure forum - Windows Server 2003 'grey' due to missing Powershell system rule Microsoft.IntelligencePacks.Types.HealthServiceProxyConfiguration.

Installing Operations Manager 2012 R2 agent fails with error code 80070005

Today, I ran into an issue when trying to install the SCOM 2012 R2 agent on a domain controller running Windows Server 2012 R2.  I found the following technet article which proved useful as it had the error and error code I was getting, but the remediation steps didn't solve my problem.

Troubleshooting Issues When You Use the Discovery Wizard to Install an Agent

Upon further investigation, I could not access the SYSVOL and NETLOGON shares on that specific domain controller from the SCOM management servers running Windows Server 2012 R2.

I remember seeing this sort of issue when accessing shares on a NetApp that we have from a Windows 2012 Server.  So disabling the secure negotiate on the Windows 2012 Server solved that issue.  So I did the same on the SCOM Management Servers which ended up fixing this issue using the following powershell command.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force

 http://support.microsoft.com/kb/2686098

You should also read this which explains Secure Negotiate which is new for SMB3.
http://blogs.msdn.com/b/openspecification/archive/2012/06/28/smb3-secure-dialect-negotiation.aspx