Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
CLI command for obtaining system serial number

Answered CLI command for obtaining system serial number

  • Wednesday, January 02, 2013 2:23 PM
     
     
    Sign In to Vote
    0

    Hi ~ I am looking for a CLI command that would return a systems hardware serial number.  I have tried "wmic bios get serialnumber" (which works on my WinXP machine).  I am trying to retrieve the serial number remotely on a SBS 2003 server but this command returns the following error:
    "C:\>wmic bios get serialnumber
    ERROR:
    Code = 0x8007007e
    Description = The specified module could not be found.
    Facility = Win32"

    any help?

    thanks much ... Happy New Year!

    Tim ...

     

All Replies

  • Wednesday, January 02, 2013 2:37 PM
     
      Has Code
    Sign In to Vote
    0

    does the command work locally on the sbs 2003 machine or is that where you see the error?

    remote querying should work like that:

    wmic /Node:"yourservername" bios get serialnumber

    if you get the error locally already, you can try to verify the wmi repository

    winmgmt /verifyrepository

    see here http://msdn.microsoft.com/en-us/library/windows/desktop/aa394525(v=vs.85).aspx

     
  • Wednesday, January 02, 2013 2:51 PM
     
     
    Sign In to Vote
    0

    Thank you for your quick response.  I am actually connected via RDP and running the command prompt.  I have since obtained the serial number through the HP Insight Management Diagnostic Tool but would still like to have the correct command.  It is a very useful tool to use.

    Thanks again

    Tim ...

     
  • Wednesday, January 02, 2013 3:28 PM
     
     
    Sign In to Vote
    0

    Hi Tim,

    See KB 558124

    http://support.microsoft.com/kb/558124

    This should be working.

    Kind Regards,

    Dion

    • Edited by Diondk Wednesday, January 02, 2013 3:29 PM
    • Proposed As Answer by Diondk Thursday, January 03, 2013 10:29 AM
    • Unproposed As Answer by Diondk Thursday, January 03, 2013 10:29 AM
    •  
     
  • Wednesday, January 02, 2013 3:47 PM
     
     
    Sign In to Vote
    0

    Thank you, Diondk.  I think there are other issues with the server I am dealing with.  I tried that command on MY server in my office (Windows 2003 Std.) and it worked fine.  Should I be concerned with that error message I am getting on my client's server?

    Thanks Tim

    Tim ...

     
  • Thursday, January 03, 2013 10:23 AM
     
     Answered
    Sign In to Vote
    0

    Hi Tim,

    If you still got issue's try the WMI Diagnosis Utility it will help to diagnose and repair any problems with the WMI service.

    http://www.microsoft.com/en-us/download/details.aspx?id=7684

    - Dion

     
  • Tuesday, January 08, 2013 3:11 PM
     
     
    Sign In to Vote
    0

    Wonderful!  Thank you, Dion!

    (sorry for the delay :-))  I will keep the thread posted.

    Tim ...