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 /un
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 /un
Hi,
OK, it sounds like you should create a VM set to a Windows OS via the
Webadmin (such as in edit). run with Run Once, choose initial run and check
the sysprep check box. Then you can set any configuration you want, run the
VM, seal with sysprep and reboot. After that create a template from the
> On 10 Nov 2020, at 12:30, ozme...@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 seal
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 usi
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.
M
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 /general
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
Il giorno lun 9 nov 2020 alle ore 15:43 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 , +Steve Goodman can
you please fix this?
>
> I
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 a
Il giorno lun 9 nov 2020 alle ore 10:22 ha scritto:
> Hi,
> I've cretated a template which has sysprep.
> Every document about sysprep says use "Attach Floppy" , but we know this
> function has been disabled/deprecated
> So, when i use Run One, attach windows cdrom and put in it definitions
> (d
11 matches
Mail list logo
