Saturday, February 14, 2015

Command Line for Finding Dell Service Tag or HP Serial

Command Line to Display Dell Server or Desktop Service Tag 

A Dell server or desktop service tag can be found by using a coomand line and no additional tools installed. This is achived simply through a common Windows command window. The command line works on Windows XP and above. Dell BCM utilities other other thrid party software does not need to be installed. The functionality to retrieve and display the service tag, serial number, and other information is built into Windows.  
On an HP system (server or desktop), the system serial number can be retrieved and displayed very quickly by starting a command prompt and typing in : 
 WMIC BIOS GET SERIALNUMBER  (the command can be upper or lower case).  

On  Dell server or Desktop/laptop system,  the same command line will display the service tag. 

Getting the serial number of a "white-box" system using command line

Without third party utilities installed on  a "white-box" system, the serial number could be displayed using the same command used for displaying the serial number and service tag. The serial number will be if the manufacturer has entered into the property field which is queried when the command is executed. Commonly however, when trying to acquire the serial number using Windows Management the results "To Be Filled by O.E.M." . 

Command on Linux to get the Dell service tag or HP serial number

Linux of course has the ability to return the manufacturers serial number or a Dell service tag. On CentOS or Red Hat Linux for example, the following utility run from a command window (shell) can be executed to display the system serial number or service tag.

dmidecode Command to display Dell Service Tag or system serial number on Linux

      # dmidecode | grep -i serial      
      # dmidecode -t 1

 DMIDECODE may have to be installed first if not available. 
The utility can be installed by executing the following: 
# yum -y install dmidecode




Dell Support said...

This is a great way to provide hardware reports for supporting many computers. With a script run from a server during logon like with a group policy object in a Microsoft Windows Domain environment, this command can be run to collect data from multiple computers on the network This is a useful method for providing support for servers and for desktop.

wetek said...

I tried this command on several computers. It worked well. one one desktop, some component had to be installed before the command would provides output results. As mentioned, this may not be desktop support software per-say but it definitely can help when implemented within a script and executed at computer start-up or at login. Upon execution of a script to run this and various other commands, this data and other data can be collected from each of the computers on the network I think there is a component to run Windows management command on remote computers. Anyone have a script to run WMIC commands from a script? Save them to a network share?

gtech said...

Another option for performing the task is the basic remote controlling a remote computer and once on the system, access via a shell or remote command prompt, run the command to get he desired information This can be a tedious way to provide desktop remote support for any purpose. Although the command executes quickly and the takes up very little resources, provide support to a computer desktop or server using a one at a time method is a tedious process. A script run at log-in or start-up is the fastest way to gather information of any kind.

Your are right about OEM as the results for systems that are not made by the larger manufacturers. These results are not useful for supporting computer desktops or servers particularly "whitebox" servers. I tried the following command and it will at least return the mode number of the mother board.
C:\>wmic computersystem get model
Although many of us have our favorite online tools and portable tools that can be run on a system either locally or remotely to get similar information in a GUI format and exportable to CSV or other file types. remembering several of these windows management commands or at least knowing they exist and easily find-able through posts such as this one is a valuable time saver. Let's say for example you only need the motherboard serial number. You don;t already have some sort of management agent on the remote computer. The remote computer is having some issues or you need to merely check the warranty of the remote desktop or server . Rather than connecting online and downloading yet another component, a simple command run at a windows command line can return the results you need for providing support in this incident. I prefer this method rather than downloading even the smallest online tool for support that gives me computer information Let's face it, unless it is an audit, most instances where this type of information is required requires only a few scraps of information. information from the remote computer like serial number or board model name or number, hard drive type and serial number.

Anonymous said...

I use remote support software to connect to servers and desktops. Once connected, SSL clients can be used to access the network components or my CentOS and other Linux systems.