Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

Agents on Windows 2012 R2 Domain Controllers can stop responding or heart-beating

Agents on Windows 2012 R2 Domain Controllers can stop responding or heart-beating

  • Comments 25
  • Likes

 

This is an issue I have been tracking for some time.  When you deploy SCOM 2012 Agents on Windows Server 2012 R2 Domain Controllers, it is possible for the agents to stop responding and or sending heartbeats.  The agent services will still be running.  You will see the events in the OpsMgr event log stop processing, and you might see heartbeat failures as well.  I have personally seen this on both of my Windows 2012 R2 domain controllers, which also run DNS and DHCP, and have the AD, DNS, and DHCP management packs imported.

This is caused by an issue in the Server OS (Windows Server 2012 R2), which is outlined at http://support.microsoft.com/kb/2923126

There is a hotfix, which addresses the issue, which is included in the Feb 2014 update rollup hotfix:  http://support.microsoft.com/kb/2919394

I recommend you consider deploying this update if you are deploying DC’s on Windows Server 2012 R2.  This issue could potentially affect any server running Windows Server 2012 R2 operating system, I have just experienced it on DC’s thus far.

If you use Windows Update – this hotfix is listed as “Optional”:

image

Comments
  • Good to know Kevin, thank you... I always appreciate your posts. Do you use twitter? Would like to follow if you do. @reidartwitt http://johansenreidar.blogspot.no

  • Thanks Kevin. I've been having this issue in my lab ever since I've upgraded everything to 2012 R2!

  • @Tao Yang -

    Yep, me too. I have just been waiting on the hotfix to announce it. :-(

  • Thanks Kevin. This was bugging me for a long time.

  • Cheers Kevin, this had been giving me no end of grief!!

  • Thanks, Kevin for articles, you can tell if the next UR2 for SCOM 2012 R2 will leave in April?

  • @Rodrigo -

    I will never comment on when a UR might or might not ship. I will only speculate.... since these are developed quarterly at best, and SCOM 2012R2 UR1 shipped at the very end of Jan, I'd not expect a following UR until the very end of April at the absolute soonest.... again, that is only speculation. Even if I knew when a UR might ship, I would not comment until they were public.

  • Many thanks for this post. Have seen this in my lab.. It was a very annoying problem.

  • After installing the update rollup my 2012 R2 DC started reporting to SCOM 2012 R2 again, but opened a lot of alerts in regards to WMI (corrupted repository, though it is perfectly fine), DNS Server (service not started though it is) etc. I think the SCOM agent has some problems connecting to WMI? Anyone else experience this?

  • @Klaus -

    You should not see that issue immediately after a reboot. The events might have been a flood of older ones catching up. There is an issue with WMI leaking on Domain Controllers with DNS on WS2012R2 (and possibly previous versions). I am planning a blog article on that.

  • @Kevin Thanks. A reboot fixed the problem, just like you said.

  • @Kevin, any additional info about the 2012R2 wmi leak issue?

  • Testing this at the moment as I have been having this problem for ages with agents going offline after a hour or so on 2012 R2 DCs.

    Also, getting WMI leak issues and then WMI stops responding as well and issues getting all DC Performance counters.

  • Hey Dave, we are seeing the same issue! If you look at the events collected on the DCs, you will see that the system is out of memory, or that the paging file is too small for the WMI query to complete, or that no more threads can be created in the system.

  • There is a WMI leak that remains, after this hotfix. This hotfix repaired the issue where the agent would immediately stop processing. The WMI issue is with the DNS PowerShell provider, but I don't have an ETA on a fix just yet.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs