This are The Option I want to set with API after creating the Host in FOG:
cdda90c8-0a3b-4a5d-a7f4-2cebaf2e81d5-grafik.png

After Imaging, Snapins wont be installed automaticaly. Is there a Task missing?
For some Reason i get this Message in the fog.log on the client.

20.05.2025 11:10:48 Middleware::Response No snapins

761870a9-1d3b-4e54-91cd-680a5fa57396-grafik.png

20.05.2025 11:10:48 Middleware::Communication URL: http://10.0.96.10/fog/management/index.php?sub=requestClientInfo&configure&newService&json 20.05.2025 11:10:48 Middleware::Response Success 20.05.2025 11:10:48 Middleware::Communication URL: http://10.0.96.10/fog/management/index.php?sub=requestClientInfo&mac=00:2B:67:99:C6:BC|58:EF:68:E6:5D:73|F8:AC:65:E2:94:65|F8:AC:65:E2:94:66|FA:AC:65:E2:94:65|F8:AC:65:E2:94:69&newService&json 20.05.2025 11:10:48 Middleware::Response Success 20.05.2025 11:10:48 Middleware::Communication URL: http://10.0.96.10/fog/service/getversion.php?clientver&newService&json 20.05.2025 11:10:48 Middleware::Communication URL: http://10.0.96.10/fog/service/getversion.php?newService&json 20.05.2025 11:10:48 Service Creating user agent cache 20.05.2025 11:10:48 Middleware::Response Invalid time 20.05.2025 11:10:48 Middleware::Response No Printers 20.05.2025 11:10:48 Middleware::Response Module is disabled globally on the FOG server ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response Success 20.05.2025 11:10:48 HostnameChanger Users still logged in and enforce is disabled, delaying any further actions ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response No snapins ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response No Printers ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response Success 20.05.2025 11:10:48 PowerManagement Calculating tasks to unschedule 20.05.2025 11:10:48 PowerManagement Calculating tasks to schedule ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Client-Info Client Version: 0.13.0 20.05.2025 11:10:48 Client-Info Client OS: Windows 20.05.2025 11:10:48 Client-Info Server Version: 1.5.10.1655 20.05.2025 11:10:48 Middleware::Response Success ------------------------------------------------------------------------------ 20.05.2025 11:10:48 Service Sleeping for 133 seconds

Greez
Chris

@Faurel ok good that looks like a clean dhcp process. It would be helpful to have the pcap file in my hand, but you want to expand the OFFER packet. The OFFER packet you can tell from the Info column.

In the packet you may need to expand the dhcp section. You should see the image similar to below. What is important is the next server IP address should point to IP address of your fog server. and boot file name should be ipxe.efi. You see in this example that the boot file name was not given, this is the error with this packet. The next server and boot file are in the ethernet header. This is the legacy bootp pxe section.

The next place you need to check is the dhcp options below. You should see dhcp options 66 which should be the IP address of the fog server and dhcp 67 should be the boot file name of ipxe.efi. In this picture this packet is also in error since the dhcp server is not sending out all of the pxe booting info. So if your offer packet looks like this you have a problem.

Screenshot from 2025-05-07 17-14-20.png

Any luck clearing up this error? Running into the same thing now setting up a separate storage node location(still local). I get this when trying to deploy an image.

This tutorial will give you a good general overview. https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Since you are talking XP, then you are also meaning bios firmware. For bios you can use a utility called memdisk.

https://forums.fogproject.org/post/142041 step #18. The memdisk program is only supported under a bios based computer. If you have uefi there is a different process. There are some limitations with bios mode, your iso file MUST be less than 2GB, this is a limitation of a 32 bit bios.

@Pingu Ok, i find out that my /images was a little bit bugged and got my snapshots in dev folder with the mac address as name folders, i moved them into /images and renamed them with the image name i configured on the Web Interface and it runs !!
Hope this will not happen for the next snapshots.

@tatanas Let me ask why are you renaming the host in the windows UI? Do you not know the actual name of the system at imaging time?

Second question: are you using the fog client service at all?

@sideone said in HyperV / Win 11 /Fog:

@dejv Ah, came here to say secure boot! Nice one.

Thanks @Tom-Elliott and @sideone for your replies 🙂

@fogcloud Hello,

Thanks for the info. I tested the cloning after modifying the nfs.conf file. It doesn’t work. I haven’t found any specific resource on this subject.

Is this the modification that was made?

/etc/nfs.conf

[nfsd] port=20048

Sincerely, Axel.

@george1421 post can be marked as solved.

Do I do that or is this done by a Moderator?

@JJ-Fullmer

I saw this a while ago! Pretty impressive. Right now, we’re working to integrate the FOG API into Oracle NetSuite, but I do use Powershell quite a lot as well and could definitely see a benefit here. I will check it out.

Thanks,

@danieln said in Using Snap Ins to run scripts post imaging...?:

@JJ-Fullmer Thanks for the reply! This is helpful.

I feel like maybe the best way to go about it is to assign the Snap In to each host. Just to confirm, this will deploy the Snap In after each time that host is image, regardless of which image it receives?

Yes that is correct, unless you specify otherwise (I think that’s really only available in the api though) the standard operation is to queue all assigned snapins to deploy after an image task

I’m also thinking of separating my inventory into FOG Groups by computer model and then assigning the Image Associated with it and Snap Ins at the group level.

Is this QC check also installing and or checking drivers? You could also use postdownload scripts to install drivers and have just 1 image that is universal and the drivers are injected and installed during sysprep specialize phase. Takes some setting up but works very well, see https://docs.fogproject.org/en/latest/kb/how-tos/post-download-scripts/?h=post

Also, if you wanted to create groups based on the model in the FOG Inventory you could build that out pretty quickly with my FogApi powershell module ( see my signature)

Something like this would get you a list of all unique model names you have in fog, this example uses is for 1.6 but should also work in 1.5.10.x
It also doesn’t include the initial api connection bits.

#get all your fog hosts with full details $allhosts = Get-FogHosts | % { (Get-foghost -hostID $_.id -ea 0)} #get the sysproduct field from the inventory of each host, and get the unique entries only $uniqueModelNames = ($allhosts).inventory.sysproduct | sort-object -Unique #list the model names in the shell $uniqueModelNames

There may be some additional filtering to do here depending on your inventory (like HP sometimes has slight differentiations of a model) but if that list is what you want your groups to be

$uniqueModelNames | Foreach-object { $jsonObj = @{ name = $_; description = "Computers that are of the model $($_)" } #I have a pending issue for creating a simple New-FogGroup function new-fogobject -type object -coreObject group -jsonData ($jsonObj | convertto-json) }

Then you’d set the membership of the matching hosts

#loop through the model names you created groups of by name $uniqueModelNames | Foreach-object { #get the group name and the matching group object $groupname = $_; $group = get-FogGroupByName -name $groupName; #find any host that is the given model and loop through them $allhosts | Where-object { $_.inventory.sysproduct -eq $groupName;} | Foreach-Object { #set the group association/membership required fields $jsonGroupData = @{ groupID = $group.id hostID = $_.id } #create the group membership association New-FogObject -type object -coreObject groupassociation -jsonData ($jsonGroupData | convertto-json) -ea 0; } }

Then you can go in the Fog web gui and assign hosts to each image. This can also be done in the api, but I just don’t have time to work out an example for that.

Also note that groups are not persistent config containers. Group membership sticks around, but it’s meant to be used as a bulk setter. If you set an image in a host it will set it on all the hosts in the group. But if you go change the image on 1 host in the group, it doesn’t auto change back, nor does it auto set when you add it to a group. There is a plugin that changes this behavior called persistent groups, but using it as a bulk setting and as a simple container/organizer of hosts is usually sufficient as you get into things more and more.

@Tom-Elliott I was able to post it just now, so whatever you did seems to have worked!

Thanks!

@theyikes Why do you need to reset it to the original installation state repeatedly?
How to do that is in the wiki here https://wiki.fogproject.org/wiki/index.php/Uninstall_FOG (that doc isn’t yet migrated to the new docs site)

I’m not sure why you’re wanting to start the server side fresh though.

The general idea is

Create Fog Server on a linux vm/machine that has enough storage for the OS images (not isos, captures of install states) Setup a different VM with the OS as ‘golden image’ (With windows you need to utilize sysprep) Register that VM as a host in FOG and capture the image. Deploy the image to as many other hosts as you desire

See also :

https://docs.fogproject.org/en/latest/capture-an-image
https://docs.fogproject.org/en/latest/deploy-an-image
https://docs.fogproject.org/en/latest/intro

@george1421
In addition to this topic
I have it working with FOG version 1.5.10.41 (dev version)
Kernel 6.6.34
Init 2024.02.3

stable (also with latest kernel/init) is not working.