@Reuban1219 said in Running Fog Server To Image Different Devices Without Internet (Using Switch):

I downloaded the MSI installer in my windows XP …

I am not exactly sure the fog-client was used on XP much. That was before I joined into working on the fog-client. Though I would think it should work.

But, it keeps giving error of installation ending prematurely.

Can you be more specific on what step it ends and what the error message is? If you don’t get an error back you should use logging as suggested by George. Open a cmd as Admin and run:

msiexec /i FOGService.msi /quiet USETRAY="1" HTTPS="0" WEBADDRESS="x.x.x.x" WEBROOT="/fog" ROOTLOG="1" /L*V c:\windows\temp\foginstalllog.txt

Put in the FOG server IP or hostname instead of x.x.x.x. Upload that log file to a file share and post a link here.

Thank you. I understand the complexity issue and removing the DB manually is easy enough.

@george1421 thank you, i try to do this.
Really thank you!!!

Thankyou Fernando!

@Sebastian-Roth

Yes, sir! My apologies for not doing this sooner.

https://forums.fogproject.org/topic/14116/development-fog-not-capturing-image-partclone-update

@Sebastian-Roth @pete Tested a host with debug tasking. With the -A ""
argument it works fine, without it Cannot view from browser

When confirming your task you are presented three options for scheduling: Instant, Delayed, and Schedule Cron-style. It sounds like you want the last option.

@george1421

FOG onto Ubuntu running as a VM.

posting an update that it worked in the end. (somehow the VM i created as test used another SCSI adaptor and it didn’t play well)

The settings that are default for a Win10 x64 still needed secure boot to be turned off.

For those who might venture, here’s my settings for my clients.
c6256d12-e5ba-4d91-b883-b1e54550e56a-image.png
ed58e765-7d34-451a-a128-f5a13a30a316-image.png

Time for some NAC + Jumpcloud + Chocolatey fun

Also done in 1.5.x dev-branch…

@sjensen Yes, seems like those devices can PXE boot: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net.md

You’d need to install your FOG server using a command line switch to enable installation of ARM kernels: ./installfog.sh -A

If PXE booting is not working you might still be able to boot those using the USB boot method.

(warninig this will be a bit biased since you are asking on a FOG forum) Truthfully setting up FOG is pretty easy and is a solid foundation for pxe booting, even multi pxe booting. iPXE is a superior network booting environment as compared to syslinux or grub. With iPXE you can transfer the boot image via http, https, nfs, tftp, and sanboot.

In regards to converting your grub menus to iPXE, i have a tutorial on using FOG as a netboot server: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

In regards to uefi vs bios, you need the proper bootloader for bios and uefi respectively. This is the same requriement for whatever boot loader you use. For FOG the default one for bios is undionly.kpxe for uefi is ipxe.efi. Most uefi boot loaders end in a .efi extension. For bios/ufei coexistence we have a wiki page for setting up your dhcp server (Win2012 and newer, or linux) so dynamically provide the proper bootloader based on the target computer: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence If you have a soho or router dhcp server that doesn’t support dynamic boot files then you can always install dnsmasq on your fog server to supply the dynamic boot loader. Understand that fog and clonezilla are built on opensouce stack so these tutorials above can be reused for other applications (dnsmasq is dnsmasq, tftp is tftp and so on)

@george1421 A Merry Christmas and a Happy new year to you guys.

@Sebastian-Roth the upper case is a mistake, oops sorry about that. Search is working now thanks all. it was the search box that was not displaying, so i could not type anything in, just clicking the search magnifying glass (expecting a search box to open), of course with no words to search it couldn’t find anything

@george1421
No problem, anything to help the community.

Just to update everyone…
Decided to go with @george1421 on this one.
It was a full day of “switch PXEClient Settings, Deploy , switch PXEClient again, Collect and repeat” but it worked out well and I have all my images in FOG now.
Thank you all for the help and advice!

A quick look at https://www.php.net/manual/en/migration74.php makes me think there shouldn’t be too many issues, though without a code evaluation I can’t say for certain.

Here is a sanitized version of my unattend.xml file and how I call the sysprep. I used pretty much the same unattend.xml file with windows 10 deployments.

https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7

I might recommend that you build your reference image on a virtual machine so you can take snapshots to save the system state as important steps. This saves countless hours of having to start over from the beginning when something goes bad.

@chasosnature Pretty close… it’s nodeBB

@FredG said in How to update FOS?:

Ok I thought that the development of FOS was independent of the development of the FOG server.

Yes, correct.

You are on the right track with what you posted so far. We just try to ask because sometimes people head down a road that costs a lot of effort and is not needed. In your case I guess it’s quite a nice idea you look into generating your custom FOS initrds to be able to play with it. Two things I’d mention:

Best you use the versions we currently use as well to prevent from possible issues that might just arise when using newer ones that we have not tested yet. Find the version numbers here: https://github.com/FOGProject/fos/blob/master/Jenkinsfile#L12

Be aware there is a much easier way to modify existing FOS initrds: https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image#Version_1.0.0_and_up