This is my PXE Advanced Menu, all of this is working:

:MENU
menu
item --gap -- blabla - PXE Boot Menu - blabla
item --gap --
item bootlocal Festplatte booten
item --gap Partition/Backup/Restore
item acronis2014 Acronis True Image 2014
item acronis2016 Acronis True Image 2016
item acronis2017 Acronis True Image 2017
item easeuspms EaseUS Partition Master Server 9.2.1
item aomeipau AOMEI Partition Assistant 6
item veeam Veeam Endpoint Backup Recovery
item --gap Password/Recovery/Restore/Repair
item erd2005 ERD Commander Windows XP
item dart7 DaRT 7.0 Windows 7 Server 2008 R2
item dart8 DaRT 8.0 Windows 8 Server 2012
item dart81 DaRT 8.1 Windows 8.1 Server 2012 R2
item dart10 DaRT 10.0 Windows 10 Server 2016
item --gap Destroy
item dban DBAN Darik's Boot And Nuke 2.3.0
item --gap --
item return <---
choose --default bootlocal --timeout 60000 target && goto ${target}
:bootlocal
sanboot --no-describe --drive 0x80 || goto MENU
:acronis2014
initrd http://${fog-ip}/iso/acronis2014.iso
chain memdisk iso raw ||
goto MENU
:acronis2016
initrd http://${fog-ip}/iso/acronis2016.iso
chain memdisk iso raw ||
goto MENU
:acronis2017
initrd http://${fog-ip}/iso/acronis2017.iso
chain memdisk iso raw ||
goto MENU
:easeuspms
initrd http://${fog-ip}/iso/easeuspms.iso
chain memdisk iso raw ||
goto MENU
:aomeipau
initrd http://${fog-ip}/iso/aomeipau.iso
chain memdisk iso raw ||
goto MENU
:veeam
initrd http://${fog-ip}/iso/veeam.iso
chain memdisk iso raw ||
goto MENU
:erd2005
initrd http://${fog-ip}/iso/erd2005.iso
chain memdisk iso raw ||
goto MENU
:dart7
initrd http://${fog-ip}/iso/dart7.iso
chain memdisk iso raw ||
goto MENU
:dart8
initrd http://${fog-ip}/iso/dart8.iso
chain memdisk iso raw ||
goto MENU
:dart81
initrd http://${fog-ip}/iso/dart81.iso
chain memdisk iso raw ||
goto MENU
:dart10
initrd http://${fog-ip}/iso/dart10.iso
chain memdisk iso raw ||
goto MENU
:dban
initrd http://${fog-ip}/iso/dban_2.3.0.iso
chain memdisk iso raw ||
goto MENU
:shell
shell ||
goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU
autoboot

i really would like to hear wayne speaking

Hi,

when using the “CopyProfile” bit in unattend.xml with Windows 10 1703 you may mention strange problems when creating new user profiles, therefore it’s needed to delete the following file and folders after deployment.

I solve this by adding the following lines to my SetupComplete.cmd:

I’ve added this to my setupcomplete.cmd:

rd /S /Q "C:\Users\Default\AppData\LocalLow"
rd /S /Q "C:\users\Default\AppData\Local\Microsoft\Windows\WebCache"
rd /S /Q "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache"
del /F "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat"

When this is done i can start Internet Explorer under every user again and Office 365 registration is functional.
This was the inital issue: https://forums.fogproject.org/topic/10210/windows-10-1703-image-with-strange-issue/21

Regards X23

@george1421 only using a filled advanced menu with a handful isos nothing more. sorry

@amjfrankenstein said in sub-menus on images page for deploying images?:

…out of date and rusty

If you rest you rust

Hi,

i really need to say i hate it without seeing it in action, brave new world!
no more comment.

It just feels like:

FOG! FOG! FOG!
@joe-schmitt

Regards X23

@tito026 said in Poblema al activar windows 10 1709:

Re: Windows 10 Pro OEM Sysprep & Imaging
Saludos.
Me gustaria pedir ayuda. Ahora usamos windows 7 y las desplegamos sin problemas. Ahora que queremos actualizar a Windows 10 Education x64 1709 modo Legacy tenemos problemas para activar los equipos, me devuelve el error 0xc0ea00a. Creo que tiene que ver con el archivo al que haces referencia en:

Hi,

you are on the wrong track, this reg file just imports a run command for a binary that changes the uuid in the eset agent db.
It’s nothing you need if you don’t install eset agent within your golden image. You can remove it.

But this will not solve your problem, it will not impact any activation stuff.

What kind of activation problems do you have?
Do you try to activate oem computers (with license in bios) with a key that you extracted from an preinstalled system from registry? If so you don’t have the real key, you need to read from bios and the usage of slmgr /ipk key and /ato to activate.

I need more information.

Regards X23

Hi,

is the server behind a proxy? Even when you have set a system proxy you also need to specifiy the proxy in fog settings, afai remember versions can only be polled if you have specified the proxy in the settings:

@tom-elliott am i right?

Regards X23

Hi,

if you say OEM license, do you have Win 7 OEM licenses or Win 10 OEM licenses?
(I talk about a sticker with a unique key)

If so you can add each key to its specific host definition in fog. the fog client will then activate with the entered key.
When you have your keys in the computers bios the way is different, let me know what you have i will explain then.

Regards X23

Hi Joe,

my collegue is italian and will do the translation into italian. How many is it?

Regards X23

I already imaged Surface 4 Pro, i’ve used the port replicator to boot them:

Afai remember i used them in legacy mode (don’t had uefi images at that point) but it’s possible that the current firmware does not support legacy anymore but ipxe7156.efi should boot them anyway in uefi mode.

But you can also use the usb nic adapter that was available with surface 3 pro’s:

It also supports pxe boot but could be hard to purchase one.

Do you already have a golden syspreped image? If not i would recommend to finish one of them then sysprep it, image it and deploy to all the others. Beware that you should remove the nic’s mac from all the imaged devices associated with fog’s hosts if you use the same dock or usb nic to image them.

Regards X23

@sunks you can activate, but you need the read out the key from the bios, i build a tool for this and this has been documented in this forum, let me find it.
Read this propperly: https://forums.fogproject.org/post/99211

I use my binary as a snapin.

Regards X23

The HP Stream do not have it’s own nic, the only possible reason for me could be the usage of the same usb nic or same usb dock that will offer the same mac to any of that streams. @jkoch what if you boot to the fog pxe menu after registering the first stream with a second one, is the menu telling you that this host is already been registered?

Regards X23

@sunks said in Windows 10 key after deployment:

@x23piracy

Thanks, i’ll check that

don’t forget reimaging is not allowed with OEM, but pssst i also do it

Regards X23

Hi,

this is not possible in the default firmware, you may can try if there is support for a freetz image that you can compile on your own. Afaik there is no support for the 75XX models for freetz: https://freetz.github.io/wiki/index.en.html

DNSMasq is maybe an option but i am not used to it, you can try to ask @george1421

Regards X23

http://www.windowsafg.com/
It’s always en-GB never UK!

Ok found it:

well done @Jaymes-Driver

Regards X23

Hi,

@abos_systemax said in Is it possible to image a client from USB, without the FOG server?:

Well, the title kinda states it already. We want to service a remote site with just a few machines. We’d like to use USB for this, is that possibile?

you mean devices that only have usb ports and no dedicated network port? If yes you should try usb nic that support network boot, this is maybe bios related regarding to the hw you are using.

Just imaging via a USB Connection is not possible.

Regards X23

@Nibor25 said in PXE Boot HP X2 210:

@x23piracy
That was the first thing that we have tried. Unfortunately there does not seem to be a option to enable Legacy.
Could you advice me how to enable legacy boot?
Thanks in advance,

Hi, i use it’s usb type c dock to have a wired network connection.
Goto the BIOS and set the following to legacy:

Regards X23

@Wayne-Workman i have tried disabling fogservice and creating a setupcomplete.cmd but it seems that it will never be launched, after login i can see that fogservice is still disabled.

I created it under C:\Windows\Setup\Script\SetupComplete.cmd
Microsoft KB let me now that SetupComplete.cmd will not been executed when using OEM Key, for this reason i removed the install key i used with slmgr.vbs /cpky and /upk but anyway SetupComplete.cmd is not executed.

Since that was not working i tried FirstLogonCommands in unattend.xml but even this is not working, i also do two registry tweaks with FirstLogonCommand, they work but setting FOGService to delayed-auto and service start not.

My last try was a unattend.xml that will autologon once the local admin i create with the unattend.xml file and placed a cmd script into Start Menu > Autostart to reenable FOGService but also this method even does not work.

Now i stuck:

• My SetupComplete.cmd does not seem to be executed for an unknown reason
• FIrstLogonCommands does not work to reenable FOGService
• AutoLogon from local Admin (unattend.xml) and a cmd script in Start Menu > Autostart not working.

Why should i disable FOGService before Imaging? the last thing before i get to sleep last night was to let the service enabled but with delayed start, after sysprepping and rerun on the same vm setup was running clean and after logon fogservice was started.

Is it really needed to disable FOGService before doing image tasks?

I am screwed

EDIT:

Something else i could find on the web:

I am using Windows Media Creation tool to get a windows 10 iso, we are using BIOS embedded or bought Windows 10 Pro OEM Licenses.
What can i do?

Regards X23

@THEMCV yes