Yes… All of our stuff does that all the time. ☺ From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Friday, October 16, 2015 3:18 AM To: [email protected] Subject: RE: [mssms] RE: Reg Inventory, best way for unknown values
Thanks Sherry + everytone else. So since I can do whatever, I will stick it into WMI and use the ID as key, and only create an instance when we have data. So each machine will have different amounts of instances. So just to double-check, client would pick that up and then deal with the different instances, creating SQL rows for only each new instance that is found? //A From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: den 15 oktober 2015 23:21 To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Reg Inventory, best way for unknown values If you mean you'd have something in WMI like this: ID:1 Name:Window Platform Count: 59 DownloadSize:699703 P2P:0 ID:2 Name:<null> Count: 185 DownloadSize:133641057 P2P:0 ID:3 Name:Skype Count: 1 DownloadSize:41955352 P2P:0 ID:4 Name:<null> Count: <null> DownloadSize:<null> P2P:<null> ID:5 Name:Office Font Download Count: 0 DownloadSize:0 P2P:0 What I'd do is on the custom Import-This.mof file, you'd either want ID to be the <key> field (and deal with the extra rows for all the Null values in SQL on the reporting side), or you could instead have TWO <key> fields, of say, Name and DownloadSize -- I think that would do it. But testing needed. Could your routine (whatever it is) simply not record anything for "ID = 4" when everything else about it is null? Then it's easy to just use ID as the single <key> On Thursday, October 15, 2015 3:52 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: +1 WMI is a much better place for dynamic data like this. Root\2Pint would be a better namespace though – avoid customizing cimv2 when possible. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, October 15, 2015 3:19 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Reg Inventory, best way for unknown values The structure looks good, but I would much rather prefer WMI than the registry, if that is possible. Easier to import, and cleaner to manage, especially with ConfigMgr. Maybe something like root\cimv2\2Pint with an instance for each BITS job? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Thursday, October 15, 2015 4:12 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Reg Inventory, best way for unknown values Hey list, We are working on generating a log structure for all BITS jobs (not only ConfigMgr ones as that already exists). This is for all the other traffic like Adobe, Chrome etc. You will be amazed to see how much stuff is using BITS. And we need some input on how to provide the info the best way for ConfigMgr. This will be part of the OSD BranchCache kit for free, but to get to the point. We want to write this data to the registry and allow for admins to collect if they want to. But since we don’t know what the reg keys are goint to be called, it’s hard to get with a .mof right? As I understand it, that requires known keys and values? If we report on an ID of 0-999 and name the reg key values like HKEY_LOCAL_MACHINE\SOFTWARE\2Pint Software\BCReporter\ReportData\0 where 0 is the actual value name for the first “type” of job and then 999 would be the last. Obviously we don’t want to fill up the DB with lots of empty data fields, so does ConfigMgr generate the tables on .mof creation or when inventory comes back? Or should I structure it in some other way? Sample data in a raw dump format: ===================================================================== TotalJobs:304 Total number of files:636 Total bytes Transferred:275840804 Total bytes Transferred From Peers:0 ===================================================================== ID:1 Name:Window Platform Count: 59 DownloadSize:699703 P2P:0 ID:2 Name:Window Update Count: 185 DownloadSize:133641057 P2P:0 ID:3 Name:Skype Count: 1 DownloadSize:41955352 P2P:0 ID:4 Name:Windows Setup Installer Count: 1 DownloadSize:98232928 P2P:0 ID:5 Name:Office Font Download Count: 0 DownloadSize:0 P2P:0 ID:6 Name:Windows Device Management Count: 1 DownloadSize:309105 P2P:0 ID:7 Name:Microsoft Outlook OAB Count: 55 DownloadSize:1002637 P2P:0 ID:8 Name:Windows Device Management Count: 0 DownloadSize:0 P2P:0 ID:9 Name:Silverlight Updater Count: 2 DownloadSize:22 P2P:0 ID:10 Name:Windows Device Management Count: 0 DownloadSize:0 P2P:0 ID:11 Name:Windows Device Management Count: 0 DownloadSize:0 P2P:0 ID:12 Name:Configuration Manager Count: 0 DownloadSize:0 P2P:0 ID:12 Name:Configuration Manager Count: 0 DownloadSize:0 P2P:0 ID:14 Name:Configuration Manager Uploads Count: 0 DownloadSize:0 P2P:0 ID:15 Name:Adobe Reader Count: 0 DownloadSize:0 P2P:0 //A Regards, Andreas Hammarskjöld Co-Founder & Dev Guy Skunkworks Division 2Pint Software<https://2pintsoftware.com/> Mobile: +46 727 253995 [email protected]<mailto:[email protected]> https://twitter.com/AndHammarskjold The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
