Write-Warning -Message "An error occurred on $($p.OriginInfo). I tested and confirmed this works with both Windows 7 and Windows 10. You can use wmic for the task of getting the monitor make and model information from a Windows system. $Monitors = Get-CimInstance -ClassName WmiMonitorID -Namespace root/WMI -Property ManufacturerName, UserFriendlyName, ProductCodeID, SerialNumberID, WeekOfManufacture, YearOfManufactureįoreach ( $Monitor in $Monitors | Where-Object ) Get Manufacturer and Model of Monitor (s) via Command Line. $BIOS = Get-CimInstance -ClassName Win32_BIOS -Property SerialNumber $ComputerInfo = Get-CimInstance -ClassName Win32_ComputerSystem -Property Name, Manufacturer, Model Now that we have our data available in WMI, read part 2 of this guide where I will show you how to collect a custom WMI class in SCCM 2012.] $CimSession Furthermore, if you need to get the serial number, Ive included a resource. Learn how to use software or commands to find serial number or product information. To make sure that later changes in hardware are correctly recorded you will need to set a repeated deployment schedule – I recommend setting it to the same interval that your hardware inventory runs at.Īlternatively you can of course also use Scheduled Tasks to regularly run it. I tested and confirmed this works with both Windows 7 and Windows 10. If you create a package in SCCM with this script and push it out to your PCs you will get a nicely formatted WMI class on all your systems. After the script has been run once, you can query the new WMI class like usual. It will parse the binary data in the correct registry key, create a new WMI class if necessary, then fill it with the most useful EDID fields of all currently attached monitors. VMs and display-less computers obviously don’t work. We can run this script with administrator rights on any PC that has physical monitors connected to it. For this, we will use a Powershell script you can get here: Download
We can’t collect that from SCCM – it first needs to be converted into nice tabular data.
However as you can see above, it is stored directly in the raw binary format sent by the monitor. Windows collects this data and stores it in the registry in a sub-key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY They do that so the operating system can display valid resolutions to the user to choose from, but this record also includes some extremely useful data for our inventory, mostly the manufacturer name, the serial number and the manufacturing date. Monitors actually advertise quite a bit more about themselves to the computer in the form of the EDID record. Only the resolution is really of any worth to us, everything else is useless. This is what ConfigMgr collects out of the box. Configuration Manager already collects some information about the monitors by default, but it is being extremely stingy about it.
0 kommentar(er)
