Reidar Johansen

3 Mar 2014 11:36 PM

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

Tao Yang

4 Mar 2014 2:26 AM

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

Kevin Holman

4 Mar 2014 2:32 AM

@Tao Yang -

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

Stanislav Zhelyazkov

4 Mar 2014 6:37 AM

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

Adrian Clenshaw

4 Mar 2014 7:19 AM

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

Rodrigo

4 Mar 2014 6:38 PM

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

Kevin Holman

4 Mar 2014 8:51 PM

@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.

Arjan Vroege

4 Mar 2014 9:07 PM

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

Klaus Runggaldier

5 Mar 2014 10:24 AM

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?

Kevin Holman

5 Mar 2014 2:51 PM

@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.

Klaus Runggaldier

11 Mar 2014 10:16 AM

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

Robert R

28 Mar 2014 10:23 AM

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

Dave M

7 Apr 2014 12:31 PM

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.

Jon Sykes

28 Apr 2014 10:05 PM

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.

Kevin Holman

28 Apr 2014 10:07 PM

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.