QlmHardware.GetUniqueSystemIdentifier1() maybe not returning the right value.

Comments

3 comments

  • Official comment
    Avatar
    Soraco Technologies (Edited )

    Hi Sean

    GetUniqueSystemIdentifer works as follows:

    For Virtual machinees, tries to get System Management BIOS UUID.

    For physical machines, tries to get Motherboard Serial Number.

    If the above fails, tries to get the first Volume Serial Number.

    If the above fails, tries to get first MAC Address.

    If the above fails, tries to get the Computer Name.

    Regards

    John

     

    Comment actions Permalink
  • Avatar
    Sean Hopen

    Thanks John, I did understand that from the documentation.

    The issue as i saw it was: "...it seems that GetUniqueSystemIdentifer() and Validate with ELicenseBinding.UniqueSystemIdentifier1 don't agree on the string to use".

    I did a little research on this. "BSN12345678901234567" is the motherboard serial number used by ASUS.  

    Fortunately QLM allows me to choose the id to use, and I could work around this issue.

    Perhaps there's something else i did wrong, but maybe other people will encounter this too, FWIW.

     

    0
    Comment actions Permalink
  • Avatar
    Soraco Technologies

    Hi Sean

    Thank you for your response.

    I'd really like to understand more about this issue and if there's a bug, we'd like to fix it.

    Can you please clarify how you are using ELicenseBinding.UniqueSystemIdentifier1 and what specific call is returning the wrong identifier?

    In the case that you mentioned, it is execpted that GetUniqueSystemIdentifer1 should return the motherboard serial number since you are not running on a VM. So I assume you're saying that ValidateLicense is using a different identifier than the motherboard SN. 

    Please include source code if possible in your response.

    Regards

    John

    0
    Comment actions Permalink

Please sign in to leave a comment.