Thanks for all the responses on this.

Rob

From: [email protected] [mailto:[email protected]] On 
Behalf Of Sherry Kissinger
Sent: Wednesday, December 9, 2015 10:28 AM
To: [email protected]
Subject: Re: [mssms] RE: Symantec Endpoint Protection - HW Inventory

Yes, it will be two tables, and 2 views.   However, for REPORTING (not for wql 
queries in the console, but for sql you can do this), you can union them up and 
make it all "look" to the people running the reports that it's a cohesive 
thing.  Let's say you used regkeytomof, and the views ended up being 
v_gs_thatCustomRegKeyToMof0 and v_gs_thatCustomRegKeytoMof_640.  and the value 
containing the regkey is called ThatRegKey0.  Here's  1 way to union it up and 
have it available to join in and look "right" to the report readers.

;with cte (resourceid, ThatRegKey)
as (Select
      a.resourceid, a.ThatRegKey0 as [ThatRegKey]
   from
  (select resourceid, ThatRegKey0
     from v_gs_ThatCustomRegKeyToMof0
   UNION ALL
    select resourceid, ThatRegKey0
      from v_gs_ThatCustomRegKeyToMof_640
   )  a
)

Select sys1.netbios_name, cte.ThatRegkey
from v_r_system sys1
left join cte on cte.resourceid=sys1.resourceid

Otherwise, yeah, you can use roger's PS2WMI, and just inventory that.  It'll 
depend what you are comfortable with.



On Wednesday, December 9, 2015 8:57 AM, "Sharma, Siddharth" 
<[email protected]<mailto:[email protected]>> 
wrote:

This  might be helpful :
http://schadda.blogspot.in/2012/02/sccm-2012-customize-extend-hardware.html


Regards,
[cid:[email protected]] Siddharth Sharma
SCCM Engineer| Infrastructure Workplace Services
Capgemini India | Bangalore
www.capgemini.com<http://www.capgemini.com/> | 
[email protected]<mailto:[email protected]>
Contact No : +91-80-6656 7000 ; Extn:8030606



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Robert Spinelli
Sent: Wednesday, December 09, 2015 8:18 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Symantec Endpoint Protection - HW Inventory

I think I’ve done this in the past, but my brain is blocked.

If you want to capture information for Symantec (or anything really) that has 
thrown the registry keys into WOW6432Node (since the machine is x64, but the 
application is x86) is their anyway of getting the info for x86 and x64 
machines into the same table or you need to have 2 different tables like the 
way it is for Add_Remove Programs?   How do others capture data like this?  I’m 
assuming easiest way is to use RegKeyToMOF, but again would create 2 separate 
tables?

Thanks

Rob

This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.




Reply via email to