• New wiki article - Getting FOG

    3
    2 Votes
    3 Posts
    930 Views
    Wayne WorkmanW

    Since the feedback has been positive, I’ve cross-linked the old ‘upgrade to trunk’ and ‘getting fog’ articles. I also ask that when people request instructions on getting fog installed, we reference the newer ‘getting fog’ article.

  • PoC: Using FOG as a netboot server

    Locked
    3
    2 Votes
    3 Posts
    4k Views
    george1421G

    [Mod Note] I have locked this post to keep it tidy for others who may find it useful. Discussion is important around this topic. If you have a question on this post, please create a new thread, reference this post and also tag me in the post so I can find it. I will add links to those posts here so others may follow along without filling up this thread.

    Discussions regarding this post:
    https://forums.fogproject.org/topic/11216/netbooting-efi-with-fog

  • Resyncing FOG's service account password

    Locked
    1
    5 Votes
    1 Posts
    6k Views
    No one has replied
  • Clearing specific kinds of task types using SQL

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Add a Nas (QNAP TS-231) as a Storage Node (Fog v1.4)

    3
    3 Votes
    3 Posts
    3k Views
    No one has replied
  • Booting MDT 2013 LiteTouch with FOG

    25
    2 Votes
    25 Posts
    26k Views
    george1421G

    @zingaro TBH I have never tried in uefi mode.

    As for your note: if these are dell computers, when in uefi mode you need to enable the uefi network stack (on the network page) in the firmware. I assume other OS will have similar options. On the boot options, it will only show valid uefi boot sources so you do need to enable the uefi network stack for that option to show up.

    Your MDT boot image should contain the uefi boot kernel. In my case we use VMWare and boot our target computers directly from the mdt iso in uefi mode. They boot without an issue, but again I’m not sending the iso image across the network with pxe.

    I can confirm uefi booting via pxe works with these instructions tomorrow since I’m out of the office today for training.

  • FOG Snapin - Font installation (Windows)

    1
    4 Votes
    1 Posts
    1k Views
    No one has replied
  • Request tutorial videos here

    1
    3 Votes
    1 Posts
    714 Views
    No one has replied
  • Windows 10 1703 delete "this" if you use "CopyProfile" in unattend.xml

    Moved Solved
    1
    2 Votes
    1 Posts
    3k Views
    No one has replied
  • When rebuilding a fog server...

    6
    2 Votes
    6 Posts
    3k Views
    Wayne WorkmanW

    Replying to this older thread with a newer article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

  • Moving FOG's /images files off the root partition

    6
    1 Votes
    6 Posts
    6k Views
    J

    @george1421

    Thanks for the clarification. We’ve been caught with storage problems frequently enough that we know to use a separate disk volume for /images. For Snapins, we defined our processes when Snaps were much less capable than they are now. We use DFS on separate windows servers and leverage Samba as links under DFS on FOG storage Nodes for smaller sites. Our approach allows for easier tweaks to any Snapin by just editing the contents of some folders. No re-uploading to FOG and re-replicating a big ball of a Snapin. The only thing that replicates are the smaller changed files via DFS.

    I get the old linux ‘mandate’ to separate everything into it’s own volume, though the guys I’ve worked with didn’t do that at the disk level, but at the partition level (since most had to deal with a storage team and getting one large chunk of disk and partitioning it was easier than explaining things to the storage team). I’m good with the concept, but don’t follow it dogmatically. Instead I consider the use of the server. If the server is an appliance - does one thing for you, as FOG does - then a FOG server than boots Linux but doesn’t do FOG is of no value to the business. In this case, I don’t split volumes for everything. This goes for Windows and Linux.

    I haven’t had the problem you describe were the OS won’t boot, plus with VMs, it’s exceptionally easy to mount the VHD and free up space. I find that placing any hard limit on a specific folder (volume, disk, whatever) is an act of fortune-telling that will end up shutting down the app sooner than allowing all folders supporting an app use the space that’s allocated. I monitor everything with XYMON so I get alerts on disk consumption, but even without that, the run-time for the app is longer w/o partitions.

    I only partition where there can be rapid growth that necessitates expanding a volume - and the /images folder in FOG is the best example, when uploading is required (server hundred GB in one client possible).

    I know my thinking is contrary to what some feel are best practices in Linux, but I’ve been happy with the results… I don’t tend to lose the service the app/service provided because I miss-guessed the space log files need by 100MB.

    Just my opinion…

    Thanks
    Jim

  • How do I run FOG after installation?

    5
    0 Votes
    5 Posts
    5k Views
    george1421G

    @i00 FWIW: The last instructions left by the installer script did tell you the same thing. If you question what I’m telling you, rerun the installer (no harm doing this) and watch the prompts. It will use the prompts you first selected. The FOG wiki also is a great source of information on how to use FOG.

    But point taken, we probably should update the wiki.

    I’m glad you got it working. If you have questions post back to the forums.

    regards

  • Adding additional image storage space to FOG server

    3
    2 Votes
    3 Posts
    12k Views
    george1421G

    Part 2 FOG WebGui Configuration

    We need to create a new Storage Group. Go to Storage->Add Storage Group Enter a new Storage Group Name and Description Press Save/Update to create this new Storage Group.
    0_1500031509623_istore_group.png Note that now we have 2 storage groups (default and ImageStoreGroup2)
    0_1499989908064_new_storage_group.png Now we need to add a new Storage Node. Go to Storage->Add Storage Node.
    Enter the values in the storage node configuration appropriate for your setup. The key values to watch are the IP Address (fog server IP address), Is Master Node, Storage Group, Image and FTP Path. The rest can remain the defaults. Its worth noting that the Management Username and Management Password are related to the FOG server where we just mounted to the new hard drive. If you don’t know what these values should be you can always inspect the default storage node settings. Just copy and paste them from the default storage node configuration to this new storage node configuration.
    0_1500032048809_istore_node_p1.png
    0_1500032067873_istore_node_p2.png In the All Storage Nodes list note that the storage node ImageStore2 is attached to the ImageStoreGroup2 and that it is a Master Node in that storage group. This is important since only master nodes in a storage group can capture files.
    0_1500032405739_istore_nodes.png Now we will setup an image definition to store images to this new storage group. Goto Image Management->Create New Image. Enter the Image Name and select ImageStoreGroup2 for the Storage Group. Fill in the remaining fields as you would normally for the image.
    0_1500032769977_new_image1.png Update your host to use this new image definition.
    0_1500033275647_host_def1.png At this point we can schedule an image capture for this host. Go ahead an schedule a capture task for this host. Below is a screen shot of the capture task as its running. The key thing to note here is that the Working with node points to our node definition that is pointing to /images2 directory. (Wh00t!!)
    0_1500032982805_active_task1.png You can also confirm that the image is being saved to the /images2 directory by monitoring the partclone display.
    0_1499990078263_partclone1.png We are done.

    As you can see from this tutorial, its possible to add a second hard drive to your FOG server to add additional storage space by simply creating a loop back storage node definition. There are a number of steps involved with setting this up, so take it slow and follow each step exactly.

  • Update Partclone program

    2
    0 Votes
    2 Posts
    1k Views
    Q

    I don’t believe there are currently steps designed for it. When Partclone has a new release, FOG tends to include it in a future update.

    Do note that FOG does not use the master branch of partclone as that’s considered unstable/experimental.

    If you still want to try, you’ll have to replace it in the init files. But these get overwritten with new FOG updates

  • 1 Votes
    4 Posts
    3k Views
    dl550D

    Hello,

    The book on FOG 1.4 is printed and available.

    For the English version, it will be necessary to wait until the French version is widely distributed.
    The current version requested: 4 years work of use, tests and more than 10 months of writing.

    https://mil2pil-fog.alwaysdata.net/produit/livre-fog-1-4-free-open-script-ghost-installation-configuration-utilisation/

    Cordially.

    Didier LACOMBLEZ

    Bonjour,

    Le livre sur FOG 1.4 est imprimé et disponible.

    Pour la version anglaise, il faudra attendre que la version française soit largement diffusée.
    La version actuelle a demandée : 4 ans travail d’utilisation, de tests et plus de 10 mois de rédaction.

    https://mil2pil-fog.alwaysdata.net/produit/livre-fog-1-4-free-open-script-ghost-installation-configuration-utilisation/

    Cordialement.

    Didier LACOMBLEZ

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • How to setup FOG 1.4.3 on Hyper-V

    3
    1 Votes
    3 Posts
    2k Views
    T

    Thanks for the feedback Wayne! I will make a note of it on the post!

  • Fedora 25 tutorial

    1
    0 Votes
    1 Posts
    765 Views
    No one has replied
  • Installed Fog, and what now?

    4
  • FOG-casting across VLANs (subnets)

    5
    1 Votes
    5 Posts
    4k Views
    george1421G

    Part 2 Pfsense Router setup

    In this design, the pfSense router will perform 4 different functions.

    Provide the dhcp addresses to the clients on the deployment network [192.168.23.0/24] Provide the necessary dhcp boot options to pxe boot the clients on the deployment network Act as a normal router to route traffic between the subnets Act as a IGMP route (via its built in IGMP Proxy server). The IGMP server will listen on its defined upstream interface [LAN] for any defined multicast streams and rebroadcast the stream on any of the defined downstream interfaces [WAN]. Please note I’m only using the concepts of LAN and WAN as interface names. I could have just as easily used em0 and em1, but inside pfSense they reference the logical names of LAN and WAN exclusively. To avoid confusion I’ll continue to use those labels through this document, just understand the are label and not based on functional intent.

    I’m not going to go through the setup of the pfSense router since there are many fine examples of setting up pfSense as a basic router. I will go through the settings I changed to configure the igmp proxy setting.

    In the graphic above I configured the pfSense router’s

    Set the LAN interface address to 192.168.50.250/24
    0_1495554662259_Interfaces_ LAN.png

    Set the WAN interface address to 192.168.23.1/24
    0_1495554685442_Interfaces_ WAN.png

    Configured the dhcp server on the WAN interface to issue IP addresses from 192.168.23.10 to 192.168.23.250.
    0_1495555318851_Services_ DHCP Server_WAN1.png

    For the imaging network, the default route points to the pfSense WAN interface of 192.168.23.1
    0_1495555352459_Services_ DHCP Server_WAN2.png

    Configured the netboot section of the WAN’s dhcp server to send out the {next-server} of 192.168.50.100 with a bios {boot-file} of undionly,kpxe, ia32 uefi boot file of i386/ipxe.efi, and ipxe.efi for the x64 uefi boot file.
    0_1495555364450_Services_ DHCP Server_WAN3.png

    In pfSense Advanced Configuration I disabled all firewall rules. In this setup I want pfSense to act as a normal unrestricted router and not as a screening or firewall appliance.
    0_1495556193981_System_ Advanced_ Firewall_NAT.png

    You will need to go into the firewall rules and add one rule to each interface (LAN and WAN) that is an allow all to any
    WAN rule
    0_1495558034751_Firewall_ Rules_WAN1.png
    LAN rule
    0_1495558047051_Firewall_ Rules_ LAN1.png

    With the static route configured on your FOG server and the pfSense router now setup on the network, you should be able to ping the deployment network’s router interface [WAN] from the fog server. If you can’t then something is setup incorrectly on the iP router side. Don’t proceed until you have basic IP routing working correctly.

194

Online

12.3k

Users

17.4k

Topics

155.6k

Posts