General

• 

  Useful Scripts
  • Tom Elliott

  8
  6
  Votes
  8
  Posts
  7164
  Views

  

  That’s really cool.

• 

  Organizations Using FOG
  • Tom Elliott

  111
  0
  Votes
  111
  Posts
  33162
  Views

  R

  Organization Name: SVOBE Schools

  Location (Optional) St. Maarten, Dutch Caribbean

  Approximate Number of systems: 500

  How long: 8 Years.

  We have been using fog to re-image all our school labs every summer.

  Wiki entry:

• N

  Requests for Wiki Access <--- ASK HERE
  • noktis

  145
  0
  Votes
  145
  Posts
  89085
  Views

  S

  @lps-rocks Thanks for getting in touch! Sounds great. You are more than welcome to update the wiki and help with iPXE stuff here too. See the chat bubble in the top right corner for more information.

• C

  Please do not cross post on multiple forums with the same question
  • chad-bisd

  2
  1
  Votes
  2
  Posts
  3867
  Views

  T

  This seems to [url=https://www.gclubtg.com/]gclub[/url] be happening more often lately [url=https://www.sbobet168.com/]sbobet[/url] than in the past.

• B

  Use HTTP instead of TFTP for fetching WIM files
  • brakcounty

  7
  0
  Votes
  7
  Posts
  51
  Views

  B

  Success! Dropped the files into /var/www and used set web-path to ${fog-ip}. In case anyone else has this issue this is my iPXE menu item parameters:
  set tftp-path tftp://${fog-ip}/os
  set web-path http://${fog-ip}
  set pe-path ${web-path}/pm11_winpe
  kernel ${tftp-path}/wimboot gui
  imgfetch --name BCD ${pe-path}/BCD BCD
  imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi
  imgfetch --name bootmgr ${pe-path}/bootmgr bootmgr
  imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim
  boot || goto MENU

• D

  FOG on Raspberry Pi
  • David Mack

  16
  0
  Votes
  16
  Posts
  15926
  Views

  

  @develroo I’ve had the FOG server running on raspberry pi 2 for quite a while. That is the 1.4.x series. For fog 1.5.x you should run that on a Pi3 or Pi4. The matter of fact, for fog imaging a Pi is more than enough for hosting the fog server. Now realize that the scope of service is for imaging a small number of system and no computers running the FOG client. The Pi4 is a bit more capable with 1GbE networking and USB3 for externally attached sata drives. The Pi 2 suffers with 100Mbs networking and USB2. The Pi3 has 1GbE networking and USB2.

  For FOG imaging all the Pi needs to do is monitor the imaging process and move the image from local storage to the network adapter. The target computer does all of the heavy lifting. So the Pi3-4 is more than enough for acting as a limited or mobile FOG server.

• R

  This topic is deleted!
  • rodgeremorgan

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• R

  This topic is deleted!
  • rodgeremorgan

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• S

  Move partitions on GPT layouts - need people to test
  • Sebastian Roth

  25
  1
  Votes
  25
  Posts
  292
  Views

  S

  I think we are getting closer to finishing this new feature. I looked through the code changes again and finally found some time to do more testing on this. Simple Debian UEFI install with sda1=/boot, sda2=/ and sda3=swap.

  Initial install on a 64 GB (virtual) disk - d1.partitions:

  label: gpt label-id: B1330462-6EE4-45E4-87F8-213A452A66A2 device: /dev/sda unit: sectors first-lba: 34 last-lba: 134217694 sector-size: 512 /dev/sda1 : start= 2048, size= 1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=47839DDA-7009-4F7B-98D9-B4B2D4C44956 /dev/sda2 : start= 1050624, size= 131096576, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=D6E07619-9532-47FD-A8C6-B0FA635CFE25 /dev/sda3 : start= 132147200, size= 2068480, type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, uuid=96D50996-9760-4C22-A14F-1EDA45509C00

  Deployed it to 32 GB disk and 256 GB disk and both worked fine. System booted and sda2 was expanded to whatever the disk size was (minus /boot and swap) and moved sda3=swap all the way to the end. With that d1.minimum.partitions I could deploy this to a disk as small as roughly 4,2 GB:

  label: gpt label-id: B1330462-6EE4-45E4-87F8-213A452A66A2 device: /dev/sda unit: sectors first-lba: 34 last-lba: 134217694 sector-size: 512 /dev/sda1 : start= 2048, size= 1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=47839DDA-7009-4F7B-98D9-B4B2D4C44956 /dev/sda2 : start= 1050624, size= 5683045, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=D6E07619-9532-47FD-A8C6-B0FA635CFE25 /dev/sda3 : start= 6733824, size= 2068480, type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, uuid=96D50996-9760-4C22-A14F-1EDA45509C00
• A

  Capturing an image from Vendor X laptop and deploying to Vendor Y laptop?
  • alexnoel2

  9
  0
  Votes
  9
  Posts
  35
  Views

  A

  @george1421

  Good to know. I’ve been rolling with the same script since Win7 and likely would not have looked at another way to do it short of it failing to run on a new version.

• D

  Automate Snapins to run after deployment?
  • danieln

  4
  0
  Votes
  4
  Posts
  53
  Views

  

  @danieln I just realized that the persistent group plugin is not very well documented. It is covered a bit here: https://forums.fogproject.org/topic/8836/basic-persistent-groups-and-1-3-0rc16

  The executive summary is

  Add the Persistent group plugin Manually create a new host with a unique name that signifies it is a template host. Associate all of the snapins and what not that you want consistent for every host added to the group. Create a new Group that is exactly the same name as the template host. Now add hosts to this group (you can do this when you are registering the new computer with FOG too).

  The settings will be copied over from the template host to the new host.

  The workaround is just a patch file that needs to be replace on the FOG server. Replace this file BEFORE you install the plugin. If the plugin is installed before you add the patch file, uninstall the plugin then add it back.

  We are discussing the discovered bug here: https://forums.fogproject.org/topic/15084/persistent-groups-snapins-added-to-host-but-not-deployed

  The thread also has the temporary patch file link.

• 

  Change default answer of the "Perform Full Host Registration and Inventory"
  • davido38

  6
  0
  Votes
  6
  Posts
  19
  Views

  

  It works great !

  Thanks a lot !

• D

  Backup program
  • d3fuentes

  6
  0
  Votes
  6
  Posts
  41
  Views

  

  With apologies for the necropost, I’m looking at exactly this question at the moment. My thinking is you could possibly pair FOG with Relax-and-Recover or SystemImager for a complete backup/image/bare metal restore solution.

  Looks like you would be able to add a Relax-and-Recover (ReaR) menu item to FOG’s menu for a full network-based restore, in the event of disaster. Since FOG can be used as a scheduler and general-purpose task executer, it is entirely possible to run one of these open source “live backup” solutions alongside FOG - i.e. on the same server.

  I also note that ReaR can deal with UEFI/MD RAID situations, which seems to be a rare gift.

• 

  Fully automated UEFI-based O/S installation (Debian 10)
  • RobPomeroy

  22
  0
  Votes
  22
  Posts
  501
  Views

  

  @george1421 Done.

• B

  Headquarters Address for FOG?
  • boriquaboy115

  2
  0
  Votes
  2
  Posts
  51
  Views

  

  @boriquaboy115 FOG is an opensource project. AFAIK there is no physical location where The FOG Project exists. One of the developers might know for tax reasons if there is a specific mailing address.

  As I said, The FOG Project is an opensource project with developers around the world. The senior developer that approves releases is based in the USA.

  If you need this information for federal regulatory submission reasons, you may have a hard time getting opensource software approved for use.

• K

  capture a image over the fog boot menu
  • ktif14

  2
  0
  Votes
  2
  Posts
  39
  Views

  S

  @ktif14 Sorry for the late reply. No, it’s not as easy as creating a new iPXE menu entry because a task needs to be created in the database. This can be done either by using the FOG web UI or the FOG API but not through the iPXE menu.

• N

  Local deploy Image
  • noithatgooccho

  2
  0
  Votes
  2
  Posts
  24
  Views

  S

  @noithatgooccho There are different ways of getting what you are calling a “local cache”. Though the solutions have different restrictions or requirements.

  Install a normal FOG master node in that location (no connection to the other server), register all your local hosts in that new server (it’s own database), create image definitions and manually copy the image files over to that server. Every time the image on the pre-existing FOG server is changed you need to manually copy the image over again. But local hosts can also capture an image to that new FOG server in that location.

  Install a FOG storage node in that location - which needs to be able to constantly contact your pre-existing FOG master node to query information from the central database. The image files will be replicated from the pre-existing master node to the new storage node once (every time the image changes) - no manual copying needed. The hosts in that location can pull (deploy) an image from that new storage node (local cache) in unicast mode. But be aware that hosts in that location can only upload/capture an image to the pre-existing master node, not to the local storage node.

  So it depends on what you want to achieve.

• S

  Ubuntu 20.04 Desktop live
  • seppim

  2
  0
  Votes
  2
  Posts
  31
  Views

  

  @seppim said in Ubuntu 20.04 Desktop live:

  http://archive.ubuntu.com/ubuntu/dists/eoan/main/installer-amd64/current/images/netboot/netboot.tar.gz

  Thank you Ubuntu… Try this link: http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/netboot/

  Ubuntu 19.10 has been removed from existence so the previous links are now broken.

• S

  Capture Ubuntu 20.04 just free diskspace
  • seppim

  8
  0
  Votes
  8
  Posts
  43
  Views

  S

  @sebastian-roth Hi Sebastian,

  thank you!

  Well, the 3 partitions are because of the Ubuntu software Raid.

  I need the Raid to prevent system halt, because the server is not local monitoring. so no one will check if the HDD goes failed.

  I finish my setup and try to capture … as long he copy 1:1 the HDD for the backup its fine

• 

  create/capture new image over the fog boot menu
  • EnricoK.

  9
  0
  Votes
  9
  Posts
  63
  Views

  

  @sebastian-roth

  I wish you and your familie a happy and healthy new year.

  I wanted to say thank you for your time.

  best regards

  Enrico