' ' ' Usage: ' info computername ' ' Example: ' info CXAFLSTPAW101 ' info ? ' '****************************************************************************** 'Option Explicit Dim objArgs Dim strComputer Const strGeneral_01 = 'Abstract:' Const strGeneral_02 = ' info.vbs - Command line utility that gathers' Const strGeneral_03 = ' hardware information including ' Const strGeneral_04 = ' serial numbers from a remote ' Const strGeneral_05 = ' computer. '**************************************Heading********************************* ' info.vbs ' ' Jason Hofferle ' - version 0.1.1 ' ' Monitor EDID code written by Michael Baird and modified by Denny MANSART ' ' Abstract: ' info.vbs - Command line utility that gathers hardware information ' including serial numbers from a remote computer. An example of using this WMI class with PowerShell is here. This class does the work of extracting monitor EDID data automatically. Microsoft introduced the WmiMonitorID class with Windows Vista and Server 2008. I used to have a link to the original code, but unfortunately Clarence Washington’s Win32Scripting site has closed it doors. I’ve used the code in other scripts that will poll subnets for computers and dump the info to a spreadsheet instead of just displaying it. This script grabs that data and then decodes it to get some information that is nice to have like the monitor’s serial number. Windows stores the monitor EDID information in the registry. The big deal is the monitor serial numbers, because that is a tricky piece of information to get. Kudos to Michael Baird and Denny Mansart for all that EDID code. This script will attach to a specified computer over the network and grab some information about it, including the serial number of the system and monitors attached to it. Running around writing down serial numbers seems like something we shouldn’t have to do these days, but we still do.

Getting computer serial numbers over the network

Computer serial number in registry