Cant get Sysprep to insert product key in Win2016 guest on RHV 4.3
I am trying to create a basic Windows server 2016 template in RHV 4.3 . I've installed the OS from the Windows DVD, and installed all the RHV tools, and drivers. Then I do a sysprep on my windows VM and make a template from it. I'd like to inject the product key when the template is cloned. I thought if we define the product key in /etc/ovirt-engine/osinfo.conf.d/10-productkeys.properties. with something like this: # Windows2016x64(29, OsType.Windows, true); os.windows_2016x64.id.value = 29 os.windows_2016x64.name.value = Windows 2016 x64 os.windows_2016x64.derivedFrom.value = windows_2012R2x64 os.windows_2016x64.cpu.unsupported.value = conroe, penryn, nehalem, opteron_g1 os.windows_2016x64.sysprepPath.value = ${ENGINE_USR}/conf/sysprep/sysprep.2k16x64 os.windows_2016x64.productKey.value = MY-WIN-PRODUCT-KEY That it would insert the product key when we tick the "Cloud Init / Sysprep" box on the run-once dialog. Now, I know this is semi-working, because all the other things I define in the run-once dialog after clicking sysprep works: Admin password, hostname, etc. But NOT the product key! I have even tried hard coding the product key in the sysprep.2k16x64 file and no luck. What am I doing wrong here? *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Solutions Architect* | NA Commercial Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>
Dear Lynn Dixon, This is a known issue where Microsoft's sysprep tool is only supporting the Unattend.xml file name whereas Windows setup is mainly supporting the Autounattend.xml file format which is inconsistent, but by design. One workaround is to add the following to the configuration after the product key setting in your example: os.windows_2016x64.sysprepFileName.value = Autounattend.xml Then the installation will work, but afterwards you will need to remove this line if you want the sysprep oobe to work. I hope this helps. With Best Regards. Steven Rosenberg. On Fri, May 22, 2020 at 6:14 AM Lynn Dixon <ldixon@redhat.com> wrote:
I am trying to create a basic Windows server 2016 template in RHV 4.3 . I've installed the OS from the Windows DVD, and installed all the RHV tools, and drivers. Then I do a sysprep on my windows VM and make a template from it.
I'd like to inject the product key when the template is cloned. I thought if we define the product key in /etc/ovirt-engine/osinfo.conf.d/10-productkeys.properties. with something like this:
# Windows2016x64(29, OsType.Windows, true); os.windows_2016x64.id.value = 29 os.windows_2016x64.name.value = Windows 2016 x64 os.windows_2016x64.derivedFrom.value = windows_2012R2x64 os.windows_2016x64.cpu.unsupported.value = conroe, penryn, nehalem, opteron_g1 os.windows_2016x64.sysprepPath.value = ${ENGINE_USR}/conf/sysprep/sysprep.2k16x64 os.windows_2016x64.productKey.value = MY-WIN-PRODUCT-KEY
That it would insert the product key when we tick the "Cloud Init / Sysprep" box on the run-once dialog. Now, I know this is semi-working, because all the other things I define in the run-once dialog after clicking sysprep works: Admin password, hostname, etc. But NOT the product key!
I have even tried hard coding the product key in the sysprep.2k16x64 file and no luck.
What am I doing wrong here?
*Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Solutions Architect* | NA Commercial Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>
participants (2)
-
Lynn Dixon -
Steven Rosenberg