Re: WMI usability



"Sam Hobbs" wrote:

"Goppi" <Goppi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0823AD7D-25C9-4685-B4B9-39410F3CFE93@xxxxxxxxxxxxxxxx

2) NIC Speed & Duplex: The WMI properties are there, but aren't being
populated. This is well known and the only alternative is to access the
registry.

Only alternative? I don't know if the registry is the only alternative but I
would be surprised if it is. Have you checked with network programming
specialists (in other words, not here where the specialty is WMI)?
Ok, I correct myself - it seems the only other efficient method to get
thesesettings is through the registry. You could perhaps hack the IO ports on
the NIC card, but I don't consider this as the way to go.

3) Serial numbers of PC's and Screen's: Not all PC's provide the Serial
number through WMI. When it comes to screen serial numbers, the only way
you
can get them is through the registry.

There is no standard for serial numbers, so WMI depends on manufacturers for
that information. It would be interesting to determine if the Web-Based
Enterprise Management (WBEM) and/or Common Information Model (CIM) standards
implemented by other operating systems does provide any serial numbers not
provided by the Windows implementation (WMI).
Due to the cause of the problem above it's very unlikely that you would get
any other result in other OS's implementations. But since we are using
Windows OS in our company, I'm talking about WMI


Note that the registry cannot read hardware; data in the registry is read by
software. In other words, if a serial number is in the registry, then
software exists somewhere that can read it. It is likely that a user-mode
program can read the serial number. It is also a good possibility that
DeviceIoControl is needed, which is not available to scripts. So it might be
true that the registry is the only alternative for scripts but I doubt it is
the only alternative for all user-mode Windows programs.
I don't get your point. The driver for the screen(s) is writing the serial
number into the registry. Hence I can read it from the registry. This is
compliant with the VESA standard, however since there are a lot of
manufactorers of screens that are saying that they complay to the VESA
standard, but the EID does not include the serial number, I am still
questioning the sense of these standards (WMI & in this case VESA as well).

if you have 500 or more
PC's in your company and they are all from the same business-oriented
manufactorer (f.i. HP) you expect to have a consistent result and not only
a
98% solution.

Perhaps support by WMI should be a requirement for PCs in the company. It is
likely that isn't support by WMI for these things dependent on the
manufacturer? If so then they are certainly more likely to cooperae if they
know it affects sales.
True


The other issues seems to be a flaw in the design of WMI
or a not understanding of the same.

If the WBEM and/or CIM standards is or are flawed then everyone would
benefit if you become involved with the standard(s).
I'll think about it. Nice comments...
.

Relevant Pages

  • Re: Health Monitor stuck in Collecting
    ... > conflict to the Performance Monitor process. ... Check whether the performance counters are disabled. ... > Run Registry Editor by typing REGEDIT in the Run box. ... Disable WMI logging which may issue ignorable events. ...
    (microsoft.public.windows.server.sbs)
  • Re: WMI Win32_PerfFormattedData hosed - how to fix?
    ... A significant portion of the Win32_PerfRawData and Win32_PerfFormatedData WMI derived classes were returning 80041001, 80041002, or 8004100a when I tried to access them. ... First, my performance registry was hosed. ... The easy way to do this is to use the following command from a command prompt at the root of your system drive, and also the root of your 'Program Folders' drive, if you run a split configuration like me: ... net start winmgmt ...
    (microsoft.public.win32.programmer.wmi)
  • Re: PolAdtEv
    ... I did try posting a question about this on ... entire array instead of just the first 254 characters? ... >This is more a WMI question and not SMS related. ... tried tojsut get the data from the registry into ...
    (microsoft.public.sms.inventory)
  • Re: Msinfo32 error message
    ... I manually uninstalled all Norton registry keys ... Ramesh Srinivasan, Microsoft MVP [Windows Shell/User] ... The Winhelponline Blog: http://www.winhelponline.com/blog ... Error: WMI ADAP status. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: WMI usability
    ... The WMI properties are there, ... I don't know if the registry is the only alternative but I ... There is no standard for serial numbers, so WMI depends on manufacturers for ... Enterprise Management and/or Common Information Model standards ...
    (microsoft.public.win32.programmer.wmi)