@wayne-workman take your time, i thougth about that often but never made the request.
I think you are going to extend the fog install script for it?

@jj-fullmer working is work in progress (alpha), dev is RC’s (beta). So i don’t think so in working branch you will receive latest changes and/or code improvements.

@wayne-workman oh to unprecise…

look here:

talking about the fog clients custom logo:

This gets lost on updating, not the settings, but the custom file in filesystem path, you always have to copy it from the backup path back to its place. It would be really convenient if it could be kept.

../service/ipxe/filename.png

Check if current banner sha is same as default one, then skip keeping it, if different keep it.

Regards X23

Hi,

is it possible to add a client banner image migration code line to keep the pure file in filesystem if it’s not the default one? I would not except that someone names it exactly like the default but if we should keep it always but could be contrac productive if the default one should be updated anytime, a possible solution would be a file sizecheck or hash.

Regards X23

wierd, one single and easy question, when you try to network boot (legacy or efi) do you see the fog menu?

i am not sure but in the end of a deployment you will see a line in the shell like: expanding filesystem, this normally take some seconds or maybe 1 minute to finish depending on the drive, maybe you can look for this maybe it ends immediately or throws an error into the console.

Possibly my mind is sending me traps and i think about capturing where it also resizes the partition to its smallest possible size. Not sure

I capture with similar settings and all my images expand just fine, an example:

Only a thougth.

Regards X23

@julienl yes, sorry found their existense, didn’t knew about that versions. Sorry for that confusing stuff.

Regards X23

@psycholiquid isn’t this done typically for offline images?
https://technet.microsoft.com/en-us/library/hh825070.aspx

Means he needs to reinstall the os after that.

Maybe he’s searching for a way to integrate drivers into a living system?

Regards X23

@dingir erm no fog doesn’t use dd (why raw? space wasting)
Ever thougth about capturing it with fog itself? Yes it can

@psycholiquid his issue: https://forums.fogproject.org/topic/10828/deploying-an-image-to-a-target-machine

This thread can be ignored

Hi,

i would suggest to test both over netio: https://web.ars.de/netio/
It’s easy, one binary, can act as server and client, look at the syntax:

Speed issue can have several causes, so knowing the native speed would be a good information in first instance.
Even strong compression/decompression actions can hit the brake.

Please post your results

Regards X23

Hey,

i was remote on the system and we installed the current RC (switched to dev branch).
Helped him out with some sysprep lines, added to stop fog service, set it to disabled and so on.

Seemed to work well but he still has a problem with the dell’s 7050’s but i have the feeling we have that spanning tree problem like here:
https://forums.fogproject.org/topic/10512/dell-optiplex-7050-fails-to-pxe-boot

This is what he gets when trying an 7050:

The op will ask his network admin for a check, i suggested to connect fog and the client with a dump switch and then to the environment. This is not done yet.

The initial problem with the dell 7050’s isn’t solved yet!
@msaglioc99 any chance to give the thread subject a better name (subject) about the problem?

Regards X23

@george1421 @msaglioc99 what about your bios versions in the 7050, compare please.

the op told me that he has the problem with a dell 7050, while a Optiplex 9020 works, so i think it could be related to this already solved thread:
https://forums.fogproject.org/topic/10512/dell-optiplex-7050-fails-to-pxe-boot

@x23piracy said in Deploying an Image to a target machine:

is it possible to create a host by the webif without errors?

yes it is, he told me.

@imagingmaster21 https://i.imgur.com/Cn4PMcL.png

@imagingmaster21 if you have setup your dhcp to enable both (legacy & efi) you just need to disable efi for the vm and then network boot. (Look at the screenshot i posted).

Not possible, Virtual Box cannot boot pxe in efi, you have to enable legacy for image/deploy actions, after that you can enable efi again for the case you are deploying an efi image.

Sounds like there is an workaround maybe…:
https://forums.virtualbox.org/viewtopic.php?f=1&t=65463

Hello, one partial solution is to initiate ipxe.efi, from the EFI shell (can be done automatically with startup.nsh), the solution is not complete because at this point, ipxe is not capable of chainload another EFI executable, only some image types, like Linux kernels with EFI STUB, can be loaded, therefore cannot load SYSLinux (syslinux.efi), GRUB2 (grubx64.efi) or any other EFI executable, but is enough to boot any recent Linux distribution, WINPE (through wimboot, abother part of the ipxe project) and some other utilities (like memtest86.efi). The capacity to chainload another EFI executable is being developed for ipxe and syslinux. GRUB2 EFI is the only EFI loader with network capacity that I found to be able to chainload another EFI executable, unfortunately cannot initiate network access in most machines when executed locally (it works perfectly when executed from network). Best regards, Diego.

Regards X23

is it possible to create a host by the webif without errors?

Search is still not working for me (tried it 5 seconds ago):