⁠10.3.3. Sealing a Windows Template

⁠10.3.3.1. Considerations when Sealing a Windows Template with Sysprep

A template created for Windows virtual machines must be generalized (sealed) before being used to deploy virtual machines. This ensures that machine-specific settings are not reproduced in the template.
The Sysprep tool is used to seal Windows templates before use.

Important

Do not reboot the virtual machine during this process.
Before starting the Sysprep process, verify that the following settings are configured:
  • The Windows Sysprep parameters have been correctly defined.
    If not, click Edit and enter the required information in the Operating System and Domain fields.
  • The correct product key has been defined in an override file under /etc/ovirt-engine/osinfo.conf.d/10-productkeys.properties on the Manager.
    If not, copy the default values for your Windows operating system from /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties into the override file, and input your values in the productKey.value and sysprepPath.value fields.
    ⁠

    Example 10.1. Windows 7 Default Configuration Values

    # Windows7(11, OsType.Windows, false),false
os.windows_7.id.value = 11
os.windows_7.name.value = Windows 7
os.windows_7.derivedFrom.value = windows_xp
os.windows_7.sysprepPath.value = ${ENGINE_USR}/conf/sysprep/sysprep.w7
os.windows_7.productKey.value =
os.windows_7.devices.audio.value = ich6
os.windows_7.devices.diskInterfaces.value.3.3 = IDE, VirtIO_SCSI, VirtIO
os.windows_7.devices.diskInterfaces.value.3.4 = IDE, VirtIO_SCSI, VirtIO
os.windows_7.devices.diskInterfaces.value.3.5 = IDE, VirtIO_SCSI, VirtIO
os.windows_7.isTimezoneTypeInteger.value = false
Report a bug