@george1421 When I renamed refind.efi to refind_x64.efi, it worked as intended. Thank you for your help, I really appreciate it.

@sebastian-roth I haven’t been able to find a solution in the forums. When will FOG support secure boot? We need this to happen, or we will have to stop using FOG altogether.

@sebastian-roth I appreciate the response. Unfortunately none of those options resolved the issue.

I spent some time reading through those articles you linked, and I saw a lot of suggestions for disabling DMA protection. I tried it out, and that fixed it for me!

@sebastian-roth I appreciate the response. Unfortunately none of those options resolved the issue.

I spent some time reading through those articles you linked, and I saw a lot of suggestions for disabling DMA protection. I tried it out, and that fixed it for me!

@sebastian-roth I appreciate the response. Unfortunately none of those options worked. It’s weird, I was able to do a full host registration last week, but now it won’t even do that. I can get to the FOG menus just fine, but any time I run a task such it’ll get stuck trying to load either bzImage or init.xz.

It really is looking like it’s an issue with these g8+ HP ProBooks. Hopefully there’s a fix found eventually

I am attempting to capture an image, but for some reason during the PXE boot process it’s getting stuck at “bzImage… 34%”. I’ve tried rebooting multiple times & even recreating the capture task to no avail. It will either get stuck at bzImage or Init, and it always says a different percentage.

That’s when I have a capture task active. When I don’t have a capture task active, I’m able to boot into the FOG menu just fine. Any ideas what could be going on here? I captured an image a few days ago with no issue, and I’m updated to the latest kernel.

The PC I’m try to capture from is a HP 450 G9 ProBook, and I’m using the snp.efi bootfile.

@george1421

If you are sharing a usb network dongle between them then that might be the problem.

Well, that’s exactly the problem. I hadn’t even thought of that as a possibility. I appreciate the response

I ran a full host registration for an EliteBook 850 G8, which worked fine. When I pxe booted a different EliteBook 850 G8 fresh out of the box, it came up saying it was already registered. It displayed the name of the device that I had just registered previously.

I know for a fact I have never registered this new device, so why is it showing up as registered in FOG? When I was at a different organization a few years ago, our FOG server never did this. From what I remember, it looked at the MAC of the device when registering. Is this no longer the case? Or am I missing something?

I’ve just finished testing with an official build, and I was able to capture and deploy a Windows 11 image with SB disabled.

Here’s how I did it:

• When building an image, install Windows 11 with Secure Boot enabled - this is the only time when SB will need to be enabled

• Go through process of building the image & sysprepping

• Once you have completed the sysprep process, you can turn off secure boot

• Set up capture task & capture your image

• From here, you are able to deploy the image to machines with secure boot off

Just figured I’d make a post because I know a lot of people were worried about this (myself included). I’m still testing, but so far I’ve been able to successfully deploy the Windows 11 image with secure boot off to multiple devices (All HP so far). If I run into any issues I’ll post them here, but so far it’s looking promising.

@sebastian-roth I haven’t been able to find a solution in the forums. When will FOG support secure boot? We need this to happen, or we will have to stop using FOG altogether.

@eduardotseoane Would you be able to explain what you did in detail?

I’d like to stay with FOG as well, but if I can’t get it to work with Secure Boot I’ll have to move to a different product completely

@sebastian-roth Would I just need to back up the /images folder, or are there other components that would need backing up as well?

I’ve been tasked with setting up nightly image captures for a simple backup of user machines. I know, not a very practical or clean solution, but the decision wasn’t up to me.

When I capture an image, then capture again, is there a way to go back to a previous capture? Here’s the scenario I’m thinking of: A user gets a virus on their machine, but it goes unnoticed for a day or two. In that case, a capture would’ve been done overnight that created an image with a virus. In that case, I’d like to grab a capture from a few days prior. Is this possible with certain config settings? I’d be curious to see what the capabilities are for something like this. Storage space isn’t a concern, as our customer already has an entire host dedicated to FOG.