FOG Server 1.5.9.x Setup with One Network Card

Managing multiple operating system images or edifice an OS from ISO is a critical part of whatever IT infrastructure. If done well by using an image management system, it can salvage a lot of time. Costless-Open Source Ghost (FOG) is a Linux-based server solution that can be used for network cloning and management.

FOG allows y’all to create, manage and deploy various Mac Bone, Linux, and OSX versions. Likewise, it supports multiple Linux distributions like Fedora, Debian, Centos, Ubuntu, etc. This server-based cloning solution tin drastically help reduce installation or update fourth dimension for new labs or computers.

It is important to understand that disk imaging or cloning means copying elements from 1 drive to some other. Yous can create an ideal image with the desired software and settings, upload it to a server and distribute it to other devices from at that place. In the case of FOG, you lot tin upload and deploy it via a Pre-Kicking execution environment.

This article is a 1-stop guide covering an introduction to FOG, its installation, configuration, FOG-Client direction, and a detailed Image Capture process.

Basic Components

As a Linux-based server, it can deploy both Windows and Linux images. However, it is essentially built to manage and deploy Windows operating systems. Such that, its user manual describes Linux support every bit primitive.

After installation, information technology requires you to utilise Linux command-line interface to operate the solution and deploy a PHP-built spider web user interface. FOG supports PXE-boot forth with DHCP, iPXE, and TFTP. Besides, it entirely relies on the client’south MAC addresses to runway PCs.

System Requirement

  1. Requires customized disk segmentation for prototype allotment.
  2. Minimum 2 GB retentivity
  3. ane or 2 5 CPU for fast image compression/decompression
  4. Minimum 100 GB hard disk drive

FOG vs. Windows Deployment Services (WDS)

Microsoft imaging solution WDS requires a Windows server 20XX license and is a lot complex. It is an open-source solution that handles heterogeneous hardware imaging with a loftier-time setup and learning investment.

Even though it is used to build large environments, the toll of fourth dimension goes up with the increasing number of machines. Besides, it requires Windows DNS and DHCP servers. In comparison, FOG is a solution for homogeneous imaging, with a low to medium toll and learning investment range, with several other multiple features and advantages.

FOG Features

  1. Automatically logs out a user after a period of inactivity.
  2. Remotely manages installed printers, performs shutdown/reboot.
  3. Allows joining the device to an Agile Directory domain and change hostname subsequently deployment.
  4. Allows joining the organization to an Active Directory domain.
  5. Allows managing images past adding target device MAC accost in the FOG’s repository.
  6. Allows performing FOG tasks on the client’s PC or target automobile.
  7. Allows selecting an private or grouping of hosts from the Hosts or Group Management section from FOG UI to deploy images.
  8. Allows removing blocks and restore deleted files.

Installation and Configuration

To begin the installation process, go to the web browser and download FOG from the project’s website.

Or type the
cd /opt
command in fustigate and copy the download link from the website. Use the
wget

utility to download FOG in the opt folder.

[electronic mail protected]:~$ sudo wget https://github.com/FOGProject/fogproject/archive/1.five.9.tar.gz

Annotation the download version
1.v.nine.tar.gz
and extract the file using the post-obit command.

cd
into the FOG bin directory
/fogproject-1.5.9/bin
to open the FOG shell script
installfog.sh.
Use the following command to get started.

[email protected]:~$ cd /opt/fogproject-1.v.ix/bin
[electronic mail protected]:~/fogproject-ane.v.nine/bin$ sudo ./installfog.sh

Notice that it automatically identifies the installed Linux distribution. Follow these step-by-footstep instructions to reply the series of questions to begin the installation process.

  • Choose
    N
    to showtime a normal installation;
  • Do not modify default NIC;
  • For FOG DHCP settings, printing No if you already have a DHCP configured;
  • Press “enter” to leave gateway, IP address, and DNS settings. Hence select the default settings such that the FOG server uses the device’due south current IP address;
  • Choose the default hostname;
  • Cull a language pack if needed; and, finally,
  • Choose to continue the installation.

FOG will at present automatically install all the necessary components. Some old versions of Ubuntu inquire to set a MySQL password during installation; nosotros tin can exit it empty equally it is not a security risk. However, we can make these changes later, if required.

After installation, you can navigate the FOG server via Web Browser. Enter the following details in the search bar:

https://fogserver(OR IP address for FOG Server)/fog/management

Earlier accessing the FOG dashboard, nosotros install or update the FOG database.

Click Update and enter the default credentials (username: fog; password: countersign) to admission the FOG dashboard.

Now, reboot the FOG server for a fresh showtime.

Further Configurations

USER Management

Navigate to the User Management icon in the dashboard. Go to
Full general>User Proper noun
and
General>Change Password
to change the default credentials.

**Optional**:
FOG also allows adding other users to create images and handle administrative tasks.

Setting DHCP Server Other than FOG

The higher up installation does not let FOG to provide DHCP services to the network. To enable the FOG client to PXE boot into the server through the network, it requires changes to the electric current DHCP server settings.

Go to your command line terminal and update the repository.

[e-mail protected]:~$ sudo apt-get update

Employ your favorite editor to edit the DHCP configuration file located in the <potent>/etc/dhcp </potent>directory.

[cc lang=”text”  width=”100%” height=”100%” escaped=”true” theme=”blackboard” nowrap=”0″]
[e-mail protected]:~$ sudo nano /etc/dhcp/dhcpd.conf

The DHCP server generally requires two options settings:

Option 66

Set an selection 66 to allow client kick requests to reach the FOG server.

Hence add the following line to the
dhcpd.conf
file in the
/etc/dhcp
directory for the client to look for the TFTP server.

option 66 <TFTP-server IP address>

Option 67

This option allows the PXE bootable device to look for the configuration files. Choice 67, too known every bit the default BIOS Boot-file name, is set to
ipxe.efi
in the newer UEFI models.

Whereas old hardware models with legacy BIOS firmware do non kicking with this file, set up the
filename
to “undionly.kkpxe” file.

Some other method to set up the
dhcpd.conf
file is past following the given template, with the correct network settings to start the dhcp server. The default dhcp settings offered past the FOG-server during the installation process do similar changes to the
dhcpd.conf
file.

Popular:   Difference Between Tennis and Pickleball

The
dhcpd.conf
file must expect like this:

#dhcpd.conf

option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
selection PXE.mtftp-cport code 2 = unsigned integer xvi;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout lawmaking iv = unsigned integer viii;
pick PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578

utilise-host-decl-names on;
ddns-update-style interim;
ignore customer-updates;
Next-server X.X.Ten.X;
authoritative;

log-facility local7;

subnet X.10.X.X netmask 255.255.255.0 {
    option subnet-mask 255.255.255.0;
    Range Ten.X.Ten.0 Ten.X.Ten.254;
    default-lease-time 21600;
    max-lease-time 43200;
    selection routers 10.X.X.Ten;

     grade “UEFI-32-1” {
    match if substring(choice vendor-course-identifier, 0, 20) = “PXEClient:Arch:00006”;
    filename “i386-efi/ipxe.efi”;
    }

    class “UEFI-32-2” {
    lucifer if substring(selection vendor-class-identifier, 0, twenty) = “PXEClient:Arch:00002”;
    filename “i386-efi/ipxe.efi”;
    }

    class “UEFI-64-1” {
    match if substring(option vendor-form-identifier, 0, xx) = “PXEClient:Arch:00007”;
    filename “ipxe.efi”;
    }

    class “UEFI-64-2” {
    match if substring(option vendor-class-identifier, 0, twenty) = “PXEClient:Arch:00008”;
    filename “ipxe.efi”;
    }

    course “UEFI-64-iii” {
    lucifer if substring(option vendor-class-identifier, 0, twenty) = “PXEClient:Curvation:00009”;
    filename “ipxe.efi”;
    }

    class “Legacy” {
    match if substring(pick vendor-class-identifier, 0, 20) = “PXEClient:Arch:00000”;
    filename “undionly.kkpxe”;
    }

}

Disk Paradigm Creation

The get-go task subsequently the FOG installation is to create an platonic machine (we will install Windows ten for this tutorial) and install all the required software to capture and indistinguishable the Bone on some other hardware.

Nevertheless, another prerequisite before creating an image is to deploy the FOG client that takes care of additional tasks offered by the FOG server Web UI.

FOG-Client Management

The FOG-client service allows lab in charge to perform tasks on the Clients device during the image boot process. Moreover, it enables the server to provide services to the client’s PC. These services vary from Auto log-off, hostname changes, display and printer direction to agile directory integration, user tracker, and many more.

Installation

Open an example of the FOG server in the windows ten web browser by typing
https://<FOG Server IP address>/fog/management. Go to the
Customer Settings
department on the dashboard and select the
FOG Client Download
department to download the MSI/Smart Installer.

Or type https://<FOG Server IP address>/fog/client/download.php? in the web browser to find the FOG client and download the installer.

Both client installers require similar installation steps.

Click adjacent on the installation screen and accept the license agreement.

Add FOG Server IP address every bit the server’due south name in the next screen.
Proceed the webroot name and the rest of the default setting.
Deselect the Enable Fog Tray option to remove the FOG symbol from the taskbar (optional).

Leave the default destination folder and follow the residuum of the installation process.

Reboot the machine and cheque the taskbar to find successful Fog-Client installation.

Car Approval

Since the windows deployment did not happen via FOG, the client is not trustworthy for the server and requires manual approval from the server.

Go to the
Host Direction
section in the dashboard, select
Listing all Hosts
and click on the machine with the recently installed Fog-Client and click on
Approve this host?

Popular:   How to Setup Your Own XMPP Server

However, machine image deployment via the FOG server does non require whatsoever approval and is considered trustworthy by the server.

Auto Registration at FOG

Now, the machine is in an ideal state to capture an image. Boot it from the network to enter a PXE Boot environment.

The screenshot above represents a successful PXE boot:

The PXE client brings the network link and requests an IP accost via DHCP. The DHCP server (X.Ten.X.Ten) provides the client motorcar with the IP-address/netmask, along with a
next-server
(FOG-server IP_address) and the bootable file “file name”
(undionly.kkpxe).
The PXE client now gets the undionly.kkpxe image from the
/tftpboot
directory via TFTP server.

Undionly executes and presents with the FOG boot menu afterward configuration.

The FOG boot menu states “Host is NOT registered”; it is unknown to the FOG. Scroll downwardly to “Quick registration and inventory” and select before default “kick from hard deejay”. After registration, reboot the client and close downward the machine.

Image Registration at FOG

This stride adds/registers an image to the FOG server. Such that, information technology captures the unabridged hard disk and all partitions.

Login to the FOG-server Web UI, select the
“Epitome Management”
section from the dashboard, and choose
“Create New Image”. Type in the new prototype name, leave default options as they are, and gyre down to click on ‘Add’.

Automobile-Image Association

Now associate the Window 10 image with the existing host in the Host Management section.

Click on the “Host Management”
section of the dashboard and select
“Listing All Hosts”
.

Select the host to capture an prototype. Get to the “Host Paradigm” drop-down menu and choose the recently added Window 10 image.

Creating Capture Task

The capture task instructs the FOG server to capture and store the hard disk drive content of the Windows 10 prototype whenever the machine boots from the network.

While in Host Direction of the FOG Web UI choose
“Bones Tasks” to select
‘Capture‘. Click on
“Task”; this allows changing the task imaging settings.

Image Capture

Make sure the host motorcar boots from the network when you initiate the capture procedure. Since the capture job is assigned to the host, you will notice a Partclone execution instead of the FOG boot menu.

Partclone reads the hard deejay content via the network and writes in the form of a compressed image file on the server. Afterwards successful image capture, the FOG updates the database, and the machine reboots.

The image is successfully captured and is gear up to deploy on other machines.

Conclusion

The article presents a detailed introduction to the Gratis Open up-source Ghost server solution and compares it with the Windows Deployment Solution (WDS). Information technology provides an in-depth tutorial on FOG installation and configuration. It also demonstrates the DHCP server setting to install FOG-Customer to PXE boot in the host machine for image capture. Lastly, it details the image capture process to facilitate readers with an easy-to-sympathize guide.

FOG Server 1.5.9.x Setup with One Network Card

Source: https://techblog.thcb.org/an-introduction-to-free-open-source-ghost-fog-linux-hint/