I've turned it on in the lab once; years and years and years ago. so my memory may be faulty. the problem I recall from then is that it's a lot of junk data. There's a lot of 'stuff' that gets registered as a printer that you just don't care about; like 'printers' that let your print to pdf, or 'print to OneNote'. it's a lot of crap for little gain. Looking at my own lab box--1 actual real physical printer out of which I would get ink on a sheet of paper if I chose to use it, and 3 "print to xxx..." fake printers.
I'd turn it around--what do you EXPECT that to gather for you? It doesn't gather things like serial number, or even if the printer is really actually honestly there. It might just be a driver for a printer that box used once 2 years ago. Also, this might not be so true anymore (remember this was years ago I looked at it); one could for example load a printer driver for "hp laserjet" -- because it will allow you to print to that knock-off cheap-o one you picked up at a flea market. It's not really a laserjet on the other end of that driver. On Fri, Jan 13, 2017 at 1:27 PM, Jeff Poling <[email protected]> wrote: > Are there downsides to enabling the Win32_Printer class in hardware > inventory classes? Just curious if others have collected that data…. > > > > Thanks, > > > > Jeff > > > > Sent from my Windows 10 phone > > > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
