Yeah, I ran the WMIC command and it was blank in SystemEnclosure. But CSProduct Name does have a value. However, my rule doesn’t trigger. :/
From: [email protected] [mailto:[email protected]] On Behalf Of steven hosking Sent: Friday, August 29, 2014 4:37 PM To: [email protected] Subject: Re: [MDT-OSD] WMI query for model comes up blank Is the field populated if you look locally on the machine? Another option would be to grab 3-4 hardware ID's that are unique to that model as the WMI and use them as the WMI call, its not optimal but would get you over the hurdle From: Daniel Ratliff<mailto:[email protected]> Sent: Saturday, 30 August 2014 9:36 AM To: [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]> Maybe a firmware or bios update our another tool to populate the wmi entries? Not sure if that's hardware or os causing them to be blank. -----Original Message----- From: Murray, Mike [[email protected]<mailto:[email protected]>] Sent: Friday, August 29, 2014 07:27 PM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] WMI query for model comes up blank We have a handful of OptiPlex 980’s that have no model listed in WMIC SystemEnclosure. No idea why. So my WMI query to apply drivers (SELECT * FROM Win32_ComputerSystem Where Model = 'OptiPlex 980') doesn’t work. I’ve also tried SELECT * FROM Win32_ComputerSystemProduct Where Name = 'OptiPlex 980', but that doesn’t seem to work, either. Any ideas on how to force the drivers to apply? Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> 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.
