@christop said in Plugin Hooks Not Running at Sub-Site:

lab computers in the desired room and thus used to multicast the room

just a data point here. Only the master fog server “the one with the database” can multicast images. Storage nodes can not (unless something changed in the last few years). Storage nodes are basically NAS devices with a little programming.

Now we used the location plugin to create storage locations. We assigned the storage nodes to a location and then target computers to locations, so as the target computer boots it finds the storage node it should image from. But that won’t help with the multicast part because storage nodes can only unicast images.

I am confident I have ruled out NFS. I can now connect to the NFS from localhost and Ubuntu to /images & /images/dev without issue and all the permissions that come with it. The only thing failing now is FOG, any guidance would be great!

@rodluz
Problem solved - the disk with the image was damaged

@lmoysidis I’m not using fortigate but check out the following article: https://docs.fogproject.org/en/latest/installation/network-setup/proxy-dhcp/?h=
I needed to dynamically assign a boot file based on vendor class and dnsmasq did the trick!

@Tom-Elliott Thank you so much Tom, as always I appreciate your support and guidance.

I reverted back to a snapshot I had on the same version and it’s working as expected. Unsure how things got corrupted but I would say it’s safe to assume this is working unless others report the same issue.

@chevengur there is not enough information to help you in that picture. If we could see more of the error message that partclone threw (i.e. just above the top of your picture) we would know what happened. At the point in the script all we know is that partclone wasn’t happy.

@Tom-Elliott thx👍

To add to this, we’ve been imaging a variety of desktop and laptops to Windows 11 last week and we’ve had three occasions where FOG has imaged to a connected portable hard drive rather than the local hard drive. I don’t remember it doing this before.

My technicians are on the lookout and are trying to remember to disconnect portable drives ongoing before a deploy but has something in Windows changed recently? We’re on FOG Version 1.6.0-beta.2233

@Tom-Elliott can confirm, this does now appear to work in 1.6 - huzzah! @george1421 looks like your hard work has paid off and it will eventually be in the stable branch!

@george1421 No, they were in proper failover config and the options replicated between the scopes. But it’s all good now and that’s the important thing ❤

I tried reinstalling the Capone plugin, but that didn’t work.

I checked my other machines that show the fog.capone option and I manually added it in using the New iPXE Menu Entry option with the same values as my other machines. I haven’t tested if this is the solution yet. Here’s a screenshot of my values:
d4f5f292-a652-4796-ad66-2531d9920b01-image.png

@Tom-Elliott latest pull resolved the issue. Appreciate your help on this!

@Tom-Elliott no stress, with so many posts it’s normal to miss some 😉