[OpsMgr 2007R2][OpsMgr 2012] Email notification may not work as expected if a time range is configured only with an exclusion ( #OpsMgr #SCOM #Notification )

The Operations Manager Engineering Team has published a post on issue with #Email #Notification when a time range is configured only with an exclusion.

When using #SystemsCenterOperationsManager (any version of #OpsMgr 2007 or #OpsMgr 2012), if you configure #Notification Recipients (so called up to OpsMgr 2007 SP1) or Subscribers (as called in #OpsMgr 2007 R2 and #OpsMgr 2012) with the option of "Only send notification during the specified times" and you configure it with only an exclude range (like "Except from" with a time range of, say 1:00am to 7:00am for example), email notifications fail altogether.


In the Operations Manager event log you will also see the event below:

      Log Name:      Operations Manager       Source:        Health Service Modules       Date:          <date> <time>       Event ID:      31501       Task Category: Notification       Level:         Warning       Keywords:      Classic       User:          N/A       Computer:      <RMS Server Name>       Description: No primary recipients were specified for the notification or all recipients are unavailable             according to the schedules. Notification will not be sent
One or more workflows were affected by this. 
Workflow name: Subscription431bd31a_37fc_4375_9cd7_29bb8a11c600
Instance name: Alert Notification Subscription Server
Instance ID: {E07E3FAB-53BC-BC14-1634-5A6E949F9230}
Management group: <Mgmt Group Name>


So what’s going on? Since we configured it to send only during specified times and then only included an excluded range, the system does not recognize any valid time that emails can be sent so it never sends any.
So to keep this from happening, or to fix it if you’ve already found yourself in this situation, you need to configure the Recipient or Subscriber first with an included time range, then configure your excluded time range.
For example, first configure you include Range like Date  | Range = Always | Time Range = All Day | Weekdays = Week days. then once you have that, configure your Exclude Range like Data Range = Always | Time Range = Excluding 1:00am to 7:00am | Weekdays = Week Days. The screen shot below shows this configuration.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] Local Resolution Time monitor in the OpsMgr DNS Management Pack may show unexpected results ( #OpsMgr #SCOM #DNS #MP )

The Operations Manager Engineering Team has published a post on the #DNS Management Pack for #SystemCenterOperationsManager.

When viewing the Local Resolution Time monitor in the DNS#MP for Operations Manager, you may notice that the response time reported does not reflect your own real world results.


Two solutions exist:

1. Configure the DNS service so that it listens only on the IPv4 address. To do this select “Only the following IP addresses:” in the dialog above and choose only the IPv4 address from the list.
Note that disabling IPv6 at the OS level is not recommended as there is no way for us to predict how this may effect your environment. Also, if IPv6 is disabled on Windows Vista, Windows Server 2008 and later versions, some components will not function as expected. See Support for IPv6 in Windows Server 2008 R2 and Windows 7 for more information.

2. The preferred fix for this is to create a reverse lookup zone as well as the associated PTR records on the DNS.
One last note: You can run into the same issue If you don’t have a reverse look up zone for the IPv4 address of the DNS server as well. This is not isolated to IPv6 but rather is a function of the lack of a proper reverse lookup zone on the DNS.

This posting is provided "AS IS" with no warranties.

[Orchestrator 2012] Automation–Orchestrator Architecture and Runbook Deployment Process ( #Orchestrator #Runbook )

Charles Joy (MSFT) has updated his guide on "best Practices" around #Orchestrator #Architecture and #Runbook Deployment.

More information on  http://blogs.technet.com/b/privatecloud/archive/2013/05/16/automation-orchestrator-architecture-and-runbook-deployment-process.aspx

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] Troubleshooting WMI Repository Bloat ( #OpsMgr #SCOM #WMI )

Russ Slaten (MSFT) used a #SCOM  #MP to troubleshoot WMI several Terminal Services servers. 

He has created scripts and shared his work on this page. 

He goes for example:

• The number of failures
• The number of failures Cimv2
• The number of failed winmgmt / control verifyrepository
• WMI size
• The number of WMI errors reported

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Custom Rule for selective APM Event collection ( #OpsMgr #SCOM #APM )

Daniele Muscetta (MSFT) has published an article on the team blog System Center Operations Manager to discuss customizing the collection rule #APM events. Side effect may occur when the agent is multi-homed on several environments. It gives such a way to create a custom rule to circumvent the problem.

More information on the ticket: Custom Rule for selective APM Event collection

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2] Operations Manager agents with teamed network adapters fail to be discovered and monitored

Operations Manager agents with teamed network adapters fail to be discovered and monitored

Direct link to Microsoft page

System Center Operations Manager 2007 R2 agent computers that utilize NIC teaming are not discovered or monitored and you see the following errors:

Log Name:       Operations Manager
Source:            Health Service Script
Date:               <date>
Event ID:          4001
Task Category: None
Level:              Error
Keywords:       Classic
User:              N/A
Computer:      <computerName>
Description: Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs : The class name 'Win32_PerfFormattedData_Tcpip_NetworkInterface Where Name ='VLAN100:HP Network Team _1'' did not return any valid instances.  Please check to see if this is a valid WMI class name.. Invalid class

You may also see the following alert:

The process started at 09:44:43 failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0
Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs"
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 23\\
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.NetworkAdapter.PercentBandwidthUsedTotal.Collection
Instance name: Local Area Connection
Instance ID: {}

Cause

This can occur if the drivers being used for NIC teaming on the agent do not properly register in WMI.

The Base OS Management Pack (version 6.0.6958.0) contains a script that is responsible for discovering teamed adapters named Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs. If the NIC teaming driver being used fails to properly register in WMI, when the script runs and fails to find the registered classes the script will fail and log the errors above. 

Many teaming NIC drivers also fail to register performance counters which can also be a reason why the required WMI registration is not created.

Resolution

If you experience script failures such as these, disabling NIC teaming on the agent computer will resolve the issue. The problem with the NIC registration in WMI needs to be addressed by the NIC manufacturer so that the driver correctly register itself in WMI when installed. Please contact the adapter manufacturer for more information.

This posting is provided "AS IS" with no warranties.