Categories

• Announcements

  Get the latest news on what's happening.
  178
  Topics
  766
  Posts

  

  I know I’ve been out of this for a little bit. I check in here or there, but just been extremely busy.

  I don’t want to stop contributing, I just am taking time for myself after my workly duties.

  I have to give a big gratitude and thanks for everyone here trying to help out whether by code, by helping the rest of the community, or documentation.

  @Sebastian-Roth I know you’re busy but you’ve kept the project rolling even with the minimal availability you have. Thank you.
  @george1421 I’m sure you’re busy, but I still see you posting and helping where possible and amenible. Thank you.
  @Wayne-Workman I know you’re helping where you can as well. (Of course I can’t exactly post everybody because I’ve been busy and honestly not keeping up with the forums as much as I probably should.)

  @everyone Thank you. Thank you for still believing in this project. We’re doing the best with what we have. Please understand in we’re lacking, it’s most likely unintentional. I know I’m just busy.

• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  2223
  Topics
  17576
  Posts

  

  @smccloud WDS and FOG use the same base technology for PXE booting. So your quest is challenging but not impossible.

  WDS uses a booting function called ProxyDHCP. This process supplies a dynamic boot file depending on the target computer’s type (bios or uefi). This ProxyDHCP overrides anything you might set in dhcp options 66 and 67. So this will be a problem if your WDS server, and FOG server are in the same broadcast domain.

  Depending on your network configuration and needs, the simplest method would be to put the windows and linux computers on different subnets. The second option would be to stop the ProxyDHCP service (called something else in WDS, but boot is in the name) and then PXE boot into the FOG iPXE menu, where from there you can chain into WDS booting. This would be a menu selection in the FOG iPXE menu.

  Tell me a bit more about your network infrastructure so we can think about the next steps.

  Also what is your mix of windows to linux deployments?

• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  10945
  Topics
  106141
  Posts

  

  @robertkwild Since you didn’t reference a step I can only guess at the answer.

  But the dbx.esl is created on this post Preparing the FOG server with the prerequisites

  More specifically is a copy of the dbx file you exported out of hardware in this section

  sudo efi-readvar -v dbx -o /opt/fog/secureboot/hwkeys/hw_dbx.esl

  dbx.esl is also created when you run these commands

  cd /opt/fog/secureboot/efitools make

  This is when you first compile the efitools programs
  Then we rename the first compiled version with this command because we don’t need it in the finished product. We’ll use the hw one that was downloaded from the firmware.

  mv dbx.esl dbx-fog.esl

  And then finally we take the firmware hw_dbx.esl file and copy it over to the dbx.esl file name.

  cat hw_dbx.esl > dbx.esl

  Depending on where you are getting the error I think you missed a step. The dbx.esl file contains any certificates that have been revoked. When you compile the file signing keys the default microsoft dbx.esl file is good enough.

• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2199
  Topics
  20479
  Posts

  

  Another thing I just now thought of - versioning the partition file we keep with the images. We can start out with v1.0.0. And if we change how we store that file, we simply increment the version. This would give us some more flexibility in regard to changes.

  Thinking further, the scripts that collect the physical partitions are fine, we can just add JSON output for those.

  And really, the LVM describing tools are what needs JSON output, so the effort there is targeted to just those.

  I think I’m going to take a swing at adding JSON to an LVM describing tool (there are several).