Subcategories

• FOG Problems

  Technical help directly related to FOG.
  8161
  Topics
  79571
  Posts

  M

  @george1421 There are no error messages in the logs, helpful or otherwise.

  I verified permissions on the ipxe directory. They are owned by the fog user, and for good measure I have them group-writable by www-data which is what the web server runs under.

• 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
  7708
  Posts

  L

  The image I created was 20H2 and it works perfectly fine. After I tried to capture an image of 21H1, it captures perfectly fine and deploys to computers perfectly fine, I find that when I run the command cd C:\windows\system32\sysprep and run the command: sysprep /generalize /oobe /shutdown /unattend:C:\windows\system32\sysprep\unattend.xml it runs the portion it is supposed to and the machine shuts down. After deploying this captured image it acts like a new UEFI image and I cannot get this image to work. I believe it is a script that is not quite right, but I am not sure. Any ideas??

• Linux Problems

  Technical help related to a Linux Problem.

  613
  Topics
  5535
  Posts

  D

  @sebastian-roth you have a point there a good way to learn linux

• 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.