Thank you so much

@Chris-Whiteley Just updated the truth table with the link to a 1.5.7 init file with partclone 0.3.13.

@ckasdf Have not had enough time at the beginning of April and lost track of this. As we are heading towards the next FOG version to be released in the next two weeks I am wondering if this is something we should take a look at. It’s only bug fixes we do now before the final release. As you still seem to use FOG 1.5.7 I would ask you to update to the latest 1.5.9-RC2 (it’s not out yet but I work on this and I don’t expect you to find this post until RC2 is out…) and we work on this from there. It’s not great to work “between” the versions.

@jhumpf Any news on this? What sort of task is this? Capture, deploy, multicast, other?

@jc35 said: Client updater works on Linux ? Really good question. I have not tried this myself I think. Not sure if it does. Will need to check.

@robbit Any news on this?

@TaTa I am wondering if you have any news on this topic or if we can mark this solved.

@Sebastian-Roth Hey Sebastian (and all other FOG devs and users out there) hope you and yours are staying safe and sound with whats going on in the world. I’d forgotten about this post myself I confess - I’ve been busy trying go setup our entire workforce across several sites to work from home. I know our service desk team would find this feature of great benefit as keeping reliable track of who was given a loaner laptop and when can be difficult without the right tool to do it. Excel sheets or even the ticketing system don’t manage this very well. But given whats going on just now for everyone its very much on the distant, nice to have when the worlds in a better place list. Stay safe everyone. Kiweegie.

@EduardoTSeoane Just wanted to see if you are still buried in work…

This is a work around, for a long term solution …ummm we must to think if this solution is for 1.5.X versions or get a final solution for 1.6.X and how can we do it XD Maybe the solution is create on fly the CSV file to export and import the data (I am thinking loud)

@george1421 i’m thinking we could have an “unregistered host” host and have it auto-register and auto-remove when the tasking was created/finished. that would also allow us to have a task to track in the gui.

@sgoodman Bump…

@sgoodman While this is a good point and I like the idea of a cleanup it’s not as easy as removing those options I am afraid. There is quite some code logic in the background that I would argue needs a cleanup together with this as well. Not sure if we should consider removing it all in a rush now. Sure we can just remove the UI part of it quickly. But all the rest would then stay in the code for way longer I suppose.

@Sebastian-Roth This is more by design. Typically snapins are one time run. If needed to rerun a while later, you can run it individually to the host needed, or you could task the host to run all snapins associated. Maybe something we can limit in the future, but I guess I need better understanding. Snapins run in queue. For example, if a host has 25 Snapins to install, it installs 1, 2, 3, etc… It will not install 25 at once. Now, based on the information, I believe the question here is about number of machines running snapins at once. Lets say you have 25 Machines to install Snapin 1, you want this to be limited? Right now the code doesn’t take into consideration the number of snapin tasks as a queued process. Hopefully this all makes sense. Thank you,

@markbam I started to implement that but need to push this further down the list. We need to focus on bugs of the core FOG code before that. Note to myself: I have saved a diff of the current work in my workspace.

@pa_fog_man I think we have a bit of confusion here (and the 390 is not helping with clarification). First let me say that the Dell’s will let you dynamically boot in the other mode without changing the firmware (where it gets its default value). You can do this dynamic switching from the F12 boot menu. The other issue with the 390s (I can’t speak for personal experience with the 390s, but we have 790s in our fleet) the 790s were the first generation to support UEFI mode. But as far as I know, the 790s don’t support pxe booting in uefi mode. The 7010s was the first generation to support pxe booting in uefi mode. To pxe boot on the 7010s you would have to enable the uefi network stack on the network adapter settings in the bios. Otherwise you would not get ipv4 and ipv6 entries under uefi on the F12 boot menu. Back on point. You MUST select the proper boot kernel for the target system bios mode (legacy/bios or UEFI). If you sent the wrong boot file to the system you will not see the FOG iPXE boot menu. for bios mode you can use ipxe.pxe or undionly.kpxe for uefi mode you can use ipxe.efi or snponly.efi The bold text above are the typical kernels to set for dhcp option 67. You can not mix the boot kernels. This isn’t a FOG issue, but rather a firmware one.

Couple of things to check: Is the original machine in BIOS or UEFI mode? Is the target machine in BIOS or UEFI mode? If both are in UEFI mode, you may have to manually add the boot option in the UEFI of the target machine.

@p4cm4n also, tried cmd and batch from sfx archives, specifically 7zip sfx maker which threw an error trying to run on my own machine and winrar sfx maker. Rar is crappier compression but oh well. One of those worked can’t remember which…but things like wifi configs using it didnt.

well, what i needed was the french keyboard for the registration/capture/deploy. I followed Quazz advice (General settings / keymap : azerty) and all is good now ! thanks :)