General

• 

  Useful Scripts
  • Tom Elliott  

  7
  6
  Votes
  7
  Posts
  6969
  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  

  111
  0
  Votes
  111
  Posts
  32687
  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
  87977
  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
  3843
  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.
• A

  Sysprep after deploying image
  • alzen  

  4
  0
  Votes
  4
  Posts
  18
  Views

  

  @alzen Well when you run sysprep it kind of resets the computer back to a neutralized condition. You can preset some values using an unattend.xml file you reference when you run sysprep. If you have ever installed windows directly from the dvd drive you know it asks a bunch of question before windows is setup. The unattend.xml file can be used to answer those questions ahead of time so it skips asking the installer the questions. This asking questions bit is part of OOBE (Out Of Box Experience) that is managed by WINdows SETUP. When you run sysprep it cleans out the system of drivers and settings that are important for that specific model of computer and reset its back to a discover new hardware mode. In my case I have 1 golden image for 15 models of hardware. I use a FOG feature to copy the correct drivers over to the target computer during imaging then when winsetup is running it finds the drivers and adds them to the windows configuration. WinSetup will only run when you reset the computer using sysprep.
• J

  Improve documentation
  • Jurgen Goedbloed  

  47
  0
  Votes
  47
  Posts
  198
  Views

  S

  @JJ-Fullmer Looks really great I find. Thanks for picking this up a working on it!
• C

  Doubts About FOG Project Client Windows
  • cstutz  

  10
  0
  Votes
  10
  Posts
  20
  Views

  C

  @george1421 Very Thanks!
• F

  NVMe madness
  • Fog_Newb  

  12
  0
  Votes
  12
  Posts
  59
  Views

  F

  @Sebastian-Roth No worries I didn’t expect the fix to be available when I updated. I was just testing/wondering about .size files and why they were missing and or not being created automatically. I didn’t know they were only created in all disk mode and thought maybe something else was wrong. Thanks for clearing that up.
• K

  capture minimum image?
  deploy image size netboot capture • • kylian  

  15
  0
  Votes
  15
  Posts
  19
  Views

  K

  @george1421 alride thanks for the help. i will get to work then
• 

  Coreboot ?
  • Wayne Workman  

  1
  0
  Votes
  1
  Posts
  10
  Views

  No one has replied

• R

  Create Basic Snapin
  • rodrigonm  

  4
  0
  Votes
  4
  Posts
  15
  Views

  R

  @Tom-Elliott said in Create Basic Snapin: batch script to directly call the npm binary. Right now, the way your batch file is written, it expects the npm to be set in system path. If you know it’s installed in C:\npm\npm.bat I would Thank you @Tom-Elliott and @Sebastian-Roth. It worked as regular user not as administrator. I have used another solution that is psexec that is a tool that runs the script at all the machines.
• F

  host primary disk
  • Fog_Newb  

  3
  0
  Votes
  3
  Posts
  9
  Views

  F

  @george1421 I figured it out. /dev/nvme1n1 I wasn’t sure how Linux named NVMe’s.
• G

  API FOG : How to Apply PxeMenuOptions to Host
  pxe pxe menu api help api • • guyfox  

  5
  0
  Votes
  5
  Posts
  20
  Views

  G

  i think i’ve found the solution . i just made a new ipxemenu entry with my winpe and force via API , the default parameter to 1 to this menu entry i can find in coreobjects pxemenuoptions. i’ll keep you informed
• 

  bad day to update RHEL
  • Wayne Workman  

  1
  0
  Votes
  1
  Posts
  13
  Views

  No one has replied

• N

  Deploy Image Every Boot/Reboot
  • nerdstburns  

  8
  0
  Votes
  8
  Posts
  16
  Views

  S

  @nerdstburns If the host is turned off and wake on LAN (WOL) works in your environment, then it will just be started automatically and do the image deployment. You can have it reboot after the task (default) or let it do a shutdown via adding shutdown=1 as Kernel parameter (general FOG settings or individual host settings). When you use the FOG web UI to schedule a normal deployment task you see the selection: Schedule instant (default selection) Schedule delayed (one shot at a certain time) Schedule cron-style (repeating task as often as you like it to happen, once a day or every other hour or whatever)
• V

  How long should it take to deploy and image on average?
  • vemoya  

  6
  0
  Votes
  6
  Posts
  12
  Views

  

  @vemoya Well 3 GB/s is on the bottom edge of acceptable (in my book). There may be some tuning needed to do in your infrastructure. Its not horrible just a bit slower than expected. Just be aware with 3 ongoing unicast images you will saturate a 1 GbE link (125MB/s or 7.5GB/min theoretical max) This isn’t a fog issue specifically but a limitation of 1GbE ethernet. You can supplement this by adding additional network cards in your FOG server and then creating LAG links between your network switch and the FOG server. Even if you create these LAG links between the FOG server and switch, if your switch to switch links are 1GbE links that will become your next bottleneck. Again this isn’t a FOG issue, but a byproduct of using a FAST imaging solution. Also if you are imaging more than 2 computers at a time, its best to have an SSD or RAID array in your FOG server and not try to serve multiple unicast streams with a single spindle HDD. That single HDD will not be able to feed the data fast enough to the network adapter. You mentioned multicasts. This is a great solution to push out one image to many computers, but it also has its drawbacks. You need to ensure your network is capable of multicast imaging (again not a fog issue). If your target computers are on the same subnet as the FOG server that is the easiest solution. You just need to turn on IGMP Snooping on your network switches and then multicast away. Just remember the slowest computer in your multicast group sets the pace for the group. But if properly setup you can multicast 30 computers in about the time it takes to image 2 computers (serially) using unicast imaging.
• W

  Automatic Provision of Raspberry Pi
  • wuast94  

  4
  0
  Votes
  4
  Posts
  17
  Views

  

  @wuast94 This is what I found when I was researching this issue for another poster in the forum: https://linuxhit.com/raspberry-pi-pxe-boot-netbooting-a-pi-4-without-an-sd-card/ There were a couple of other ones that I found but it appears I didn’t save the links.
• M

  SOLVED Clone Image Without LAN Port
  • mikmatcr  

  7
  0
  Votes
  7
  Posts
  33
  Views

  M

  @george1421 said in Clone Image Without LAN Port: @mikmatcr said in Clone Image Without LAN Port: What I mean is using an image captured with FOG but displaying it with Clonzilla. It’s possible? No capture the image with clonezilla and deploy it. If you don’t have a clonezilla image, deploy with fog and have fog power off the computer after imaging. Then boot from clonezilla usb and capture image. Not clean but without a network port you are a bit stuck. How can I put this answer as a solution and close this thread?
• T

  How much are deploy and capture speeds affect when FOG server is running from a Hyper-V VM?
  • tesparza  

  11
  0
  Votes
  11
  Posts
  26
  Views

  O

  I don’t believe this is a Hyper-V issue. We have Fog running in a Hyper-V Ubuntu VM, with 8 CPU and 16g of ram, with no issues. The storage is backed by a hybrid disk array with 10TB of SSD accessed via ISCSI, and network is provided as 4x 40g links in a LACP bond. Routinely see 13-15g on NVME backed clients, 4-6 on spinners, 3ish on the 5400 rpm spinners.
• D

  Image can only boot through FOG Menu
  • dennis.porter  

  6
  0
  Votes
  6
  Posts
  21
  Views

  S

  @dennis-porter FOG does not capture/deploy UEFI boot entries because almost all UEFI firmware out there is able to boot without explicit creation of boot entries and some firmware even has trouble when FOG would so this. So for now I don’t see why we’d add this to FOG. Though in your case the firmware seems to not be able to find the boot partition and loader and won’t boot from it. In this case you can use Post deploy scripting to add the entry using efibootmgr Linux command included in the FOS inits.