Topics created by Yeet

@sebastian-roth I appreciate the response. Unfortunately none of those options resolved the issue.

I spent some time reading through those articles you linked, and I saw a lot of suggestions for disabling DMA protection. I tried it out, and that fixed it for me!

@yeet See if the bios has a setting called mac passthru or something similar. That will passthru the built in mac address of the mobile device to make the network adapter generic and the computer unique.

Doesn’t secure boot use unique keys? Have you been able to boot with secure boot enabled on machines that you deployed the image to?

We have an “easy” solution for this. We are using a NAS (a Syno in our case) to store the images, and we enabled the recycle bin. When the image is overwritten by FOG, the old one goes in to the recycle bin of the Syno (#recycle). Depending on the filestore size(we have around 32TB), number of hosts, size of the images and the size of the recycle bin, you can have the “history” for a few days.
The images are renamed in the #recycle of the Syno(e.g. d1p4_1.img or d1p4_5.img) and if you need an older image, you just copy it back, and rename it.(e.g. d1p4.img )
We can go back in this way, for 5-6 copies, in your case it would be 5-6 days.
I hope it helps.

Well, first of all … I’m sorry for getting up this old post.

Secondly … I’ve been reading some posts on this forum … and I’ve found this one which I think it’s very interesting to be linked in here (not sure if you’ve linked it yet, but I’d say I can’t see the link anywhere).

After researching a little bit more about this topic … I’ve found this project … which not sure if it could be interesting also. What do you think? Could this make easier the process described in @george1421’s tutorial?

Thank you guys, and so sorry again because I’ve created a new topic instead replying in here 😞 maybe some mod can remove it 😄

@yeet Good you have found FOG’s cron scheduled taskings. That’s the way to go for what you are asked to do.

@yeet If you look at the very top of that wiki page it actually explains all of the arch types.

Type Architecture Name ---- ----------------- 0 Intel x86PC 1 NEC/PC98 2 EFI Itanium 3 DEC Alpha 4 Arc x86 5 Intel Lean Client 6 EFI IA32 7 EFI BC (EFI Byte Code) 8 EFI Xscale 9 EFI x86-64

Unless you think you might run across 1, 2, 3, 4, 5, 8 you probably won’t need to configure them. FOG Doesn’t have a iPXE boot loader anyway for those arch.

@yeet The concepts are covered here: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

You will want to edit the fog.man.reg script and comment out the sections you don’t want. It helps if you know linux bash scripting or can follow programming. The idea is for you to make your custom fog.man.reg file then patch FOS Linux every time it boots, replacing the FOG supplied script with your custom script.

You can download the current fog.man.reg file from the fog github site: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.man.reg

@yeet said in Setting up my 2012R2 DHCP server to handle UEFI and BIOS PXE boot, and I need some help.:

I’ve had ipxe.efi work 99% of the time, but there’s some models that only snp.efi and snponly.efi work on.

The issue is that those models having an issue with ipxe.efi use the same vendor class than the others and can’t be distinguished from the by vendor class identifier.

I am not very good with Windows DHCP server but in generel you’d setup a particular rule/policy for problematic clients using their MAC address to distinguish those from other machines.

@Yeet The FOG installer doesn’t ask for a DHCP server IP. Though it asks for router/gateway and DNS server IP to be used in the DHCP configuration (if you tell it to enable this service on the FOG server).

@sebastian-roth Thanks to your suggestions I took a deeper look at the host server I was provided for this project, and there was a lot of driver packages missing. Once I installed those drivers, everything loads at a good speed now.

In the end it was my mistake not looking over the host server my colleague prepared for me, but I learned a lot more about FOG in the process so it wasn’t all time wasted.

I appreciate the help though, sorry if I confused you there

@yeet said in Error trying to restore GPT Partition tables (restorepartitionTablesAndBootLoaders) on different sized drives:

Is this due to the drive being 6gb smaller than the one the image was built on?

Yes, if your Windows 10 is 2004 or a newer build and your are using FOG 1.5.9 or older. That’s because with those versions of Win 10 they put a new recovery partition at the end of the disk and we have updated inits that can handle this in the latest dev-branch version.

Is there a setting I’m missing? I have the image set to single disk, resizable.

That setting is correct but as mentioned above you need the latest inits. Manually download inits (64 bit and 32 bit) and put into /var/www/html/fog/service/ipxe/ on your FOG server. Rename the existing files as backup instead of overwriting!

Now you need to re-capture the image. Maybe even create a new image definition for this to not overwrite your existing image files as a backup. Assign the new image to the host you capture from and schedule the task.

This image captured with the new inits should deploy to devices with smaller disk fine. If not, let us know here.

@yeet said in UEFI and Legacy Bios coexistence with SonicWall DHCP:

Problem is we use our SonicWall for DHCP

Yes this can be a problem if your SonicWall doesn’t support dynamic boot options. The quickest and most direct route is to install dnsmasq on your FOG server to supply only the pxe boot information. Your sonicwall will supply all other dhcp settings except pxe booting.

I have a tutorial on how to add dnsmasq in about 10 minutes to your FOG server here:https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

If your pxe booting computers are on a different subnet than your fog server, you will need to update your dhc-relay/dhcp-helper service on your subnet router. Add the fog server as the last dhcp server in the helper service. Then everything will just work. If everyone is on the same subnet then just install dnsmasq and it will work.

@yeet The startech adapter is not supported by your HP firmware.

So that startech adapter is an external usb to ethernet adapter, right?

Since the HP uefi firmware doesn’t show that startech adapter as bootable, the built in PXE roms will not work. So instead of using the onboard PXE roms, we can load FOG’s iPXE from a usb flash drive. Once iPXE is loaded then imaging happens normally.

How the boot order goes is this:
(UEFI) PXE ROM -> downloads and launches iPXE -> downloads and launches bzImage (FOS Linux).

So if the pxe roms don’t work we can just launch iPXE from a usb flash drive and hope that iPXE has the drivers for the nic built in.

If iPXE won’t configure that startech adapter, then you can skip iPXE and just load FOS Linux on the usb stick and not use iPXE.

The reason why I said USB-2 network adapter is that the older the adapter is the better the chance that both iPXE and FOS Linux will have a built in driver for it.