You really didn’t supply enough information but looking at the error I can give you a direction to look in. The error is http://192.168.2.10/bootimgs/18.04/casper/vmlinz… does not exist. So that means you are using the http protocol which has a base directory of /var/www/html/fog from that directory bootimgs/18.04/casper/vmlinz needs to exist. Just looking at the directory you provided there is no base references but I see Ubuntu directory of 18.04_64 which if you translate that to the file not found path 18.04_64 != 18.04 assuming the base path was /var/www/html/fog/bootimgs

To clarify, all I’m doing is modifying the MAC address on a host in FOG and clicking the update button. After that, when refreshing the page, I noticed it added the old address as an additional MAC. You might not see it until you refresh. I’m not clicking any other buttons related to adding an additional MAC. FOG just adds one itself.

you da man!

Some options. 1º Use a snapin pack including the executable. 2º Put it in a ftp server and use a cmd ftp client to download it. (You can use the fog server/node as ftp and the built-in ftp client) This two solutions works!!!

Hi @Junkhacker It’s an raid array of 6x900gb 15k SAS drives connected to an HP P408i-a SR Gen10 Controller. All of it combined to a single D: drive in Windows.

Hi all, i have secureboot working with ipxe (FOG) using a self-signed certificate and you do however need to enroll the keys but i have added an .efi program that you can run to automate all this from the pxe boot menu to ease this process. i’ve been testing it for the last 12 months or so to see if there is any gotchas but none yet and over 80% of our estate have secureboot with ipxe working (7K devices) - only lenovo x1 carbons have been problematic but this appears to be due to poor bios and/or secureboot implementation. this does mean you have to manage the certificates yourself going forward too as you are essentially taking ownership and provisioning the devices and applying your own PK which means you have to trust 3rd party CAs however the plus side there is no cost involved. i also don’t have assurances how to remotely distribute a renewed certificate when it expires but expiration is 10 years and there is going to be some work needed when microsoft CA expires in 2026. on first attempt, i hadn’t included microsoft CA so windows os failed to load with untrusted error from secureboot… i loved the irony… i dont trust microsoft either :-) if anyone is interested i can write up instructions however you have to remember technically this is outside of FOG remit, so support on FOG forums will be extremely limited and unfortunately with 2 jobs i have very little time to spare either.

@Brad-Schumann said in Blank Screen with Blinking cursor in top left corner: Would a Windows, bios or driver update have this affect The short answer is no. Older firmware on the target system might. So just for additional clarity the 5570 is in uefi mode? If so then we have an issue with rEFInd executable not finding the disk controller. When the FOG iPXE menu exists it calls refind to locate the hard drive boot device to boot the target computer.

@Sebastian-Roth Sorry about that. I was just showing an example of what modifiers I used. (-S, -y, -K, -C) And the combinations I tried with them. I do install fog as a root user, but I have a habit of using sudo anyway.

@Lee-Rowlett Thanks!

i restored the background file, clicked “Update” on the menu settings page of the WebUI and all is fine now. Weird. One question though, from the main FOG ipxe menu, when i hit Deploy Image, and get the prompt to authenticate with fog/pass, that text is blue, i want it to be white. Where can i change that setting?

I will definitely look into this issue when I get back.

@darkxeno In the dell firmware switch the disk controller from Raid-on to AHCI mode. Unless you have more than one disk connected in a raid configuration raid-on mode doesn’t help you. There is a document issues between linux and intel controllers in raid-on mode. Once you have imaged with fog you can switch back to raid-on mode or leave it in ahci mode. It doesn’t matter to windows.

What device is your dhcp server. I’m going to guess it is a soho (home) router? The reason I think this is your gateway is 192.168.0.1 and your next server (from the picture) is also 192.168.0.1. Home (soho) routers will often say they are the pxe boot server and not the fog server.

@Sebastian-Roth if I had to guess it’s lvm setup.

@george1421 said in Capture problem: I have noticed an uptick in people reporting this invalid storage group. Aß mentioned in my last post it’s not the same error message everytime. A couple of times we hat the “Invalid Storage Node” but this one is not.

George, I have another question, this time about sysprep. Why do we need to go through OOBE for an installation that is all in the same locale? Wouldn’t it be easier to just generalize and be done? And if doing that, do I still need to disable the Fog Client Service before doing it? Thank you, Dave

@andrewhancock91 I am on the road right now und will be for the next two weeks. Not easy to give you all the details not having my laptop with me. First you should start by searching the forums for “https fog-client” and see if you can find my older posts about why this part is tricky. It’s not a no-go but it will need good planing and manual adjustment - could even compile your own custom fog-client package… For switching back to HTTP for now you’d edit /opt/fog/.fogsettings file, find the line httpproto=https and remove the “s” at the end of “https”. Save and re-run the installer. That should be it. Make you read all you can find on this topic before diving into this again. If you have many hosts with fog-client installed and communicating to your current FOG server already you break this switching your apache config to a different certificate! Feel free to ask here if you can’t find those forum topics.

ill take a look next time i capture. i make sure the actual image size is the compressed, used data from the drives i capture, in the terminal using dh -u. we use a custom sccm image that is based on the stock windows install, which has bitlocker disabled.

@dario-vettore Try testing aß suggested in the wiki: https://wiki.fogproject.org/wiki/index.php?title=Troubleshooting_a_multicast Are you sure there is no firewall between FOG server and the clients??