1. (I know not liked, but if pressing) hooks can probably handle this today by altering the floppy content on first run if getting this parameter from custom property.
2. in 3.1, this may be feasible via custom vm pay load - need to check, and not sure this will be via UI or only API.
[3. add this field in the product]
(In reply to comment #3)
> 1. (I know not liked, but if pressing) hooks can probably handle this today by
> altering the floppy content on first run if getting this parameter from custom
> 2. in 3.1, this may be feasible via custom vm pay load - need to check, and not
> sure this will be via UI or only API.
> [3. add this field in the product]
It is somewhat pressing, yes. I know we don't write hooks for customers but is there anything I can provide to them that will assist us in developing this hook?
(In reply to comment #4)
> What prevents the customer from modifying the sysprep template file RHEVM
We could do that but that assumes that the user will want every VM in the same OU. Sure, most of State Street's VMs likely will exist in a single OU but they want the functionality to specify the OU in the AdminPortal.
to solve as a part of the redesign of sysprep to allow to supply a custom config file
question is if important enough to be a named field (like timezone is), or just part of the custom config generic one
IIUC this is the required field that will be in the Add/Edit/RunOnce VM Sysprep section:
user will need to add something like:
Is that sufficient?
That is the correct syntax and sysprep.xml key. The user will need to define the OU in the proper DN sytax as highlighted in Comment 14.
Do you have a suggestion for UI label for this field?
Does "Active Directory OU" sufficient enough?
Is it possible to have the label shown as "Active Directory OU", then have the ? tool tip with the definition "This field will map to MachineObjectOU within Sysprep"
(In reply to Scott Herold from comment #18)
> Is it possible to have the label shown as "Active Directory OU", then have
> the ? tool tip with the definition "This field will map to MachineObjectOU
> within Sysprep"
Sure, added to the patch
Clear FailedQA in ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch (beta).
Due to XML parse errors in all XML-based sysprep templates, caused by missing ending tag, i.e., `<MachineObjectOU>$MachineObjectOU$<MachineObjectOU>`.
Windows then complains about invalid answer file during the sysprep process.
Verified in rhevm-3.5.0-0.11.beta.el6ev.noarch (vt3).
If given, Active Directory Organizational Unit value is passed to sysprep file as MachineObjectOU parameter and Windows guest is then joined to it.
Original problem was:
3. What is the nature and description of the request?
The sysprep answer file provided by RHEV-M needs the ability to specify an Active Directory OU for the VMs to join instead of the Windows default. This feature is supported by sysprep and I have it confirmed by a Microsoft representative.
4. Why does the customer need this? (List the business requirements here)
They have many OUs in their environment and would like the ability in the VM sysprep tab to specify which OU the VM will be placed in.
5. How would the customer like to achieve this? (List the functional
* The ability to specify an OU for a sysprep'd VM
6. For each functional requirement listed in question 5, specify how Red Hat
and the customer can test to confirm the requirement is successfully
* option in VM properties
* new field in sysprep answer file
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.