Hi @Tom-Elliott
After moving from RC-2 to RC-4 the plugin, the WinPE image and the step that closes the task at the end of the WinPE flow all kept working. Only the Apache part needed a change.

With RC-4 the whole vhost sits inside FOG’s managed block, so my earlier Alias plus rewrite exception was gone and /fog/winpe_3400/wimboot started answering 308 (FOG’s rewrite rule sends it to the API). Instead of putting the exception back, I now serve the files from /winpe_3400/ (no /fog/ prefix), with an Alias and a <Directory> in a separate conf-available file enabled with a2enconf. FOG’s rewrite rule only matches /fog/, so it never sees these requests, and nothing in 001-fog.conf should need restoring after an update. The only change in the plugin is its WIMBOOT_HTTP_PATH constant.

Checked after the change: the Latitude fetches wimboot, BCD, boot.sdi and boot.wim from the new path (all 200), WinPE starts, and a full deploy on the Latitude 3400 and one on an HP with the normal FOS/Partclone flow both completed and closed their tasks.

@Valer I think we need to understand what this plugin is doing.

CSS isn’t something we’ve allowed to be injectable though it could be.

You can still use your own CSS but that’s more at the FOG Configuration -> FOG Setting -> FOG_THEME, but you would need to put it on your server in a location you type the path too here.

https://docs.fogproject.org/en/latest/development/plugin-development

This is a good toolkit for understanding how to build your own plugin.

@Valer Hi Valer,

You can see my tutorial on using Secure boot with Shim, and my thoughts on what 2.0 means for Secure Boot with FOG here: http://forums.fogproject.org/post/158170

@Sebastian-Roth Can I bother you with this quick question ^^^

@george1421 Great, thanks for the info!

@george1421 seems like in this post it is a similar interest they were implying by putting FOS on a bootable partition of the hard drive

https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/4

Hello,

Fix Members tab for accesscontol plugin and some display elements for site plugin (11807ac) : https://github.com/FOGProject/fogproject/pull/647

Regards.

@AUTH-IT-Center Subree is updated to be properly listed as Subtree

@AUTH-IT-Center fog has some hooks and events capable but those are relatively new and not quite as granular as I’d like to see them, though I suppose with the effort of 1.6 it may be worth while to try to find all the possible hooks/events (they can be either and/or both technically) as will as the attributes available for each one. That may help with the event notifications. I warn it does not exist currently.

@csa Did you had success making your own custom task type ?

@Bhav duplicate thread here: https://forums.fogproject.org/topic/17521/not-booting-to-pxe-uefi

@Tom-Elliott Apologies, I don’t know what went wrong there but somehow I got an incomplete version of your changes. git is a confusing beast to me :). I’ve now checked again that I’m running dev-branch and I can confirm that all the warnings have gone.

Thanks again.

@Sebastian-Roth perhaps I can achieve the same outcome with snap-ins?

I have batches of Ubuntu machines that I multicast image. I have a bash script in the image that essentially prefigures the machine but it currently need to be run manually as it require two user inputs unique to each machine.

The reason I wanted the IP of each machine was so I could write a script to SSH into each machine from my PC, run the script and populate the unique inputs from a CSV.

It’s not so clear to me the limitations of snap-ins - is this a correct use case?

@aviel1540 Sure you are welcome to build your own UI. The best of documentation we have you can find here: https://news.fogproject.org/simplified-api-documentation/

@TaTa FOG does not do SSO though you are invited to make it happen. Tell your company to get involved in this open source project, put one developer on this for a few weeks. 🙂

I changed the code to PHP and now it works, so I think it was something security related from the browser.