XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Base board serial number in Windows VM

    Scheduled Pinned Locked Moved Hardware
    4 Posts 2 Posters 673 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      Gge7UE5yMo
      last edited by

      Hello, I am new to XCP-NG recently migrated from Hyper-V and hoping for some help with regards to using/getting the base board (motherboard) serial number in a Windows VM;
      For example, if I run the command below from a windows PC 'cmd prompt' it returns correctly the information requested in the get

      wmic baseboard get product,manufacturer,version,serialnumber
      

      But if I do this from inside a XCP-ng Windows VM, it's unable to get any information, with a message 'No Instance Available'

      I was wondering if there is something I can do to allow this information to pass through?

      And the reason for this strange requirement is for a specific software that I need to run, as it licenses against the motherboard serial number.
      Any help will be very much appreciated, TIA.

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Online
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        You need to do (at VM creation) "Copy host BIOS". I don't remember how to do it after VM creation right now (at least not on the top of my head)

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          Gge7UE5yMo @olivierlambert
          last edited by

          @olivierlambert Thank you for your swift reply!

          I think that I just stumbled across this moments after I posted my question, and have been 'playing' with these settings, it looks like I need to have the boot firmware set to bios, to allow the selection of the check box 'Copy host BIOS strings to VM', which causes a new problem as the disk I've exported from Hyper-V needs UEFI to boot 😞

          Anyway thanks so much for pointing this out, it gives me a better understanding.

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Online
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            I see, so you might need the UEFI info from the host or something similar 🤔 I don't know if this exists, I have to admit I'm not using Windows in production myself.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post