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

I’m going around replying to all these old Docker request threads so people can try out my work. Check out my thread here:

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

and provide feedback in the comments.

the actual github repo is here:

https://github.com/88fingerslukee/fog-docker

I’m going around replying to all these old Docker request threads so people can try out my work. Check out my thread here:

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

and provide feedback in the comments.

the actual github repo is here:

https://github.com/88fingerslukee/fog-docker

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👍

@Tom-Elliott What’s the difference between the full and quick registration processes then? because AD join exists in full, but not in quick…

@Tom-Elliott Cheers, works as expected now!

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

Thank you!

Ok, nevermind, did the git thing, got it working, cheers 🙂

@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!

@Tom-Elliott cheers - looks like someone changed working branch in 2019 to add hdbios, and it’s not something that’s in the dev branch either!

I think I have the same problem and I want to be sure of exactly what I need to do (I don’t know if there is a step-by-step tutorial…).

I boot with a USB-C network adapter on an HP Elitebook. It finds FOG, I have the menu, I choose to deploy an image, and then I get this error message:

IMG_20251106_162705.jpg

Is this the problem in question?
If so, what exactly should I do? I see (link @FlorianLenz ) that I need to replace two files with the new ones, then run the .sh. But isn’t that dangerous for other network boots?

Thank you in advance for your help.

@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 ❤