Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Imaging OEM PCs

Answered Imaging OEM PCs

  • Monday, December 03, 2012 8:43 PM
     
     
    Sign In to Vote
    0

    I work for a Microsoft Partner and we're an MSP managing corporate networks.  I want to perform the following procedure when setting up new PCs for my customers, but am having problems determining whether this is a valid path:

    Format a new PC using a Windows 7 Volume disc

    Customize and sysprep this image with WAIK, but do not enter a product key

    Clone this image and deploy with WDS

    Enter the OEM key for each machine at the time of setup.

    I'm having some difficulty determine whether this is a valid path, especially as it pertains to a partner and their customers.  Any information (especially along with official statements from Microsoft) would be a huge help on this.

    Thanks!

     

All Replies

  • Monday, December 03, 2012 9:31 PM
     
     
    Sign In to Vote
    0

    I would recommend do live tests instead of waiting for hint. All procedures are described in Windows 7 Resource kit (MS Press, part of it is free)

    http://social.technet.microsoft.com/Forums/en/outlook/threads

    Rgds

    Milos

     
  • Monday, December 03, 2012 9:58 PM
     
     
    Sign In to Vote
    0

    Maybe I'm asking the wrong question.  I know that doing it that way will work, and that I'll end up with an activated copy of Windows at the end, but the questions is whether that is a licensing violation.

     
  • Monday, December 03, 2012 11:34 PM
     
     Answered
    Sign In to Vote
    0

    This is how I currently do it for our deployments (as the company is too tight to buy a VLK license).

    1. Install Retail/MSDN Windows 7 in Virtualbox virtual machine

    2. Modify installation as needed (install apps, customise settings etc)

    3. Using MDT 2012 U1 run a 'Sysprep and Capture' task sequence

    4. Deploy image using MDT 2012

    After deployment the installation is in an un-activated state,  we then just manually type the COA product key from the sticker into the activation and it works no problem.  As to whether this is a licensing issue I'm not 100%,  the old reimaging rights for Windows 7 weren't 100% clear,  the reimaging rights documentation freshly created for Windows 8 seem to say that this procedure is within rights.

    One little problem with this that we are now finding is that with Windows 8,  while downgrade rights are included for Windows 7,  no COA key is provided... not sure how we are going to tackle that one yet.

    Windows 8 reimaging rights

    This seems to apply here (?):

    Customisation of an OEM Image after Delivery

    The End-Customer does have a Volume Agreement

    • An organisation received a ‘clean image’ from an OEM supplier which is pre-activated prior to delivery and acceptance.
    • The OEM installs the ‘clean image’ and activates OEM Windows OS on each PC. This removes the requirement to perform any activation tasks in the deployment plan.
    • The OEM license allows the organisation to use the pre-installed image on the specific OEM PC to which it was assigned (non-transferable).
    • Upon acceptance of the PC shipment, the organisation utilises theWindows AIK toolset (7)/ Windows AIK Toolset (8) to customise the OEM ‘clean image’ based on the ‘Standard Corporate Image’. The AIK Toolset allows an organisation to create a new master image, which is then installed on the specific PC.
    • The organisation will have to adopt a systematic approach to directs their staff to unpack the all PCs and follow the same process to customise, save, and install a new master image on each PC.

    If the organisation wants to adopt Volume Licence customisation and deployment the following approach applies:-

        • The organisation has access to a Volume Agreement from Microsoft and has access to Volume Agreement Media viaVLSC
    • The organisation must ensure it first has a licensed and qualified operating system (OS) installed on each computer. This can be checked in the following article
    • The organisation’s Volume Agreement provides it with reimaging rights but only for reimaging the custom Volume Licence media image.
      • An organisation cannot use the Volume Agreement to reimage the new PCs with a custom OEM media image.
    • The organisation will then Activate the software Volume Activation(VA)
    • For volume activation, the organisation adopts the MicrosoftVolume Activation Management Tool (VAMT)
    • It is recommend to work with the OEM to create a CFI (Corporate Factory Image) that the OEM will use to install and activate Windows OS prior to shipping and acceptance. Alternatively, adopt a Master ‘Standard Corporate Image’ using Volume Agreement re-imaging rights using Volume Licence media via VLSC


    • Edited by mhouston100 Monday, December 03, 2012 11:37 PM
    • Proposed As Answer by mhouston100 Monday, December 03, 2012 11:52 PM
    • Marked As Answer by mjt9 Tuesday, December 04, 2012 1:21 AM
    •  
     
  • Tuesday, December 04, 2012 1:03 AM
     
     
    Sign In to Vote
    0

    Thanks for the confirmation.  It seems like I can at least do what I want to do and have it work from a technical standpoint.  I'd like to get a clear answer from Microsoft as to whether this is a licensing violation or not, but I guess that's not likely to happen.

    Thanks for the help, though.

     
  • Tuesday, December 04, 2012 1:10 AM
     
     
    Sign In to Vote
    0
    If you read through the page I linked to,  it basically confirms the new re-imaging rights allow you do do what your asking,  I think the major change is that in the past,  modifying an OEM image and then redeploying was not allowed,  using a full version was.  Now it seems you can pretty much do whatever you like as long as the media and key are legit.
     
  • Tuesday, December 04, 2012 1:22 AM
     
     
    Sign In to Vote
    0
    Okay, thanks.  I marked yours as the answer, but I think I need to call Microsoft to confirm.