Subcategories

• FOG Problems

  Technical help directly related to FOG.
  8162
  Topics
  79622
  Posts

  

  @jyost If it does not work, verify that the build number has changed from your previous picture. The build number in the hex code in the square brackets on the ipxe banner page.

  Also if it doesn’t work, try the snponly.efi boot loader instead of ipxe.efi (fog recommended default).

• Hardware Compatibility

  Problems with specific computer models.
  615
  Topics
  7547
  Posts

  

  @tformentini Yes you are running 4.19.x series. That is a little old and does not have the drivers built in for the latest hardware.

  To update you do this from inside the FOG Web user interface. It is easy. Go to FOG Configuration -> Kernel update. You will see a listing of kernels. Select 5.10.71 for both 64 bit and 32 bit. Once that is done you can verify by running the same command line command as you did before. It should confirm as 5.10.71

• Windows Problems

  Technical help related to a Windows Problem.
  889
  Topics
  7711
  Posts

  

  @littleman1234 said in 20H2 Image Worked, but Tried Building a 21H1 Image and Now Image Does not Work:

  So after I deploy the presysprep image, it works fine, it is only after I run sysprep /generalize /oobe /shutdown /unattend:C:\windows\system32\sysprep\unattend.xml this is when I have trouble

  I think I see a strange workflow that I don’t under stand.

  So let me see if I use my words to explain what I’m seeing.
  I can create a golden image on a physical machine. I can sysprep the image which also powers off the computer using this command sysprep /generalize /oobe /shutdown /unattend:C:\windows\system32\sysprep\unattend.xml. At this point I capture the image with FOG. I can deploy this captured image with FOG to a second computer and it boots fine. But the problem comes when I try to resysprep this image using the command sysprep /generalize /oobe /shutdown /unattend:C:\windows\system32\sysprep\unattend.xml that is where it fails. I don’t try to recapture it with FOG.

  Do I understand where its failing?

  Are you a MSP or system rebuilder? (not judging just trying to understand the context).

  I have a few ideas, I just want to make sure I’m on the right track.

• Linux Problems

  Technical help related to a Linux Problem.

  614
  Topics
  5543
  Posts

  

  @alireza2n May I include your configuration in this tutorial? https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

• Mac Problems

  Technical help related to a Mac Problem.

  66
  Topics
  839
  Posts

  S

  @Matthew-Wyneken I have never tried the fog-client on Mac OS X myself I have to say. It’s been other developers working on this part. Though I am wondering if the instructions given in the wiki are not up to date anymore and if we should update documentation?

  Would you be so kind and let us know what steps you took and what is missing in the documentation?

• General Problems

  General Developer questions relating to FOG.
  527
  Topics
  4278
  Posts

  S

  @Bristow-0 Capturing and deploying a single partition is easy. I suggest you create new image definition, make sure you set the option Partition to “Partition 5 only”! As Image Type use Single Disk - resizable or non-resizable should both work (this plays much more a role when Partition is set to “Everything” which you don’t want in this case!).

  Now go to the command line of your FOG server, manually create the new image directory as /images/newimagename (or whatever it was named) and copy the partition image file you want to use over: cp /images/existingimagewithlinuxpartition/d1p5.img /images/newimagename.

  With that in place you should be able to deploy to your machines.

  BUT there is something I am concerned with and that’s the question of what boot loader do you use and which partition was it installed into??? I can imagine you can’t boot the Linux OS after deploying it the way I described but I am pretty sure this can be fixed using postinstall script magic. So you need to figure out which bootloader is used and where it was installed.