Thanks for response, I've rad this docs several times. If you check "7.9.1. Configuring Sysprep on a Template" it says "Attach Floppy", but there is no Floppy options. I've figured out something. If i use only initial boot sysprep enable option, after booting there is no change but i can see addtional cdrom device that has unattend.xml file

Hi, We removed the floppy option and added an additional cd rom that contains the Unattend.xml file. You can still use the Unattend.xml file from the additional CD ROM in order to seal the OS via the sysprep tool. The floppy drive was removed because it is outdated technology. Thank you for your enquiry. With Best Regards. Steven Rosenberg. On Mon, Nov 9, 2020 at 4:50 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno lun 9 nov 2020 alle ore 15:43 <ozmen62@hotmail.com> ha scritto:

...

Thanks for response, I've rad this docs several times.

If you check "7.9.1. Configuring Sysprep on a Template" it says "Attach Floppy", but there is no Floppy options.

+Arik Hadas <ahadas@redhat.com> , +Steve Goodman <sgoodman@redhat.com> can you please fix this?

...

I've figured out something. If i use only initial boot sysprep enable option, after booting there is no change but i can see addtional cdrom device that has unattend.xml file

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/T4OQOOU277CKIX...

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA <https://www.redhat.com/>

sbonazzo@redhat.com <https://www.redhat.com/>

*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2XDTRF5ILEYJLQ...

Hi, You could use reboot. The idea of sealing is that one sets say the time zone differently via run once, runs the VM, verify that the Unattend.xml file does have the selected time zone, run the sysprep with generalize and reboot and upon rebooting the OS should be set to the proper time zone. Maybe you can clarify what you expect from sysprep. With Best Regards. Steven Rosenberg. On Tue, Nov 10, 2020 at 10:43 AM <ozmen62@hotmail.com> wrote:

Hi, I've edited osconfig 00-defaults.properties and sysprep.w10x64 files After sealed w10 by using "sysprep /generalize /oobe /shutdown" command i'm using run ones/initial boot/sysprep But windows passes the process and booted like a new machine. If i sysprep the template like ""sysprep /generalize /oobe /shutdown /unattend:D:\unattend.xml" and run the vm with sysprep option, it takes and applies only few options like create username not joindomain or productkey. Is there any proper guide to do sysprep on oVirt? By the way i've already red official guide Thanks for help _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/46DII2GF2GJ5JP...

On 10 Nov 2020, at 12:30, ozmen62@hotmail.com wrote:

thanks for reply, I've made a template W10 and sealed with sysprep generize. After now, we want to use this template for new user vms. For example, a user wants a vm for personnel usage. I create a new vm from template which sealed. after creation, we want to customize this vm for the person by using sysprep. Change Windows pc name, join domain and assign to specific OU

you can see the resulting unattend.xml, that’s all that we do, if windows is not happy with it you’d need to dig into logs if you modified the template(and even if you didn’t, but it still doesn’t really work) you would have to check windows what’s failing. They keep changing the options and behavior between versions way too often and we don’t have automated tests for each and every sysprep option, so it could be that the particular setting in a particular windows version doesn’t work correctly. Thanks, michal

_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/N5BF5NNEW7CQWA...

H, I might have found a solution. After your reply, i've tested reboot option . It does not work normally But, if i seal vm in audit mode, these steps works; - boot vm "run ones" mode and sysprep enabled - run sysprep like this "C:\Windows\System32\Sysprep\sysprep.exe /oobe /generalize /reboot /unattend:D:\Unattend.xml" after reboot vm will be configured as in Unattend.xml whis is made by ovirt-engine as we configured in osconfigure and syspre.w10x64 files. This is the only way i've 'found for now. The key thing is showing the unattend.xml file whic is in virtual DVDROM Drive. Windows caches xml file for using next reboot. I'm not sure but it can cause security issue if this files be cached in windows permanently. I'll check this out.