Bug 1145999

Summary:	[RFE] Generate sysprep answers file with name matching the version of Windows
Product:	[oVirt] ovirt-engine	Reporter:	Juan Hernández <juan.hernandez>
Component:	RFEs	Assignee:	Shahar Havivi <shavivi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ilanit Stein <istein>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, gklein, iheim, istein, lsurette, mavital, michal.skrivanek, rbalakri, s.kieske, yeylon, ykaul
Target Milestone:	ovirt-3.6.0-rc	Keywords:	FutureFeature
Target Release:	3.6.0	Flags:	rule-engine: ovirt-3.6.0+ ylavi: planning_ack+ rule-engine: devel_ack+ mavital: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764	Doc Type:	Enhancement
Doc Text:	Feature: When attach sysprep floppy we use to call it sysprep.inf Windows expect sysprep.inf to old windows such as windows 98, new windows such as windows 7 expect the file name to be Unattended.xml	Story Points:	---
Clone Of:
Clones:	1146912 (view as bug list)		Environment:
Last Closed:	2016-02-10 12:55:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1146912, 1203929

Description Juan Hernández 2014-09-24 09:19:02 UTC

Description of problem:

Currently when using sysprep the engine generates the answer file always with the name "sysprep.inf". This is OK for windows XP, but newer versions like Windows 7 or Windows 2008 use an XML file and they expect it to be named "Unattend.xml".

Version-Release number of selected component (if applicable):

3.5

How reproducible:

Always.

Steps to Reproduce:

1. Run a virtual machine using Sysprep.

Actual results:

The file included in the attached floppy is named "sysprep.inf" regardless of the version of Windows.

Expected results:

The file included in the attached floppy is named "sysprep.inf" or "Unattend.xml" according to the version of Windows specified when creating the VM.

Additional information:

The issue can be avoided modifying the adding the following entry to the registry of the Windows machine before creating the template:

  HKEY-LOCAL-MACHINE -> SYSTEM -> Setup -> UnattendFile = A:\sysprep.inf

Comment 1 Giulio Casella 2014-10-27 16:38:13 UTC

If this issue could be fixed in future version, it would be great: it's not a blocking issue, but it's quite confusing.

Comment 2 Ilanit Stein 2016-01-27 10:03:09 UTC

Moving to verified based on BZ 1146912 comment #9