@sebastian-roth Thanks for this reply.
I will try un inventory task to check bi-directional data exchange.
Luc.

@alomarh Well it depends on what version of linux you are using. This appears to be RHEL compatible OS.

You can restrict the NFS server in FOG to limit access to a specific subnet range. You can do this without the need of a firewall. Look at the /etc/exports file. In the share line it starts with a star ( * ) replace that with the subnet range you want to share to. Look up nfs and exports for the exact syntax. Its hard to limit NFS to a single port range. You can do it, but you will need to make some configuration changes. NFSv4 is the way to go, but FOG is not there yet. I did experiment with it and it works with a few changes to the FOG server and FOS Linux.

@Wayne-Workman Ok, right. Then toss it I would say.

@vtl.victor I am not saying it’s impossible to do. It just needs work and we don’t seem to find the time to work on this. Your quickest way to achieve what you want is capture/deploy an image at your FOG network site. Don’t let the deployed host boot into the OS (add kernel parameter shutdown=1 to that host). Then boot that same host up with Clonezilla (for example) and for taking a backup that can be deployed at an offline site on USB - no FOG server needed there - just the Clonezilla boot media and image on portable drive. (cross references: 1, 2, 3)

If that’s not what you want you need to dive into the details. Just quoting Junkhacker’s postfrom another topic here:

FOG image capture and deploy are multi-step processes. each are several commands that rely on scripts and programs in the FOG OS (FOS) and change based on what options you have selected. FOG images are not designed to be used stand alone. Using FOG images without a FOG server will require steps that were expected to be automated and there really isn’t a quick way around it.

So if you or anyone else is keen, you want to start looking at the commands to do this here:

Clear old partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2012 Apply new partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2041 Loop to do the restore: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2376 Finally call partclone deploy the image files one by one: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L760 Restore UUID information: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/partition-funcs.sh#L25 Possibly more things I have missed…

And that’s just the simple case without resizing partitions!

It’s all open source, it’s all yours!

@fernando-gietz thanks

@londonfog Just wondering out loud but if that python script can hit the FOG API, and register that new host and then select image deploy when the target computer boots up for the first time and it pxe boots, it will boot right into imaging. So if you already have the image defined, then you would create one curl api call to register the new server’s name and mac address with fog, then a second curl api call to deploy your image.

ref: https://forums.fogproject.org/topic/11184/api-powershell-create-host-and-deploy-task-script

@sebastian-roth Great job, the installation tests are looking beautiful today.

@sebastian-roth thanks for the information. Since everything else is running fine there has been no need to try the dev-branch. It’s good to know that it will be included in the next release.

Thanks, it’s done.

@zaboxmaster said:

I know about dban etc… just nothing seems to work

What exactly have you tried and what was the outcome/error?

Just a quick note: FOG is made up of several open source tools to also allow for wiping disks. BUT we only provide those tools and have no share in them producing any kind of report or proof for you. So we probably won’t be able to help you with that point.

@tom-elliott unicast fonctionne bien mais multicast non cela ne fonctionne pas en multicast j’ai toujours la même erreur comme tout à l’heure

@george1421 @Sebastian-Roth I just wanted to let you know that I moved to snapins and never regreted it for one second 🙂
It is indeed much more flexible and involves way less maintenance on FOG updates.

Thanks again!

bonsoir george, stp excuse moi de venir ce soir te poser ce problème,

je veux déployer mon image sur une machine physique mais cela ne fonctionne pas. voici l’erreur que je reçois.20210404_012630.jpg 20210404_012700.jpg

la marque de mon ordinateur c’est un dell latitude et en passant, mon serveur est sur une machine virtuel et j’ai connecté ma machine cible directement sur la machine physique qui abrite mon serveur fog sur virtual box. par quelle moyen savoir que ma machine physique est bien connecté à mon serveur virtuel???

@brakcounty said in Quick question about the tftp/ftp credentials:

The web ui login username is still fog and a password I set.

That is correct. Those are two different things. The web UI user has nothing to do with the fogproject service account (Linux).

@astrugatch I haven’t done anything on this yet.

@moderators would there be any issue with using a forums topic to host torrent files for a fog VM image?

@wayne-workman said in Fedora 33 and Ubuntu 16:

wants to get everything OS agnostic by replacing PHP components with NodeJS ones, getting the UI and API away from making native OS calls, so on.

I agree with this too. Node.js opens the door to running the FOG server on a lot more platforms than just linux. It WILL be a long road to get there (if ever). We do need 3-4 node.js new developers to step up and restart the FOG-too project to get things moving.

@george1421 @Sebastian-Roth Thank you very much for the recommendation I would try to integrate it into the database just for the trill of it, I may even try to edit the php to integrate it into the original system.
Thanks

The figures seem much more stable now, much less fluctuations. Thank you @Quazz !

@EduardoTSeoane It will be interesting to see how optimization works for you. With the size of your campus we may need to split the database from the FOG server to give the sql database more CPU time. We need feedback from large campuses like you have to help with performance tuning of FOG.