There’s no such list. ConfigMgr can inventory anything you want it to 
ultimately. If it’s accessible in or via WMI, then it’s trivial for ConfigMgr 
to grab it. This includes anything in the registry, event logs (be careful 
here), or custom data – Roger created a cool method last year to pull in 
PowerShell results even. The default sms_def.mof is simply a subset of things 
that could have been inventoried like 20 years ago. It is by no mean exhaustive 
and would be a bad thing to give to anyone as representative of what ConfigMgr 
can inventory.

J

From: <[email protected]> on behalf of "Schultz, Michael A" 
<[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Tuesday, December 13, 2016 at 7:56 PM
To: "[email protected]" <[email protected]>
Subject: RE: [mssms] Convert MOF to manager readable format

We have SCCM and there is a CA tool (ITCM) in our enterprise that collects a 
lot of data.  We are hoping to just use SCCM but they want to see everything 
SCCM collects and could collect OOB from hardware inventory.  They are then 
going to compare the tool and decide.

Michael Schultz
Client Systems Engineering
Information Systems
Providence Health & Services
[email protected]<mailto:[email protected]>

From: [email protected] [mailto:[email protected]] On 
Behalf Of Sherry Kissinger
Sent: Tuesday, December 13, 2016 4:29 PM
To: [email protected]
Subject: Re: [mssms] Convert MOF to manager readable format

Personally, I'd reverse it.  "What do you, managers, want to see that you don't 
already see?"  Why? Even if you got it into a legible-ish format, you'd spend a 
lot of time trying to explain what each option actually *is*.

On Dec 13, 2016 4:12 PM, "Schultz, Michael A" 
<[email protected]<mailto:[email protected]>> wrote:
Anyone have any recommendations for a tool or script that will read an exported 
HInv MOF and output something manager readable?  I have been tasked to report 
everything that is being inventoried and what is available to be inventoried.

Michael Schultz
Client Systems Engineering
Information Systems
Providence Health & Services
[email protected]<mailto:[email protected]>


________________________________

This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.



________________________________

This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.



Reply via email to