We've ran into an issue using SCCM 2012 R2, when in Hardware Inventory the Win32_User Class is active, the Domain Controllers go to 100% CPU Utilization. Deactivating this class and waiting an hour or so relieves the issue. 

According to Microsoft, this is a known issue in SCCM 2012 R2, and the only way to resolve it is to deactivate the Class in HWInventory. There isn't a fix in the works that he's aware of. We'd really like to have this reactivated, as its worked fine for over 3 years.

Anyone heard of this, and if so, is there anything that can be done? 

Never head of it myself.

Are you using this to gather inventory of local accounts on your managed clients?
Can't you gather for non-DC's only? (use a custom client settings package/policy for DC's which doesn't gather this class)

what class do you mean when you say "win32_user" ?  If you mean win32_useraccount, it completely makes sense to me that something like win32_useraccount, on a domain controller, would just kill you.  You are basically asking for "just import every single user account from AD, via Hardware inventory, into the per-computer inventory for this computer, which happens to be a domain controller".  Sure, if you have < a few hundred useraccounts in AD, it might finish.  But once you start growing your useraccounts in AD, I can't see it finishing, and even if it WOULD finish, the resulting inventory.mof file would be too big to be imported into the database.

I can't image there WOULD be a fix for that.  because it doesn't really make sense.  If you do desperately need win32_useraccount, from your NON-Domain Contollers, I'd do this:

1) Make a collection of "every system except domain controllers" (however you want to do that)

2) Your Default Client Settings does NOT have win32_useraccount enabled.

3) Create a Custom Client Agent Setting, where it's only setting is Hardware Inventory, and you enable the win32_useraccount class.  Deploy that custom client agent setting to the collection of "every system except domain controllers".

Alternatively... forget all that.  and implement this:  http://mnscug.org/blogs/sherry-kissinger/244-all-members-of-all-local-groups-configmgr-2012  and then the sql report (for just local users) would be something like select distinct domain0 [ComputerName], account0 [Local Username]  from v_gs_localgroupmembers0 where type0 = 'Local' and category0 = 'UserAccount'

Apologies, I should have included more information.

The SCCM Client isn't on the Domain Controllers, we're not installing either manually or automatically there. The Class in question is User Account (Win32_UserAccount). The default client setting has had this class activated for three plus years, and now its a problem, as its polling the DCs, for information like "FullName" and "PasswordExpires" 

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Turns out that using the Win32_UserAccount class in SCCM 2012 R2 client was the issue. Microsoft knew about the issue, but had not posted an external blog or KB article. We had to turn this class off and use another class to get the information we needed: Ful lName/Display Name (managers wanted to see name instead of User ID), etc. 

• Proposed as answer by Garth JonesMVP, Moderator 19 hours 10 minutes ago