General

• 

  Useful Scripts
  • Tom Elliott  

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

  107
  0
  Votes
  107
  Posts
  32079
  Views

  S

  @Tom-Elliott said in Organizations Using FOG: Organization Name: Davidson County Sheriff’s Office Location: Nashville, TN Approximate Number of systems: 750 How long: since 2012
• N

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

  135
  0
  Votes
  135
  Posts
  87475
  Views

  H

  @iyoung good
• C

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

  2
  1
  Votes
  2
  Posts
  3804
  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.
• Z

  How to PXE boot to a Windows PE ISO
  • zaboxmaster  

  7
  0
  Votes
  7
  Posts
  106
  Views

  A

  Windows 10’s ability to read the product key from the BIOS has nothing to do with MBR or GPT deployments, but how the Windows image was created.
• J

  Mounting and booting an NFS provided Linux root
  • johnny_verdane  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  Well this is a pretty complex subject. I see you have the system booting via FOG iPXE. In a way you do want the live boot running, but in your case you want to create a custom environment. The vmlinuz and initrd files are the base/core OS. (note this part I’m guessing) the core OS has just enough stuff in it to get the system up on the network and to attach to the NFS share. At this point it probably transfers the complete OS to the target computer. That OS is typically contained in a squash fs file. IMO you need to target that squash fs file to add in your custom applications. (I don’t know how, only giving you a direction to look in). You can pass boot time stuff to the target computer through kernel parameters. In your example you could add a kernel parameter mac=${net0/mac} This is using an iPXE variable to set the kernel parameter. It may be just as easy to pick up some boot time information via bash in a rc.local script within your environment. Since you are in the iPXE menu construct you can not use any of the FOG run time variables like ${hostname}, because that environment is not running at this time. A totally different approach you might want to look into here is using buildroot to build your own custom OS (akin to what FOG calls FOS Linux). This would then create a bootable bzImage (vmlinuz) and initrd specifically for your workload. Once you are done you would just boot bzImage and initrd directly from FOG and not need any network shares because everything would be contained within initrd. The system would boot very fast since only the required bits would be in the OS. If your workload didn’t need XWindows then don’t include that in your buildroot OS. I can tell you when you first start out using buildroot is VERY intimidating. But you can really do some cool things with it once you understand the process. If you look at the FOG Project’s FOS files on github, you can reverse engineer how the FOG developers created FOS Linux and then incorporate your workload into that framework.
• J

  Client does not stop at FOG menu
  • jrprajapati  

  3
  0
  Votes
  3
  Posts
  21
  Views

  A

  As a Post Mortum, the issue I originally had was with the Scheduler Process. So, if you assign an image to a PC, see the upload task in the web interface, but the client is not starting the upload process when you PXE boot it, check the fogscheduler.log in /opt/fog/logs to make sure it is picking up the task in the first place. My “fix” was a fresh install because something was busted with my install.
• X

  Problems with Solid State Drives?
  • xburnerx00  

  3
  0
  Votes
  3
  Posts
  19
  Views

  X

  Thanks for the information. Relieves some of my worries.
• S

  The future of partclone and therefore FOG as it is
  • Sebastian Roth  

  96
  0
  Votes
  96
  Posts
  644
  Views

  

  @Sebastian-Roth OK I’ll hold off until I get the green light from you.
• T

  Problems with using-fog-to-pxe-boot-into-your-favorite-installer
  • TmGard  

  22
  0
  Votes
  22
  Posts
  1649
  Views

  B

  I hate to beat a dead horse, but I just wanted to say thank you for this in depth tutorial. It is amazing. Thank you!
• C

  Bandwidth line colours
  • CoxM  

  7
  0
  Votes
  7
  Posts
  236
  Views

  C

  @Hanz Amazing, thank you! worked a treat.
• A

  Fog Basic User
  • Atton  

  4
  0
  Votes
  4
  Posts
  34
  Views

  A

  The access Control Plugin was exactly what I was looking for. Thanks! I didn’t know about the plugins.
• G

  Client Stop at: Starting haveged: OK
  • gianni  

  2
  0
  Votes
  2
  Posts
  26
  Views

  

  [MOD Note] Duplicate post from here: https://forums.fogproject.org/topic/13451/client-stop-at-starting-haveged-ok I’m going lock this thread. All comments should use the link thread.
• O

  Fog 1.5.6 for different hardware
  • Olduser  

  2
  0
  Votes
  2
  Posts
  50
  Views

  

  @Olduser What the image sysprep’d? Did you include the 9020 drivers into your golden image? But the likelyhood if you sysprep’d the image then the native win10 drivers will probably work on the 9020. Other issues, is the 7760 in uefi or bios mode? The same goes for the 9020? You can only capture and deploy uefi based images to uefi base target computers. You can’t mix bios hardware with uefi captured images.
• R

  If I create a fog server, can I push an image to a friends computer remotely via the internet if he has ipv4 pxe option in his bios?
  • Razuel  

  4
  0
  Votes
  4
  Posts
  77
  Views

  

  @Razuel remote management is what it sounds like. Public facing meaning the fog server is accessible from the internet. While technically possible to image, it really wouldn’t be the best experience. By remotely managed we simply mean you can change the host name, tell it to join a domain, configure printers, set up snapins, and that kind of thing. I wouldn’t recommend imaging over the internet as it would be constrained by your internet upload speed and the remote sides download speed. Usually download speed is fine anywhere but upload is typically limited much more so.
• P

  FOG : Main sites and Branches organisation
  • processor  

  14
  0
  Votes
  14
  Posts
  81
  Views

  P

  @george1421 Thanks, I’ll give a look at it this weekend.
• P

  How to change how many clients i can image
  • pyrate31  

  8
  1
  Votes
  8
  Posts
  29
  Views

  P

  @george1421 nevermind i found what i was looking for…this is all i wnated to do FOG image queue size too small By default, FOG unicast is set to image no more than 10 machines at a time. Other devices will be placed in a queue and wait for another machine to complete. If you want to increase this queue number, you have to do it in two places. First, under Storage Management > Select your Default Member > Change the figure in Max Clients to the desired number. Second, under FOG Settings > Expand General Settings > Change the figure in FOG_QUEUESIZE to the desired number.
• 

  Deploying Windows Server?
  • THEMCV  

  7
  0
  Votes
  7
  Posts
  51
  Views

  

  @THEMCV said in Deploying Windows Server?: Can feature installations be set with Snapins? While I don’t use snapins, features can be added with powershell such as in: Import-Module ServerManager Add-WindowsFeature FS-NFS-Service
• 

  image to SSD, do I need to do anything special, or am I over thinking this.
  • Roger Saffle  

  2
  0
  Votes
  2
  Posts
  56
  Views

  

  @Roger-Saffle There is nothing you need to do with fog, its your final destination OS that has control of the disk once it is launched. FOG Image format wise there is no difference between a HDD, SSD, or NVMe drive once fog captures it. Once FOG deploys the image you will not be able to tell the if the source image was from a ssd, hdd, or vmdk file. As a test deploy the same image to the 3 different disk structures (hdd, ssd, nvme drive). On the hdd you should get 50-90MB/s sequential speed using crystal disk mark. For the ssd you should get 350-520MB/s sequential speeds depending on your sata attached ssd. For the NVMe drive 700-900MB/s sequential transfer rates. All from the same source image.
• W

  Change Hostname Early / Client Hostname Changer
  • willian  

  10
  0
  Votes
  10
  Posts
  99
  Views

  W

  @george1421 the next time I need to change something in the golden image I will test these scripts. Thank you.