Subcategories

• FOG Problems

  Technical help directly related to FOG.
  9.0k
  Topics
  84.4k
  Posts

  N

  No new ? 😞

• Hardware Compatibility

  Problems with specific computer models.
  688
  Topics
  8.2k
  Posts

  W

  @rodluz , Thanks for your help, this solved the problem.

• Windows Problems

  Technical help related to a Windows Problem.
  983
  Topics
  8.1k
  Posts

  J

  I’m having similar issues on a newly created Windows 11 24H2 FOG image. (Please note that the sysprep answer file I created is bypassing the Secure Boot check allowing FOG to pxeboot from the VM for capture). Once I bring the image down on a physical device and try to encrypt the drive I get the identical error shown above. If I go into the BIOS and enable Secure Boot the device begins encrypting automatically after a restart. NOTE: The drive will fully encrypt and the recovery key is populated successfully in Active Directory. I was feeling confident until I restarted again, then got a BSOD (unrecoverable). Windows 10/11 without secure boot enabled at the time of installation/imaging does not like having secure boot suddenly enabled.
  So, if my thinking is correct this has something to do with secure boot, or more precisely the act of bypassing the secure boot check during Windows setup that was done in the sysprep answer file.
  FOG can’t pxe boot on devices with secure boot enabled, but those same machines can’t be encrypted without secure boot and enabling secure boot after imaging only ends in a BSOD (unrecoverable).
  FOG 1.5.10 on Ubuntu 2204

• Linux Problems

  Technical help related to a Linux Problem.

  711
  Topics
  6.2k
  Posts

  G

  @COE Typically if the permissions on the /images directory get messed up you can reinstall FOG and it will fix the permissions.

  If you run the chmod 777 /images that will make the directory world writable but not the existing files / folders under that directory. If you use chmod -R 777 /images it will change everything under that directory to world writable.

  But before you do that, the linux user fogproject should have read write access to /images. The password for that user is found in the hidden file /opt/fog/.fogsettings That is the user account fog uses to move files around while imaging.

• Mac Problems

  Technical help related to a Mac Problem.

  78
  Topics
  935
  Posts

  J

  UPDATE –

  @astrugatch

  I just wanted to follow up on this. I realize this thread is ancient but I feel this is still very much relevant. We ended up going with Mosyle (PAID) for our MAC / Apple MDM. We are unhappy with it. It does not meet either myself or the instructors expectations.

  You are 100% correct, Mosyle does not meet the expectations of a true MDM. It’s clunky and the support is not great. I have not looked at munki yet but am going to pursue that to try and make the most of what we have. I am also looking at another product called FileWave, which is supposed to work very well with pretty much every platform (minus Linux). FileWave is a paid service / subscription.

  Thanks again!

• General Problems

  General Developer questions relating to FOG.
  650
  Topics
  4.9k
  Posts

  D

  @danieln Figured it out. Posting the answer here for posterity. This is the request that worked:

  Request: PUT http://10.15.0.2/fog/host/7700

  JSON body:

  { "snapins": 1 }

  it was "snapins" that I had to pass into the JSON body. I found this by just running a general GET request for snapins GET http://10.15.0.2/fog/snapin (another total guess that ended up being correct) and in the JSON body response it returned "snapins" with an array of objects, so I just passed that into the PUT request body and it worked. The Snapins are literally numbered in the order in which you create them and you can reference them here to assign them.

  Hope this is helpful to any future person who tries to do this! 🙂