@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.
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.
@george1421 When I renamed refind.efi to refind_x64.efi, it worked as intended. Thank you for your help, I really appreciate it.
@george1421 Hi, I’m attempting this fix right now and I’m running into an issue. I downloaded the latest version of the zip, and I only see refind_aa64.efi, refind_ia32.efi, and refind_x64.efi. I do not see the refind.efi file in the latest version, or 1 version behind that. Should I just replace the 3 files I listed? or will that cause issues.
I haven’t seen anything regarding this, so I figured I’d ask. Will FOG ever work with Secure Boot on? I’ve been reading that Windows 11 will require secure boot, and that causes some issues. If FOG won’t support Secure Boot enabled, I may have to look at a different deployment solution. I would love to stay with FOG as it works for what I need.
If there is a way to make it work with secure boot enabled that I’m not aware of, please feel free to share what I need to do.
@brakcounty Since I’ve posted this I’ve discovered the cronjob option. I guess I’m just confused how this will work in the future with Secure Boot. If I have a scheduled task, I’d need secure boot off so it can PXE boot. Unless there’s an option to boot into fog with secure boot enabled, but I haven’t found anything
I’ve been managing a FOG server for about 9 months now, and today I was requested to find a way to schedule either weekly or nightly captures of devices to function as a backup. They had spoken with someone that does this on a FOG server currently, but I wasn’t given their contact info so I’m not sure how it works.
How would I achieve this? I’m not sure exactly what scheduling capabilities FOG has, so I figured I’d ask here.
Any help is appreciated, I need to make this work.
@maximeguidez I ran into this issue in the past, and if I remember right switching the bootfile to snp.efi was what fixed the issue. I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.
If that doesn’t work, I’d recommend updating the kernel version.
@george1421 I had already used that article you linked to set up DHCP for UEFI and BIOS coexistence, but it only has information for 5 of the architectures (00002, 00006, 00007, 00008, 00009). I need to know what to point the remaining 4 types to, because there’s 4 remaining that don’t have any association.
That’s why I was wondering if there’s any simple way to view the boot architecture on any specific PC, so I could go PC by PC and set up the policies that way
I’m looking into setting up FOG servers for multiple of our customers for simple workstation captures, and I’m worried about the pxe boot process with such a wide variety of PCs.
I currently have Windows DHCP set to look at the architecture type, then pick a bootfile based on that.
Is there a way to view what pre-boot architecture type a PC has? If I could do that, it would make my life much easier. Then I would be able to make the correct DHCP policies for each architecture, so I can avoid PXE boot related issues.
I’d be willing to share the DHCP policies to help others, I just need to figure this out first so I can get them configured correctly.
I’d like to remove a few of the questions when performing a Full Host Registration & Inventory. Is there any simple way to do this? I just want it to ask for the name, image ID, and whether or not it wants to image the PC or not.
Any help is appreciated, even if it’s just a suggestion.
To start, I’m following the following link to setup UEFI and BIOS to PXE boot correctly:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
I have the vendor classes setup, but I’m not sure what architectures to assign to bootfiles. For example, I’ve had ipxe.efi work 99% of the time, but there’s some models that only snp.efi and snponly.efi work on. As a result of this, I’m skeptical what bootfile I’m supposed to use for each architecture.
Just looking for guidance to see what has worked for others, because the tutorial I sent a link for only includes instructions for PXE client architecture 00007. Any help/ suggestions are appreciated. I want to make sure I have everything setup correctly before I put this in a live environment