1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

virtualization and oem licenses

Discussion in 'Windows Home Server' started by agostino, May 12, 2009.

  1. agostino

    agostino Guest

    I have a virtual server with a guest so: win 2003 std oem.
    In case of disaster, i will move the machine on a new hardware.
    The license will no longer be valid, so i will buy a new OEM license.
    If i don't reinstall the sytem, it will keep the old-license product key.

    Microsoft asks me to buy a license for each hardware, and i do.
    But do they ask me to reinstall the hole system in order to have the new
    product id?

    tnx
    Agostino
     
  2. Bill Grant

    Bill Grant Guest

    The license for an OS running in a vm is tied to the vm, not to the host
    machine on which it is running. As far as licensing is concerned, the term
    "machine" covers either a virtual machine or a physical machine. If you have
    a license for the OS running in a vm, it does not matter what physical
    machine it runs on or what type of virtualization is used. The OS is
    licensed to run on that "machine".

    "agostino" <sclauzero@_rem_cedapsrl.com> wrote in message
    news:uGvs36x0JHA.4272@TK2MSFTNGP06.phx.gbl...
    >
    > I have a virtual server with a guest so: win 2003 std oem.
    > In case of disaster, i will move the machine on a new hardware.
    > The license will no longer be valid, so i will buy a new OEM license.
    > If i don't reinstall the sytem, it will keep the old-license product key.
    >
    > Microsoft asks me to buy a license for each hardware, and i do.
    > But do they ask me to reinstall the hole system in order to have the new
    > product id?
    >
    > tnx
    > Agostino
    >
    >
    >
    >
    >
    >
     
  3. agostino

    agostino Guest

    The "guest" machine thinks the vm is it's hardware, so moving on a different
    phisical machine doesn't trigger the "invalidation" of the activation.
    But from a legal point of view this violates the oem agreement (while it
    would be correct in the case of open licenses).
    So my question is: how do I change the product key to a win 2003 std os?
    tnx

    "Bill Grant" <not.available@online> ha scritto nel messaggio
    news:%234k71o10JHA.4800@TK2MSFTNGP06.phx.gbl...
    > The license for an OS running in a vm is tied to the vm, not to the host
    > machine on which it is running. As far as licensing is concerned, the term
    > "machine" covers either a virtual machine or a physical machine. If you
    > have a license for the OS running in a vm, it does not matter what
    > physical machine it runs on or what type of virtualization is used. The OS
    > is licensed to run on that "machine".
    >
    > "agostino" <sclauzero@_rem_cedapsrl.com> wrote in message
    > news:uGvs36x0JHA.4272@TK2MSFTNGP06.phx.gbl...
    >>
    >> I have a virtual server with a guest so: win 2003 std oem.
    >> In case of disaster, i will move the machine on a new hardware.
    >> The license will no longer be valid, so i will buy a new OEM license.
    >> If i don't reinstall the sytem, it will keep the old-license product key.
    >>
    >> Microsoft asks me to buy a license for each hardware, and i do.
    >> But do they ask me to reinstall the hole system in order to have the new
    >> product id?
    >>
    >> tnx
    >> Agostino
    >>
    >>
    >>
    >>
    >>
    >>
     

Share This Page