General

• 

  Useful Scripts
  • Tom Elliott  

  7
  6
  Votes
  7
  Posts
  6435
  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
  32012
  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
  87429
  Views

  H

  @iyoung good
• C

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

  2
  1
  Votes
  2
  Posts
  3796
  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.
• P

  FOG : Main sites and Branches organisation
  • processor  

  6
  0
  Votes
  6
  Posts
  14
  Views

  P

  @george1421 Hi, This seems to be the best for our case. I did what you suggested but something is not working as expected. I configured a new node on default storage group on main server. This how configured it : ip : ip of the branch server image path : /mnt/FOG same as it is configured on the branch server ftp path : same interface : ens160 (outgoing interface of the main server) management username : fogproject management password : same as it is configured on branch server. All other settings left as default. On the branch server default storage node : master is now unchecked. I can see the new storage on main server dashboard with space available. But the replication is not working as expected this is what I can see in the logs : [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.mbr (FR3-FOG-01) [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.minimum.partitions (FR3-FOG-01) [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.original.fstypes (FR3-FOG-01) [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.original.swapuuids (FR3-FOG-01) [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.partitions (FR3-FOG-01) [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1p1.img (FR3-FOG-01) [06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1p2.img (FR3-FOG-01) [06-18-19 9:09:06 pm] | CMD: lftp -e 'set xfer:log 1; set xfer:log-file /opt/fog/log/fogreplicator.W10_Remote-20190523-HS-745-755.transfer.FR3-FOG-01.log;set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c --parallel=20 -R --ignore-time -vvv --exclude ".srvprivate" "/mnt/linux_iSCSI/FOG/W10_Remote-20190523" "/mnt/FOG/W10_Remote-20190523"; exit' -u fogproject,[Protected] 10.69.0.11 [06-18-19 9:09:06 pm] | Started sync for Image W10_Remote-20190523-HS-745-755 - Resource id #93271 [06-18-19 9:09:06 pm] * Found Image to transfer to 1 node Any idea of what is going wrong?
• 

  Deploying Windows Server?
  • THEMCV  

  4
  0
  Votes
  4
  Posts
  19
  Views

  

  I’ve deployed to physical, Hyper-V and Vmware without issue.
• 

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

  2
  0
  Votes
  2
  Posts
  20
  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
  82
  Views

  W

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

  Replication Inquiry
  • blainey  

  4
  0
  Votes
  4
  Posts
  9
  Views

  S

  @blainey Replication needs FTP (random ports for the data channel) and HTTP.
• E

  Dual Port NIC Config
  • explosivo98  

  6
  0
  Votes
  6
  Posts
  44
  Views

  E

  After a few days of testing on a local network just using the onboard ethernet port going to a router this is already a heck of a lot easier than the previous imaging solution that I banged my head against for a month. Bare metal is definitely the way to be and I greatly appreciate the insight. I would have torn what remains of my hair out trying to figure out making that work with Virtualbox. Going from here, trying to get the final set up the way I described in my original post, it sounds like I need to look into the DHCP configuration to move the imaging to the two additional ethernet ports and off eno1, is that correct? Right now I have eno1, enp2s0f0, and enp2s0f1. eno1 will be supplying internet and I presume the other two will be on different gateways reaching out to the switch where the target PC’s will be connected to. Would this be something I can achieve using the built in tools?
• D

  Deploying BIOS Boot Order to multiple computers (booting to network 1st)
  • drumnj  

  5
  0
  Votes
  5
  Posts
  30
  Views

  

  @drumnj said in Deploying BIOS Boot Order to multiple computers (booting to network 1st): You said you return yours to “normal” boot (I take it hd 1st) What I was referring to here is with Dell and CCTK you can set a flag in the bios that basically says on the next reboot boot to the network. On reboot+1 boot what ever the default boot device is. So if you wanted to do an unattended imaging but your normal boot device was the hard drive you could push out a FOG snapin that called cctk on next boot-boot to the LAN, then schedule a fog deployment. If the fog client is installed it will reboot the target computer and then start imaging right away.
• Q

  fogproject user account ?
  • Qweeqweg  

  5
  0
  Votes
  5
  Posts
  45
  Views

  

  @Qweeqweg the change from using an account named “fog” to an account named “fogproject” is recent. in spite of directions, people kept creating and using an account named “fog” as their user account when setting up the server.
• S

  Chainloading sudden failure
  • svandam  

  4
  0
  Votes
  4
  Posts
  37
  Views

  S

  @Sebastian-Roth Alright, good to know for the future. Since I didn’t have a clear fix, I blew up the VM and am starting from scratch. There were only two images anyway.
• S

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

  91
  0
  Votes
  91
  Posts
  539
  Views

  Q

  @george1421 Well, potentially that was a resize bug in the inits if you’re using an NVME drive. Could also be the mount failing for some reason? Just some ideas.
• 

  This topic is deleted!
  • activateproductkey  

  2
  0
  Votes
  2
  Posts
  16
  Views
• S

  How does TPM on Win10 react to PXE'ing Ubuntu LiveCD?
  • smellyonionman  

  3
  0
  Votes
  3
  Posts
  17
  Views

  S

  Thank you @george1421 for giving me such a complete answer. My greatest concern was looking as if I had attempted something like a cold boot attack, but if something onboard such as IME is going to show logs then I really wouldn’t bother. It’s not worth finding out if they care to distinguish, so thanks for your advice. In regards to potentially angering people like yourself, I’m grateful you were still fair to me! I didn’t take any steps that were contrary to IT’s mandate, we are after all a team. Maybe they will approve the request. :) FOG was a means to satisfy a curiosity (NDI) but will prove to be much more useful and fun with my own half-broken Desktops. Have a good one!
• Z

  How to PXE boot to a Windows PE ISO
  • zaboxmaster  

  6
  0
  Votes
  6
  Posts
  70
  Views

  

  @zaboxmaster Ah ok that is how G4D got into the picture. You didn’t use my steps exactly. That is ok you go there. The iPXE menu that you have will only work for BIOS systems and not uefi. There are additional parameters that are needed for UEFI. I thought I had the answers hidden in that thread, but I must have removed them. This will be from memory (I have it in a config file at home) In your line like initrd http://192.168.100.160/windows/10Pro-x64/Boot/bcd BCD you need to use the -n switch to make the line look similar to this for uefi. initrd -n BCD http://192.168.100.160/windows/10Pro-x64/Boot/bcd BCD Also you will need to change out the bootmgr.exe for the uefi equivalent. initrd -n bootmgr.efihttp://192.168.100.160/windows/10Pro-x64/bootmgr.efi bootmgr.efi Again this is posted from a rusty old memory, so it should be close but not exact. Edit1: While this isn’t where I started from look a the uefi section here ref: http://mistyrebootfiles.altervista.org/documents/TinyPXEServer/files/winpe_wimboot.htm
• D

  how to clone a windows drive without sysprep
  • dongtuuyenblackpeony  

  2
  0
  Votes
  2
  Posts
  58
  Views

  S

  @dongtuuyenblackpeony Sounds very strange because the iPXE menu/task execution simply is selected via the MAC address of the client machine. That should be no different whichever state the machine is in. For example, you could even wipe the whole disk or install Linux on the drive and it should still behave same on the PXE boot! Sorry, don’t want to sound rude but have you used FOG to capture/deploy images before? Just want to make sure you know the process.
• P

  SOLVED Fog gets stuck at "Erasing Tables"
  • pdit  

  5
  0
  Votes
  5
  Posts
  36
  Views

  P

  I didn’t update kernel. it still working for me. Thanks,
• P

  dhcp issue - Lenovo E73 - Realtek RTL8111GN
  • pdit  

  45
  0
  Votes
  45
  Posts
  228
  Views

  S

  @pdit So it’s probably something that changed in the Linux kernel that is causing this issue. I’d like to track this down but I don’t think I’ll find the time to do so in the next months. You should be able to switch between different kernels to see which version first had the issue. Find all the different kernel versions in the FOG web UI or here: https://fogproject.org/kernels/