7.9. Using Sysprep to Automate the Configuration of Virtual Machines
/usr/share/ovirt-engine/conf/sysprep/ directory. You can also create a custom Sysprep file and reference it from the the osinfo file in the /etc/ovirt-engine/osinfo.conf.d/ directory. These files act as templates for Sysprep. The fields in these files can be copied and edited as required. This definition will override any values entered into the Initial Run fields of the Edit Virtual Machine window.
/etc/ovirt-engine/osinfo.conf.d/, have a filename that puts it after /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties, and ends in .properties. For example, /etc/ovirt-engine/osinfo.conf.d/10-productkeys.properties. The last file will have precedence and override any other previous file.
/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 7.2. 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
7.9.1. Configuring Sysprep on a Template
/usr/share/ovirt-engine/conf/sysprep/ directory. For example, "<Domain><![CDATA[$JoinDomain$]]></Domain>" can be used to indicate the domain to join.
Important
Prerequisites
- The Windows virtual machine parameters have been correctly defined.
- If not, click Edit the Virtual Machines tab and enter the required information in the Operating System and Cluster fields.
- The correct product key has been defined in an override file on the Manager.
Procedure 7.13. Using Sysprep to Prepare a Template
- Build the Windows virtual machine with the required patches and layered software.
- Seal the Windows virtual machine. See Section 7.1, “Sealing Virtual Machines in Preparation for Deployment as Templates”
- Create a template based on the Windows virtual machine. See Section 7.2, “Creating a Template”
- Update the Sysprep file with a text editor if additional changes are required.
7.9.2. Using Sysprep to Initialize a Virtual Machine
Procedure 7.14. Using Sysprep to Initialize a Virtual Machine
- Create a new Windows virtual machine based on a template of the required Windows virtual machine. See Section 7.10, “Creating a Virtual Machine Based on a Template”
- Click the Virtual Machines tab and select the virtual machine.
- Click .
- Expand the Boot Options section, select the Attach Floppy check box, and select the [sysprep] option.
- Select the Attach CD check box and select the required Windows ISO from the drop-down list.
- Move the CD-ROM to the top of the Boot Sequence field.
- Configure any further options as required. See Section A.5, “Explanation of Settings in the Run Once Window” for more details.
- Click .

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.