@fry_p Some options to try out here in this thread:

http://superuser.com/questions/747830/file-name-warning-for-c-program

@fry_p Can you delete it from command prompt (administrator)?

I create them in Virtual Machines, I have some batch files to automatically change certain things such as default user account picture and such.

It also adds ethernet/chipset drivers in a specific folder in C:\Windows\Inf so we always have network connectivity on first boot, which is necessary to load Snappy Driver Installer over the network for the rest of the drivers by launching the auto install batch file from firstlogon.cmd

@Jo2220

This is what I have for my ubuntu entry

set ubuntu-url http://192.168.1.155/0-LINUXUBUNTU15.10/ubuntu
set nfs-url 192.168.1.155:/mnt/INSTALLERS/ISOFILES/0-LINUXUBUNTU15.10/ubuntu/
kernel ${ubuntu-url}/casper/vmlinuz.efi
initrd ${ubuntu-url}/casper/initrd.lz
imgargs vmlinuz.efi boot=casper vga=normal root=/dev/nfs netboot=nfs nfsroot=${nfs-url} fetch=${ubuntu-url}/casper/filesystem.squashfs external-persistent locale=nl_BE.UTF-8 keyboard-configuration/layoutcode=be mirror/country=BE
boot || echo failed to boot
prompt
goto MENU

Also useful is

chain --autofree https://boot.netboot.xyz

Allowing you to boot livecds hosted online.

I use snappy driver installer and I drop chipset + ethernet drivers in a driverpack folder inside of windows/inf and it works fine. After setup it launches SDI over network and installs the rest of the drivers.

There’s other reasons why sysprep could fail, such as Windows Media Player service (or whatever it’s called) running or your windows grace period expiring.

@TomBagley This will most likely be due to the dhcp leases that are handed out allowing the other DHCP server to reach it before FOG has a chance.

@Sebastian-Roth It happens right after the first “Could not open net0” in the screenshot (third line in the original post of the screenshot)

@Sebastian-Roth I thought the clients only asked for manual TFTP information if there’s either a problem with the DHCP server (which would make little sense as it wouldn’t be able to reach this stage) or if there’s something fishy going on on the network (typically DHCP servers giving out the same options)

@melvinpaz It’s very odd that it asks for TFTP information if there’s only one DHCP server available.

To me this indicates some kind of network issue, I’ve only seen it when there’s multiple DHCP servers giving out the same options, confusing the client.

I could be way off base, but I think a packet capture might help us

https://wiki.fogproject.org/wiki/index.php?title=Tftp_timeout…#Troubleshooting

Trinity kit is very difficult to add to ipxe boot, I had to give up after trying several times because it would never work properly.

@TomBagley Considering you have to enter tftp server address, it is likely you have another DHCP server on your network (likely your modem), which might be interfering.

You seem to have two dhcp server on your network. Not that this necessarily causes the issue, but just wanted to point that out.

@Tom-Elliott It seems like mysql 5.7 broke a few things, but I’m guessing not enough to bother with this?

@Tom-Elliott On this note, would it be possible to add something similar for mysql or would it be wiser/simpler to simply fix the issues at hand instead?

@atarone I don’t know if ntfsfix is included in debug mode (guessing not), so assuming it’s not, boot up a linux distribution livecd, install ntfs-3g if it isn’t included yet and then try:

sudo ntfsfix /dev/sda4

And try again. If it still happens, then you can manually force the dirty bit to go away with

sudo ntfsfix -d /dev/sda4

It’s also possible that you simply have a checkdisk scheduled at some point.

You might also before doing all the above check the following registery key:

HKLM\System\CurrentControlSet\Control\Session Manager\BootExecute

This actually makes me wonder about the possibility of something similar to a task for imaging groups of hosts, but using multicast instead of singlecast.

Multicast session name could be the group name + incrementing number or something.

Did you uncheck default item for local disk?

@RipAU You can set those variables manually by for example creating something like:

:variables
set fog-ip youriphere
set fog-webroot /var/www/html
:start

Sometimes the code looks fine, but the structure is actually not filled in properly which causes stuff like this. I’m guessing something went wrong here :

item return return to previous menu
choose --default return --timeout 15000 target && goto ${target}
:wd

It’s probably formatted accidentally something like

item return return to previous menu
choose
 --default return --timeout 15000 target && goto ${target}
:wd

So expand the code box and double check all that.

@Tom-Elliott This is a capture of a VM with a fixed size disk of ~30GB (about 25 filled I believe?). I haven’t touched partition layout or anything, but perhaps it’s because of the snapshot?