@Tom-Elliott Thank you so much for your verification. I was a little panicked haha. Have a good day!

@Sebastian-Roth Thanks!

I’ve been having the same issue with the G8 ProBooks and have finally got one to image throught the NIC however I’ve been through many steps so I followed this guide
https://docs.fogproject.org/en/latest/reference/compile_ipxe_binaries.html
I then re-downloaded & re-installed FogProject from github.
PXE is noticably faster and so far so good.
Whether compiling and copying the ipxe worked or whether it was the re-install or a bit of both I cannot say.

@tom-elliott sorry! I meant last deployed date. Is there a way for me to see per host when it was? I am just looking to get an output of that via some sort of command line. I use Powershell currently with the FOG API.

@sebastian-roth It did not help. It still got stuck there. I think it was a version issue with the .fogsettings between 1.5.2 (old) and 1.5.9 (new) and the difference in Linux Distro. I will just move images and other settings and recreate the cert. Thanks for the help!

@Chris-Whiteley I finally had some time to work on the module and created a Start-FogSnapin function that can deploy a single snapin task.

See also https://fogapi.readthedocs.io/en/latest/commands/Start-FogSnapin/

@tom-elliott Thanks Tom!

@chris-whiteley said in API Help:

The only thing I can’t figure out is how to make that host be associated with a SnapinID. For instance, I want it to be associated with a SnapinID of 1. How can I do that?

While I haven’t tested lately I would think you should be able to create a snapin association like this:

curl -X PUT -d '{"snapins":[1]}' http://x.x.x.x/fog/host/33/edit

Assuming the host you want to associate the snapin (ID 1) to has host ID 33. Don’t forget the API tokens in the call.

@Chris-Whiteley The default for a current install of FOG is still 4.19.x series because that is the last / latest LTS version of the linux kernel. When the kernel developers release the next LTS version of the linux kernel (supposedly to be 5.10.x) then the FOG Developers will make that standard.

@sebastian-roth Thank you! I am going to give this a shot.

@george1421 Remember that during a capture, the $storage variable is defined, usually:

IPAddress:/images/dev

In the case of a deplooy the $storage variable is defined, usually:

IPAddress:/images

That’s why the checking.

If somebody wants to move the postinit into /images, then it should be symlinked, but that’s beyond our scope. That’s more of a preference .

Okay, I will dig into this. Thanks!

@Sebastian-Roth This is not a new branch, just an upgrade and move from Ubuntu to Centos 7 as it is more stable when upgrading. The only thing I can do as far as getting closer is to move this computer into the server room, but since it is a desktop that would be a little cumbersome. These are juniper switches.

For creating the schools’ base image, I use this same machine to do the work for all of them since it is pretty close to the “golden image” for each one. I am using this Dell Optiplex 7040. I create a legacy image (have some more impoverished districts with old machines) and a UEFI image.

I have not tried different iPXE binaries and I wasn’t aware that you guys wanted me to do a mirror port. I will try and work on this today if I get some time.

Thanks for the guidance.

Ok, let’s call it quits. I just pushed a commit to the fos repo to add this patch to our build of partclone and add the ignore_crc parameter back to the scripts.

Marking as solved.

@george1421 Thanks for the response. I think I might’ve actually figured it out. If you Legacy PXE boot, it errors out on a UEFI based machine. However, if you use the Network Stack PXE boot (UEFI), it will correctly boot. The DVD does work for both UEFI and Legacy. I don’t know why I didn’t think to try that first.

Thanks for the help!

@quinniedid said in FOG 1.5.6.2 Issues with Resizable image:

Sometimes the resize works and other times it doesn’t

Do you mean the same image sometimes resizes and sometimes not? We’d need the exact same information from your image (best to open a new topic) to look into this.

@george1421 You are the man! That was it! I made the changes and the menu came up. It was the - before the Windows 10 1809 - Office 2013 image

@Wayne-Workman Thanks for the response. I ended up renumbering the image name to include 01. through 14 and that did sort them. I appreciate the quick thinking and that fixes my issue!

@george1421 0_1535146823857_Surface_4.JPG