Creating a VM image

When generic VM image is created.  Should we activate Windows on the VM or leave it inactivate?  if we do, will syspred take it away?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Channeler 1 year ago
Red Belt

Nope, do not activate Windows in your VM.

The activation is done from the Answer File XML, with a KMS Server, Multiple Activations Key- MAK - or Stand Alone license key.

  • We used to do it as well. However, we installed Windows enterprise on the image. Put our KMS key on the answer file, and somehow after imaging, it became Windows Pro for workstation. Checking the license key, it is suitable for all version of Windows 10. Now sure what is going on now. - jzhu 1 year ago
    • the activation key is the one that determines the Windows version.
      Are you sure your Devices are actually contacting your KMS server?
      They could be unable to contact the KMS serve and falling back to Microsoft Servers.

      PLUS double check your license key, compare that to:


      There isn't something like "a key suitable for all versions".
      Each Win10 version has it's own unique KMS key. - Channeler 1 year ago
      • I used slmgr.vbs /dli and it showed it connected to the KMS server. That is weird then, when I connect to the Microsoft license site, doesn't matter which version I click, it always shows the same key. - jzhu 1 year ago
Posted by: Hobbsy 1 year ago
Red Belt

If you are using a vm image to capture an image for your SDA, you will still need to Sysprep before you capture

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ