locked
WGA failure after some shuffling RRS feed

  • Question

  • Good day,

      My question pertains to a copy of windows that was bundled with a machine I use at work: About a month ago my mainboard failed, so both hard disks were moved into a new computer (from the same batch).

    Not having booted since, I attempted to boot windows today (via Virtualbox), and have been repeatedly informed of its invalid license.

    I'm in Lancaster University, which to my knowledge has a site license, and these machines were both provided by Dell  Whilst I recognise that the hardware ID and such will have changed in all possible regards, is there some way to relicense to the uni without reinstalling?

    Thanks in advance,

    S. Wattam

    P.S.Below is my WGA diagnostic output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {6FEAC91A-CD26-4083-9152-D38D7EFBFACA}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100618-1621
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{6FEAC91A-CD26-4083-9152-D38D7EFBFACA}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-733WD</PKey><PID>00371-OEM-8992671-00524</PID><PIDType>2</PIDType><SID>S-1-5-21-1247827125-1996990295-3643737950</SID><SYSTEM><Manufacturer>innotek GmbH</Manufacturer><Model>VirtualBox</Model></SYSTEM><BIOS><Manufacturer>innotek GmbH</Manufacturer><Version>VirtualBox</Version><SMBIOSVersion major="2" minor="5"/><Date>20061201000000.000000+000</Date></BIOS><HWID>B0BB3607018400EC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ABEA72C50866586</Val><Hash>hvzo3zjKlaC5lDy3mYNaw+qjwOg=</Hash><Pid>89388-707-1353414-65159</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00178-926-700524-02-1033-7600.0000-2112010
    Installation ID: 018656014823321676284530769813610585184813739836842581
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: 733WD
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 3
    Trusted time: 31/05/2011 12:11:58

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 5:31:2011 12:09
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: LgAAAAEAAwABAAEAAAABAAAAAQABAAEAnJ9ePLyt5rckZv7btjV26Hb5ulsUpg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            VBOX          VBOXAPIC
      FACP            VBOX          VBOXFACP
      SSDT            VBOX          VBOXCPUT


    Tuesday, May 31, 2011 11:21 AM

Answers

  • "Stephen Wattam" wrote in message news:575f19af-c808-4450-83d5-b0ff2304b582...

    Good day,

      My question pertains to a copy of windows that was bundled with a machine I use at work: About a month ago my mainboard failed, so both hard disks were moved into a new computer (from the same batch).

    Not having booted since, I attempted to boot windows today (via Virtualbox), and have been repeatedly informed of its invalid license.

    I'm in Lancaster University, which to my knowledge has a site license, and these machines were both provided by Dell  Whilst I recognise that the hardware ID and such will have changed in all possible regards, is there some way to relicense to the uni without reinstalling?

    Thanks in advance,

    S. Wattam

    P.S.Below is my WGA diagnostic output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048



    The Windows Key in use here is an OEM_SLP one - and such Keys are only valid when used in the original computer that they came with. They cannot be used in Virtual Machines.
    For Virtual Machines, you need to use Full Retail Licenses, or at least the COA License that is on the machine';s case.
    OEM or COA Keys are NOT transferable between machines under any circumstances.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 11:31 AM
    Moderator
  • I believe Colin may be correct in his interpretation of the License.  However, there seems to be intricacies in Licensing when it comes to VMs that I don't fully understand.  I believe http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx or more specifically  http://www.microsoft.com/licensing/about-licensing/virtualization.aspx would be a better resource regarding VM related Licensing questions.

     

    Sorry I couldn't be more help,

     


    Darin MS
    Wednesday, June 1, 2011 9:10 PM

All replies

  • "Stephen Wattam" wrote in message news:575f19af-c808-4450-83d5-b0ff2304b582...

    Good day,

      My question pertains to a copy of windows that was bundled with a machine I use at work: About a month ago my mainboard failed, so both hard disks were moved into a new computer (from the same batch).

    Not having booted since, I attempted to boot windows today (via Virtualbox), and have been repeatedly informed of its invalid license.

    I'm in Lancaster University, which to my knowledge has a site license, and these machines were both provided by Dell  Whilst I recognise that the hardware ID and such will have changed in all possible regards, is there some way to relicense to the uni without reinstalling?

    Thanks in advance,

    S. Wattam

    P.S.Below is my WGA diagnostic output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048



    The Windows Key in use here is an OEM_SLP one - and such Keys are only valid when used in the original computer that they came with. They cannot be used in Virtual Machines.
    For Virtual Machines, you need to use Full Retail Licenses, or at least the COA License that is on the machine';s case.
    OEM or COA Keys are NOT transferable between machines under any circumstances.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 11:31 AM
    Moderator
  • "Stephen Wattam" wrote in message news:575f19af-c808-4450-83d5-b0ff2304b582...

    Good day,

      My question pertains to a copy of windows that was bundled with a machine I use at work: About a month ago my mainboard failed, so both hard disks were moved into a new computer (from the same batch).

    Not having booted since, I attempted to boot windows today (via Virtualbox), and have been repeatedly informed of its invalid license.

    I'm in Lancaster University, which to my knowledge has a site license, and these machines were both provided by Dell  Whilst I recognise that the hardware ID and such will have changed in all possible regards, is there some way to relicense to the uni without reinstalling?

    Thanks in advance,

    S. Wattam

    P.S.Below is my WGA diagnostic output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
    Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
    Windows Product ID: 00371-OEM-8992671-00524
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {6FEAC91A-CD26-4083-9152-D38D7EFBFACA}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100618-1621
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{6FEAC91A-CD26-4083-9152-D38D7EFBFACA}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-733WD</PKey><PID>00371-OEM-8992671-00524</PID><PIDType>2</PIDType><SID>S-1-5-21-1247827125-1996990295-3643737950</SID><SYSTEM><Manufacturer>innotek GmbH</Manufacturer><Model>VirtualBox</Model></SYSTEM><BIOS><Manufacturer>innotek GmbH</Manufacturer><Version>VirtualBox</Version><SMBIOSVersion major="2" minor="5"/><Date>20061201000000.000000+000</Date></BIOS><HWID>B0BB3607018400EC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ABEA72C50866586</Val><Hash>hvzo3zjKlaC5lDy3mYNaw+qjwOg=</Hash><Pid>89388-707-1353414-65159</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00178-926-700524-02-1033-7600.0000-2112010
    Installation ID: 018656014823321676284530769813610585184813739836842581
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: 733WD
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 3
    Trusted time: 31/05/2011 12:11:58

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 5:31:2011 12:09
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: LgAAAAEAAwABAAEAAAABAAAAAQABAAEAnJ9ePLyt5rckZv7btjV26Hb5ulsUpg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            VBOX          VBOXAPIC
      FACP            VBOX          VBOXFACP
      SSDT            VBOX          VBOXCPUT



    Hmmmm - thinking a little more on this, you may be able to use a clause in the SLT's that I only recently discovered myself....

    d. Use with Virtualization Technologies. Instead of using the software directly on the licensed computer, you may install and use the software within only one virtual (or otherwise emulated) hardware system on the licensed computer. When used in a virtualized environment, content protected by digital rights management technology, BitLocker or any full volume disk drive encryption technology may not be as secure as protected content not in a virtualized environment. You should comply with all domestic and international laws that apply to such protected content.

    Since you say that the two machines are from the same batch, the OEM_SLP license should be valid on a bare metal install (but not in a VM) The COA license *for the current machine*, however, should be valid in the VM.
    Simply use the Change Product Key link on the System Properties page - you will have to activate by telephone.
     
    telephone activation.
     Click on the Start button
    in the Search box, type
    SLUI   4
    and hit the Enter key
    follow the instructions - but when asked which service you require by the telephone ansafone, do NOT reply - this should force an operator to respond, who can deal with you.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 11:37 AM
    Moderator
  • Noel,

      Many thanks for the expediant reply.  I'll give them a ring later and sort it out.

    --S. Wattam

    Tuesday, May 31, 2011 12:52 PM
  • "Stephen Wattam" wrote in message news:44091534-710c-4b82-b1a9-dfc9088e86e4...

    Noel,

      Many thanks for the expediant reply.  I'll give them a ring later and sort it out.

    --S. Wattam


    Note that it would be much better if you were to sort it out through the IT department - it's their PC after all?

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, May 31, 2011 1:22 PM
    Moderator
  • Noel,
     
    He cannot apply that clause to an already installed OEM copy of Windows.  See the section above your quote (OEM version)
     
    b. License Model. The software is licensed on a per copy per computer basis. A computer is a physical hardware system with an internal storage device capable of running the software. A hardware partition or blade is considered to be a separate computer.
     
    2. INSTALLATION AND USE RIGHTS.

    a. One Copy per Computer.
     
    The software license is permanently assigned to the computer with which the software is distributed. That computer is the "licensed computer." 

    Once installed the software cannot be transferred and only one copy is permitted to be installed.   The virtual machine is in fact a separate computer under the meaning of the license because installing the software in it would be a second installation of the software.  That violates the 'one copy per computer' clause of 2a.  Had the OEM shipped this copy of Windows installed in a vm (which is exactly what Microsoft does with XP Mode) the user would be fine.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Tuesday, May 31, 2011 1:54 PM
    Answerer
  • "Cbarnhorst" wrote in message news:a82449d6-7fcc-4f3e-adfc-f01b8e4b1f75...

    Noel,
     
    He cannot apply that clause to an already installed OEM copy of Windows.  See the section above your quote (OEM version)
     
    b. License Model. The software is licensed on a per copy per computer basis. A computer is a physical hardware system with an internal storage device capable of running the software. A hardware partition or blade is considered to be a separate computer.
     
    2. INSTALLATION AND USE RIGHTS.

    a. One Copy per Computer.
     
    The software license is permanently assigned to the computer with which the software is distributed. That computer is the "licensed computer." 

    Once installed the software cannot be transferred and only one copy is permitted to be installed.   The virtual machine is in fact a separate computer under the meaning of the license because installing the software in it would be a second installation of the software.  That violates the 'one copy per computer' clause of 2a.  Had the OEM shipped this copy of Windows installed in a vm (which is exactly what Microsoft does with XP Mode) the user would be fine.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    Colin -
    I wasn't advocating using two installs - merely saying that I believe that it is legitimate to use the COA license in a VM on a properly licensed system. (so if the machine is upgraded using a Retail Ultimate,  the COA license could be used in a VM on that machine).
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, June 1, 2011 6:52 AM
    Moderator
  • Noel,

    The OEM license is specific that it cannot be reassigned.  It makes no difference whether or not you are using the COA key.  As the license says,

    a. One Copy per Computer.

    The software license is permanently assigned to the computer with which the software is distributed. That computer is the "licensed computer." 

    A different blade or partition is another device and virtual machines are a different device or partition because the vhd is a partition.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Wednesday, June 1, 2011 12:46 PM
    Answerer
  • "Cbarnhorst" wrote in message news:4d6295a9-e14b-4140-93f0-2cd1c190c9ff...

    Noel,

    The OEM license is specific that it cannot be reassigned.  It makes no difference whether or not you are using the COA key.  As the license says,

    a. One Copy per Computer.

    The software license is permanently assigned to the computer with which the software is distributed. That computer is the "licensed computer." 

    A different blade or partition is another device and virtual machines are a different device or partition because the vhd is a partition.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    My quote was from the OEM license SLT - which specifically states (AFAICS) that it can be used as a VM on the same machine.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, June 1, 2011 1:36 PM
    Moderator
  • But only if it has not previously been installed on any computer.  It is a one-time choice for OEM software that is not available to the end user because the OEM has already made it.  It is an impossible provision when the license has been preinstalled at the factory.  Darin can verify, but I assure you that an OEM copy that has been retired (upgraded or whatever) cannot be used anywhere including in a vm except to be restored where it was originally installed.  It makes no difference that the software can be installed in a vm if the vm is not the first device it was installed on.  I would agree that it is an absurd situation that the provision has been left in the end user license for preinstalled OEM copies.  But regardless there is no legitimate way to re-use an OEM SLP/COA copy that has been retired anywhere else.  Remember that the license defines the blade or partition where the software was preinstalled as the licensed device and that the license is permanently assigned there.  Only a repair replacement is allowed.

    Microsoft does do initial OEM installations in vms;  that is what XP Mode is.  Microsoft also provides a license and preinstallation software for distributing OEM Windows in virtual machines. 

    Hopefully Darin will comment further.

     


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

     


    Wednesday, June 1, 2011 2:04 PM
    Answerer
  • I believe Colin may be correct in his interpretation of the License.  However, there seems to be intricacies in Licensing when it comes to VMs that I don't fully understand.  I believe http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx or more specifically  http://www.microsoft.com/licensing/about-licensing/virtualization.aspx would be a better resource regarding VM related Licensing questions.

     

    Sorry I couldn't be more help,

     


    Darin MS
    Wednesday, June 1, 2011 9:10 PM
  • The intricacies are things like the licensing of multiple instances of the same software license in enterprise environments.  But for an end user who has no access to software assurance the client EULA seems straightforward enough. 
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Wednesday, June 1, 2011 9:28 PM
    Answerer