Support Tip: Operations Manager agents on Windows Server 2012 R2 show as grayed out

[System-Center-Team]

First published on TECHNET on Mar 17, 2014

~ Brian McDermott

Hi everyone, Brian McDermott here again with another OpsMgr 2012 R2 support tip for you. Recently we’ve had some customers contact us who have installed the System Center 2012 R2 Operations Manager agent on their Domain Controllers and found that the agents become grayed out (greyed out) in the OpsMgr console and show up as not monitored.

The Operations Manager Event logs on the affected DCs contain many events similar as the following:

Source:              Health Service Modules
Date:
Event ID:            26017
Task Category:   None
Level:                Warning
Computer:        DC.domain.com
Description:
The Windows Event Log Provider monitoring the Operations Manager Event Log is 24363 minutes behind in processing events.  This can occur when the provider is restarted after being offline for some time, or there are too many events to be handled by the workflow.

One or more workflows were affected by this.

Workflow name: many
Instance name: many
Instance ID: many
Management group: MG

and

Source:              HealthService
Date:
Event ID:            4506
Task Category:   None
Level:                Error
Computer:        DC.domain.com
Description:
Data was dropped due to too much outstanding data in rule…

This behavior is not limited to DCs, however because it occurs when unloading a PowerShell module and both the AD and DNS Management Packs make frequent usage of PowerShell workflows, these servers are amongst the most likely servers to be affected.

Cause

This is happening as we are hitting a lock in the operating system code when we are unloading the PowerShell modules that ran a PowerShell script. More details on this can be found in the following Knowledge Base article:

2923126 - Application crashes when the search path is constructed for non-static dependencies of the module in Windows 8.1 ( http://support.microsoft.com/kb/2923126 )

Recovery Steps

This issue has been fixed in the following update rollup:

2919394 - Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: February 2014 ( http://support.microsoft.com/kb/2919394 )

If you are affected by this issue then you simply need to install that update to remedy the problem.

Brian McDermott | Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter :

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/