General

• 

  Useful Scripts
  • Tom Elliott  

  7
  6
  Votes
  7
  Posts
  6931
  Views

  J

  We have created a dedicated repository for community scripts: https://github.com/FOGProject/fog-community-scripts. All scripts in this repository are under the MIT license, and contain a brief README describing basic usage.
• 

  Organizations Using FOG
  • Tom Elliott  

  110
  0
  Votes
  110
  Posts
  32647
  Views

  I

  @Tom-Elliott Organization Name: High Point University Location (Optional) High Point, NC Approximate Number of systems: 50 How long: 1 month Wiki entry: I am able to properly capture and deploy images to Mac OSX Mojave and on Ubuntu Linux 18.04 LTS both using nvme drives, and supported with hostname changing via the Fog-Client. I migrated us to FOG, suggested by a faculty member, after realizing manually doing this with CloneZilla was not ideal. We at High Point University in North Carolina have migrated from CloneZilla to this open-source software and image management. You have saved us a lot of future time by creating this software. From the Webb School of Engineer, as the solo systems admin here, thank you.
• N

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

  143
  0
  Votes
  143
  Posts
  87961
  Views

  S

  Added fry_p.
• C

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

  2
  1
  Votes
  2
  Posts
  3841
  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.
• 3

  Wiki errors - "Troubleshooting a multicast"
  • 3mu  

  9
  0
  Votes
  9
  Posts
  14
  Views

  3

  @george1421 - I can’t remember if it picked up the correct interface on install or if I changed it later when preparing to try multicasting, but it has been set to ens3 for at least a few weeks. ps only gives: [username] 18913 0.0 0.0 13136 1092 pts/0 S+ 01:39 0:00 grep --color=auto udp-send The multicast task appears as “queued” for each host in the Active Tasks pane, and the multicast log continues as if all is well: [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 image file found, file: /images/T500Linux19-10desktopclean [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 2 clients found [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 sending on base port 61792 [04-07-20 11:59:25 am] | Command: /usr/local/sbin/udp-sender --interface dev --min-receivers 2 --max-wait 600 --portbase 61792 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/T500Linux19-10desktopclean/d1p1.img; [04-07-20 11:59:25 am] | Task ID: 10 Name: Multi-Cast Task - Multicast t500 has started If I start a multicast from the command line with sudo udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint I get root 20233 0.0 0.1 66696 4268 pts/1 S+ 01:48 0:00 sudo udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint root 20234 0.0 0.0 8884 896 pts/1 S+ 01:48 0:00 udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint [username] 20351 0.0 0.0 13136 1000 pts/0 S+ 01:49 0:00 grep --color=auto udp-send
• K

  Fog is awesome!!!
  • kyokushin  

  1
  3
  Votes
  1
  Posts
  11
  Views

  No one has replied

• R

  Adding HP SPP iso to fog
  • rockinhc  

  8
  0
  Votes
  8
  Posts
  31
  Views

  

  Just to round out this thread, this is the final configuration steps to get this service pack up and running. In the end I did need the iso image to try to reverse engineer what it was trying to do. If you want to test this configuration on a VM make sure you use the E1000 type nic or the booting kernel may not see the network adapter. HPE SPP2019120 1.First we’ll create the required directories: mkdir -p /images/os/spp mkdir -p /tftpboot/os/spp 2.Now we’ll mount the SPP2019120 installer over the loop directory. mount -o loop -t iso9660 /{full path where you have the iso stored}/SPP2019120.2019_1219.1.iso /mnt/loop 3.Finally we’ll copy the pxe boot kernel and intfs to the tftpboot directory. Then unmount the iso image and move the iso image into place. cp /mnt/loop/pxe/spp2019120/vmlinuz /tftpboot/os/spp cp /mnt/loop/pxe/spp2019120/initrd.img /tftpboot/os/spp umount /mnt/loop mv /{full path where you have the iso stored}/SPP2019120.2019_1219.1.iso /images/os/spp/SPP2019120.iso 4.The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS. 5.In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry Set the following fields Menu Item: os.HPE.SPP2019120 Description: HPE 2019120 Parameters: kernel tftp://${fog-ip}/os/spp/vmlinuz initrd tftp://${fog-ip}/os/spp/initrd.img imgargs vmlinuz initrd=initrd.img media=net root=/dev/ram0 splash quiet hp_fibre showopts TYPE=MANUAL AUTOPOWEROFFONSUCCESS=no iso1=nfs://${fog-ip}/images/os/spp/SPP2019120.iso iso1mnt=/mnt/bootdevice iso1opts=nolock,ro boot || goto MENU Menu Show with: All Hosts 6.That’s it, just pxe boot your target system and pick HPE 2019120 from the FOG iPXE boot menu. In the syslinux kernel parameters for this iso image there was to groups of kernel parameters. In the syslinux menu there was a manual method and an automatic method. During the development of this process we only tested the manual method. The manual method uses these kernel parameters as show above. TYPE=MANUAL AUTOPOWEROFFONSUCCESS=no The automatic method uses these kernel parameters. TYPE=AUTOMATIC AUTOPOWEROFFONSUCCESS=no AUTOREBOOTONSUCCESS=yes If you want to use the automatic method (I have no clue what that means) replace the manual kernel parameters in the iPXE menu with the automatic parameters. Be careful to not replace too many bits because the HPE SPP seems to be a bit fussy with what it expects in the linux kernel parameters. With this setup in place you can use the same tftp boot infrastructure to boot into any of the HPE SPP iso, now by just adding the iso image to the directory and copying the iPXE menu configuration to a new entry while updating the iso name in the iPXE menu.
• D

  Why does FOG need a DNS server?
  • danieln  

  6
  0
  Votes
  6
  Posts
  24
  Views

  S

  @danieln The DNS IP the FOG installer asks about is only ever used when you let FOG setup the DHCP stuff for you. It is used to hand the DNS server IP to all the clients when booting. It’s just what pretty much any DHCP server does, tell clients where the default gateway and DNS server is.
• N

  FOG server hardware workload
  • nockdown  

  11
  0
  Votes
  11
  Posts
  42
  Views

  

  @nockdown snapins are programs (think ms office) that you will install post imaging. By putting those on a different partition than the root, you reduce the risk of filling up the root file system and bringing down the fog server.
• 

  FOG reapply Windows Setup
  • FuriousGamer065  

  8
  0
  Votes
  8
  Posts
  15
  Views

  

  @FuriousGamer065 Now if you were going to do 50 or more per year I would recommend a bit different approach in that you will create a fat image and include all of the applications you need right in the golden image. You would only install applications post imaging that require a system unique ID like enterprise virus protection. You would also use the unattend.xml file to answer all of the preinstall OOBE questions so the deployment is completely lite touch. https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem?_=1584219461172 You would also create a post install script to install the system specific drivers etc.
• N

  Mounting option for /images
  • nockdown  

  2
  0
  Votes
  2
  Posts
  6
  Views

  S

  @nockdown Haven’t tried it myself but I would think yes, shouldn’t cause an issue. Give it a try and let us know.
• K

  Best hardware for Fog server
  • kyokushin  

  3
  0
  Votes
  3
  Posts
  18
  Views

  

  So the answer depends. How many end user computers will have the fog client installed on? How big (computer wise) is your campus? For a small site FOG will run on a Raspberry Pi3, but that doesn’t scale well. Most systems we would start out with 2 vCPU and 4GB of RAM. For the host OS disk 50GB and then I would recommend creating a second disk just for the images and a 3rd if you plan on having a lot of applications deployed by the fog server. The reason for independent disks for images and snapins is that you can expand a dedicated disk easier than the disk your root filesystem is on that is used by your linux OS. That is a bit deeper of a subject than what does fog run on.
• C

  New NIC solely for MGMT
  • clarkjohnken  

  2
  0
  Votes
  2
  Posts
  8
  Views

  S

  @clarkjohnken The FOG web UI should not be pinned to a specific interface or IP (unless you have HTTPS enabled). So you should be able to configure an IP to eth1 and simply open the web UI with that new IP. Though this is just from the top of my head. I have not tested this myself yet.
• R

  configuring net0 DHCP failed
  • robertkwild  

  2
  0
  Votes
  2
  Posts
  9
  Views

  R

  sorted it out, i had to enable port fast on the cisco switch for the port(s) the reason it took ages to get a dhcp address is because when port fast is disbaled it takes 30 seconds for it to give it a lease address
• G

  Distributed computing
  • Gabor  

  4
  0
  Votes
  4
  Posts
  24
  Views

  

  @Gabor said in Distributed computing: just installed FOG for imaging computers Ok I was under the impression that you installed FOG for netbooting. So then if you have FOG installed for imaging then you can continue to use it for both imaging and netbooting since everything you need is included with FOG for imaging as well as netbooting. If you want to run off the shelf OS by netbooting I have a tutorial on that and how to integrate with FOG here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images The buildroot approach is a bit more complicated but you an end up with a really fast and tight system. To build a custom linux OS using buildroot you will need to use a linux computer and to download the buildroot dev environment from here: https://buildroot.org/ I suggest that you watch a few youtube videos on buildroot to see if its right for you. If you want to start by building FOS Linux init.xz image you can start with the data on the github site: https://github.com/FOGProject/fos/tree/master/Buildroot The github repo won’t mean anything to you unless you understand a little bit about buildroot. But with the board/FOG/FOS file path, those files will be copied to the target disk image without changes. The files in that path are placed in the init.xz initfs. Really the files in this path make the image FOS. The packages directory is for custom applications you want complied and installed in the target init.xz file. Again watch a few youtube videos to understand what buildroot is and what it does to decide if you want to go down this path.
• I

  Error when trying to deploy images
  • ItsMeFIZ  

  9
  0
  Votes
  9
  Posts
  30
  Views

  I

  @Sebastian-Roth Here’s the output…I will try re-imaging with non-resizable
• I

  upgrade from 1.5.7 to 1.5.8 fail at password
  • ItsMeFIZ  

  6
  0
  Votes
  6
  Posts
  22
  Views

  I

  @Sebastian-Roth this is my lab. I have this server as a Samba DC as well
• B

  Documentation Snapin Return Codes
  • BSZAdmin  

  2
  0
  Votes
  2
  Posts
  15
  Views

  Q

  I think they just return the exitcode of whatever it is you’re trying to snapin.
• R

  deploying image from xen windows 10 - blue screen
  • robertkwild  

  3
  0
  Votes
  3
  Posts
  22
  Views

  A

  Xen defaults to BIOS though in 8+ you can switch to EFI and I’m pretty sure new versions of ESXi default to EFI. Can you confirm which you have on each?
• R

  creating an image container for windows server 2012 r2
  • robertkwild  

  5
  0
  Votes
  5
  Posts
  13
  Views

  S

  @robertkwild said in creating an image container for windows server 2012 r2: so for normal cloning i can use “single disk resizable”? Please read this: https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images If you don’t need to deploy to a smaller size disk you might consider using this image type as it’s less likely to cause an issue and image size on the server is still as small as with resizable image type.