System Center Operations Manager 2012 Daily Alert Management

Here's a quick little Operations Manager powershell command that I use pretty much on a daily basis.



Get-SCOMAlert | Where-Object { ($_.ismonitoralert -like "False") -and ($_.lastmodified -le (get-date).addhours(-24)) -and $_.resolutionstate -ne 255 } | Set-SCOMAlert -ResolutionState 255

So, this basically closes all the open alerts created by alert rules that are older than 24 hours.  Alerts created by alert monitors will close themselves once the condition that triggered them is resolved.

Windows Server 2012 R2 MPIO DSM for HP EVA P6000

HP recently released a new version of their MPIO full feature DSM for P6x00 EVA, version 4.04 on May 15, 2014. This new version now supports Windows Server 2012 R2 (x64).  You can download the software from the HP Support Center here. http://bit.ly/RaMzfZ

Although, on September 12, 2013 HP has already announced the EVA P6000 end of life.  According to the announcement: http://bit.ly/1m9S0Ho

• "The EVA P6350 and P6550 systems will no longer be orderable after January 31, 2014."
• "Customers who have purchased EVA P6350 and P6550 storage systems will be supported until January 31, 2019, 5 years after the obsolescence date."
• "HP will continue to qualify major new operating system releases (Windows, VMware, Linux, and HP-UX) until January 31, 2015 to ensure HP EVA Storage will run in your environment."

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