Posts made by Yeet

@sebastian-roth Fair enough. Out of curiosity, when I entered an IP for the DHCP server during FOG installation, what exactly did that do then?

I’m currently using a sonicwall for DHCP on my FOG server, but I’ll bet setting up a DHCP on a windows server to replace it. How do I change the IP of the DHCP server FOG is pointed at?

I know I set it during the initial FOG installation, but I can’t find anywhere I can change it.

@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

@sebastian-roth I tested on another machine, and it ran into the same issue with bzImage and init.xz loading slowly. I confirmed I don’t have this issue on my other FOG server using this same machine & bootfile that I’m testing with. What would you reccomend doing next? I’ve updated to the most recent kernel & have the most recent init files that I could find.

@sebastian-roth I’ll give that a shot. Do you think changing bootfiles will resolve this issue on certain models?

I am setting up a FOG server, and for some reason it takes a long time to load bzImage and Init.xz during tasks.

For example: I selected to run a full host registration & inventory, and before I can even enter the hostname it’ll say “bzImage… __%”. It will slowly count up to 100, and then it’ll say the same for Init, but it takes even longer. It does it during just about any task I run

I never had this issue on the other FOG server I’ve been using, so I’m not quite sure what is happening here.

Any help is appreciated

I built a Win10 Image on a 256 GB NVMe drive. Didn’t have any issues deploying images until recently. We had a mixup when ordering drives, and we ordered 250 GB drives instead. When I try pulling it down to one of our machines of the same model with a 250 GB NVMe drive, it gives me the following error:

Error trying to restore GPT Partition tables (restorepartitionTablesAndBootLoaders)

Is this due to the drive being 6gb smaller than the one the image was built on? Is there a setting I’m missing? I have the image set to single disk, resizable.

I made an image for a HP ProBook a while back, making sure to use /generalize during the sysprep process to avoid activation issues. Usually, this process has worked just fine on other devices. For some reason, this specific image is still pulling down the same activation key & saying that it’s already in use. As a result, we can’t activate windows on this specific device. I have ran this same image multiple times without error, and yesterday was the first time we ran into an activation issue.

It’s been a little over 2 months since I created it, so I’m not sure if the activation clock may be causing issues.

After doing some research, I’ve seen some suggestions to use the SkipRearm setting when setting up the answer file. Has anyone had success with this? It is supposed to bypass the activation clock resetting, but I’m not sure if that would just be indirectly reverting what /generalize would’ve done.

Any help is appreciated

We’re running into an issue now that we’re getting devices with no Legacy BIOS support. We have to switch the bootfile on the DHCP server almost every time we image a device.

I did some research, and saw that there’s some documentation for this exact issue:
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

The Problem is we use our SonicWall for DHCP, and there’s nothing listed in there about configuring this on a SonicWall.

Any help or even suggestions is appreciated. I’ve looked into this for quite a while, with no success.

@george1421

There is another way too, If you have a generic USB2 ethernet adapter we can pxe boot using a usb stick and let iPXE or FOS Linux manage the network drivers.

Can you please elaborate on this? I’m having a tough time understanding what you mean by that. I’d use a USB 2 ethernet adapter, then also use a USB stick?

@sebastian-roth We tried plugging in a StarTech USB->Ethernet adapter, but we just couldn’t get it to show up in the boot menu. Confirmed USB boot and PXE boot were enabled in the BIOS, but we still weren’t able to get it to show up in the boot menu. The model of laptop I was testing was a HP EliteBook 850 G7. We sell a lot of G7 HP devices, and we just noticed this issue now.

The only options that show up are IPv6 and IPv4 WiFi PXE boot, which I don’t have any experience with. I figured I’d ask here to see if anyone has any ideas or suggestions.

We’re running into an issue with some newer laptop models that don’t have legacy support, where we can’t find a way to PXE boot. There’s no ethernet port on the devices, so we’ve been trying USB->Ethernet adapters with no luck. Is there a way to set FOG up for WiFi PXE booting? Or is there another way to make this work?

Any suggestions are appreciated, I’m guessing I’m not the only one with this issue.