Use dnsmasq on the fog server to supply the pxe boot information.

The quick steps are this.

1. Remove the pxe boot information from your router.
2. Install dnsmasq service from your linux distribution’s repo
3. Make sure its at least version 2.76 by issuing this command at the fog server’s linux command prompt sudo dnsmasq -v The version needs to be 2.76 or later.
4. Create a configuration file called ltsp.conf in /etc/dnsmasq.d directory.
5. Paste this content into that file.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,<fog_server_IP>

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=<fog_server_IP>,proxy

6. Be sure to replace <fog_server_ip> exactly with the IP address of your fog server. Be aware that <fog_server_ip> appears multiple times in the config file.
7. Save and exit your text edit.
8. Issue the following command to restart dnsmasq service sudo systemctl restart dnsmasq
9. Ensure that dnsmasq service is running in memory by issuing this command ps aux|grep dnsmasq. You should see more than one line in the response. If its running then go to step 10.
10. Ensure that dnsmasq starts when the system is rebooting with sudo systemctl enable dnsmasq
11. PXE boot a target computer.

NOTE: If you are supporting multiple foreign subnets (not on the same subnet as your dnsmasq server, you will need to add additional with dhcp-range statements that properly describe that foreign network segment. If you fail to do this the dnsmasq server will not respond to the request from your dhcp-relay service an example of what is needed is below:

dhcp-range=<fog_server_IP>,proxy
dhcp-range=192.168.100.0,proxy,255.255.255.0
dhcp-range=172.16.45.0,proxy,255.255.255.0

Dhcp option 93 to hardware type table

DHCP option 93 Client architecture|
0 Standard PC BIOS
6 32-bit x86 EFI
7 64-bit x86 EFI
9 64-bit x86 EFI (obsolete)
10 32-bit ARM EFI
11 64-bit ARM EFI

Introduction

First I have to say this article contains the results of many brilliant people and is not my content. I’m only assembling this information into a consistent document instead of spread around buried in posts and responses. My intent is to not dig into the details behind the scripts or how to tweak them for your needs. You can read the links below to figure out why things are being done the way they are. I wanted to create a tutorial that was as close to a cut and paste to get driver injection going in your environment. Now I will primarily focus on Dell hardware for the main reason that Dell does supply driver archive files (known as .CABs) that can be downloaded and extracted quickly to create the driver structure. I’m sure that HP, Lenovo, and others have similar driver packs.

You can download the Dell driver cabs for your hardware from here: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-command-deploy-driver-packs-for-enterprise-client-os-deployment

Reference links:
https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script-under-construction
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script
https://forums.fogproject.org/topic/8878/fog-drivers-script-will-not-run-correctly-in-postdownloadscripts/46

In this series if posts I plan on outlining what the FOG post download script is, what its about, and how to use it to your advantage with image deployment.

I’ve debated with myself if another post was needed since Lee https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins and I https://forums.fogproject.org/topic/7391/deploying-a-single-golden-image-to-different-hardware-with-fog have written tutorial about them in the past.

Where I want to explore with this series of posts is more about the background behind its function and to cover some of the script elements from Lee’s and my previously linked tutorials.

First of all lets get a little background here and some terminology defined. The FOG image deployment system consists of three main components:

1. The FOG management environment. The FOG management environment is the FOG server itself, which is responsible for planning, scheduling, instructing and documenting the image deployment.
2. The FOS (FOG OS) target engine {need better name here}. The FOS target engine, or FOS (as it will be known in this document) is responsible for capturing and deploying images from the defined storage node, as well as other actions on the target computer. FOS is actually an FOG Project created high performance linux operating system that was specifically constructed to image target computers. We have to remember for the rest of the tutorial, FOS is a linux based operating system that is used to deploy any OS image to your target computer.
3. FOG Client. This is an add on utility service for windows and linux, which is installed on the final or target OS. The FOG Client queries the FOG server for instructions and actions. I’m not planning on discussing the FOG client during this tutorial since it is out of scope in regards to post installation scripting.

The FOG Post install scripts give FOG system admins the ability to inject actions in the image creation process. To allow this custom scripts to run the developers added an external call into the image deployment sequence. Just after the image is placed on the target computer’s storage device, the FOG server calls a script in the /images/postdownloadscripts directory (on the FOG server). That script is called fog.postdownload. The fog.postdownload script is created when the FOG Server is installed. In its default state the script doesn’t do anything much. It is just a place holder to call your custom post install scripts. As I mentioned the fog deployment process calls this fog.postdownload bash script just after the image is placed on the target computer’s storage device. Once all of the external post install scripts have completed the FOG server completes the imaging and data recording steps.

While the post install scripts are stored on the FOG server in the /images/postinstall directory, they are executed by FOS running on the target host. So you have to remember when writing your post install scripts, they execute from the perspective of the target host. The post install scripts have limited access to resources on the FOG server (outside of the /images directory), but have full access to the target host. As noted above, these scripts run on a linux OS, so any resource (programs) available to linux operating systems can be run against the target host. I want to make this distinction to make it clear that FOS is linux and not MS Windows based. So you can not run MS Windows based applications, like DISM, in your post install script. FOS and linux is very powerful, but also limiting in some ways. As long as you are aware that MS Windows based applications can not run in a post install script then you should have little trouble. There are some cross over applications that are compiled for both MS Windows and linux, you just need to ensure you have the correct application for the OS and architecture (IA32 or X64).

The developers found this issue to why the log file grew so big (after almost a year of log file collection). The log file will now be capped at the log file maximum set by the fog configuration settings. This was just a fluke case that caused this file to grow to an abnormal size.

The fix / log file limiting code will be in 1.3.5RC11 when its released.

What you need to understand that the FOS Engine (the customized linux operating system that captures and deployed images on the target computer) is a complete linux OS. It is built with 2 halves. The first part is the the kernel (bzImage) which contains the core linux functions as well as the compiled in device drivers. And the second part is the virtual hard drive (inits) which contains the linux utilities, programs, and fog command scripts. When you PXE boot a target computer into the iPXE menu, certain iPXE menu options will send the bzImage and inits files to the target computer. The iPXE menu will also send specific kernel parameters to tell the FOS Engine (linux) how to react when it boots.

You can take the FOS Engine (bzImage and inits) and just as easily boot directly from a usb flash if you use grub as your boot loader. The FOS Engine will boot from the USB stick without requiring the FOG server to be online. The FOS Engine won’t do much without the proper kernel parameters being passed from the FOG server. But in the end FOS is a specialized, high performance, standalone linux OS.

Now for specifics, I don’t have the details from inside FOS, but I suspect there is something in /etc/init.d that calls the main fog script called /bin/fog that script. The fog master script reads in the passed kernel parameters and then selects the proper task to execute.

Preface

The bits I’m going to cover here are the general outline of what needs to be done to create and deploy a hardware independent image across your fleet of computers. In this tutorial I’m going to discuss how to do this with Dell computers. I know this process works with Lenovo, Intel NUC, and a few others with some caveats. I’m going to touch on some steps that you need to do in MDT to build your universal reference image, but I’m not going to discuss how to setup MDT to create your reference images. There are plenty of examples on the internet on how to do this.

This process makes use of a custom script that gets executed post image deployment but prior to the reboot of the FOS client. This step is vial since we need to make some tweaks to the windows environment pre first windows boot. This is the key. I can’t/won’t share that script I created because of my contract with my employer, because it is derived work because of my employment. So that script is intellectual property of my company. I’ve held the job title of unemployed, its not a great title. The pay stinks, the stress level is high, but the hours are great. I don’t plan on going there any time soon, so no script for you. BUT, sitting here on my zorin (ubuntu) dell laptop I should be able to reverse engineer the important parts to give the crafty scripters here the tools they need to create their own post install script.

Our master image is created following the standard Microsoft SOE guidelines, meaning MDT to build the reference image, sysprep to reseal the image, use a custom unattend.xml file (required to make this process work for Win10) and some disk imaging tool to capture and deploy the image to the target hardware. In this process sysprep is mandatory since we want to create a single image that can be deployed to any hardware. The generalize process of sysprep removes all hardware references (for the reference image) so that when windows first boots it goes through the hardware discovery process. Without sysprepping the image the process I’m going to discuss will not work. So use sysprep.

When I started out creating this process for FOG, I began with the process we created for deploying Windows XP from a usb stick using Ghost. In that process we would automate the image deployment with ghost to lay a hardware independent image onto the target hardware and then detect the current hardware using a DOS program that would query smbios to get the target hardware. Then once the target hardware was known we would move the correct driver pack into a location where windows would find it on the first boot. This worked extremely well with Windows XP. So I took the knowledge that I had from that process and tried to do something similar with FOG.

I do have to say I did not think up this entire process all by my self. I did start the design base on the information found on this wiki page. https://wiki.fogproject.org/wiki/index.php?title=Auto_driver_Install This page and associated scripts gave me just what I needed to take our xp/ghost process and covert it to windows 7/FOG. So without that wiki page the remainder could not be possible.

NOTE: Changes in FOG's code since this article was written have made it harder to use NAS' as storage node with FOG. If you use a NAS with FOG 1.5.x and beyond the FOG replicator will continue to cycle and recopy files over and over again.

Part 1 NAS Setup

So far I’ve setup what should work from the synology NAS side of the fog storage node. This has NOT been proven to work just yet. So far the synology nas has been configured to what “should work”. On my test NAS I’m using DSM 6.0.

The following is just my short hand notes that will be used to create the actual tutorial. I’m out of time tonight to complete the docs for this.

The first thing we need to do is setup our NAS with the required network shares. To do this you need access to the Synology NAS’s web console. Log into the web console as admin and do the following.

1. Control Panel->Shared Folder
   Create new share
   Name: images
   Location: volume 1
   Checked Hide this shared folder in My Network Places
   Checked Hide sub-folders and files from users without permissions
   Press OK
   NFS Permission (tab)
   Create new Permission
   Hostname or IP: *
   Privilege: Read/Write
   Squash: No mapping
   Security: sys
   Checked Enable asynchronous
   Checked Allow users to access mounted subfolders

2. Control Panel->Shared Folder
   Create new share
   Name: snapins
   Location: volume 1
   Checked Hide this shared folder in My Network Places
   Checked Hide sub-folders and files from users without permissions
   Press OK
   NFS Permision (tab)
   Create new Permission
   Hostname or IP: *
   Privilege: Read/Write
   Squash: No mapping
   Security: sys
   Checked Enable asynchronous

3. Control Panel->Shared Folder
   Create new Share
   Name: tftpboot
   Location: volume 1
   Checked Hide this shared folder in My Network Places
   Checked Hide sub-folders and files from users without permissions
   Press OK
   NFS Permission (tab)
   Create new Permission (we only need this nfs shared for setting up the storage node)
   Hostname or IP: *
   Privilege: Read/Write
   Squash: No mapping
   Security: sys
   Checked Enable asynchronous

4. Control Panel->File Services
   Select Win/Mac/NFS (tab)
   Checked Enable NFS

5. Control Panel->File Services
   Select FTP (tab)
   Checked Enable FTP service (no encryption)
   Checked Use the default port range

6. Control Panel->File Services
   Select TFTP (tab)
   Checked Enable TFTP service
   TFTP root folder: tftpboot (this is the share name we created above)

7. Control Panel->User
   Select User (tab)
   Create user foguser
   Name: foguser
   Description: FOG User
   Password: fogremote1 (pick your own secure password)
   Conform Password: fogremote1
   Checked Disallow the user to change account password
   Press Next
   Join to group: users
   Press Next
   images: RW
   snapins: RW
   tftpboot: RO
   Press Next
   (Assign quota as needed)
   Press Next
   Assign application permissions: None
   Press Next
   Speed limiting: None
   Press Next
   Press Apply

8. Control Panel->User
   Select the Advanced (tab)
   (scroll way at bottom)
   Under User Home
   Checked Enable user home service
   Press Apply

That completes the setup of the Synology NAS.

In the next part we’ll test the network shares we setup above and create the remaining flag files and directory structure needed to transform the Synology NAS into a FOG storage node.

Setting up the foundation for installation

Hopefully this setup will be pretty clean and easy (just hoping…)

In this tutorial, I’ve personally setup each distribution and booted it into a virtual machine. I didn’t run the installer to completion, but I did ensure the installer was running as far as I took the install (unless otherwise noted).

These setups were only tested with a bios (legacy mode) target computer. They WILL NOT work with uefi systems. For uefi based systems they have their own kernel requirements and options. The intent of this tutorial was to show its possible to boot your installation media via pxe booting.

First we need to setup the storage locations for our boot images. The plan is to put the installation media on the /images nfs share and the boot kernel and initfs in the tftp boot directory.

mkdir /images/os
mkdir /tftpboot/os
mkdir /mnt/loop

For the foundation setup that should do it. On to the OS specific configuration…

Link to Windows 7 & Windows 10 BIOS Mode Only
Link WinPE 10 for BIOS and UEFI based systems
Link to Centos 7
Link to Ubuntu 16.04.03
Link to Ubuntu Desktop 19.10
Link to Ubuntu Server 19.10
Link to Ubuntu 17.10 Desktop
Link to Ubuntu 16.04.03
Link to Linux Mint 18.1
Link to Linux Mint 19.1 Cinnamon
Link to Debian 9.2
Link to OpenSuSE Leap 42.3
Link to Fedora Workstation v26
Link to Fedora Workstation v27
Link to Ubuntu Desktop 17.10
Link to installing Samba on your FOG server
Link to Kali Live 2017.3
Link to ESXi v6.5u1
Link to ESXi v6.7u2
Link to SystemRescueCd 5.2.2 x64
Link to GParted 0.33.0 x86
Veeam Agent Rescue DVD
Acronis 2018 (WinPE version)

@julianh A SSD for only the OS will not add much value making FOG go fast. The critical data path is from /images -> nfs -> network -> target computer.

We have seen (sometimes) the FOG Admin will use/change/modify the linux user fogproject’s user account properties and password (note: versions prior to 1.5.6 use fog as account name). This is generally a bad idea to use a service account for normal system maintenance. In fog’s case if someone outside of the FOG installer changes this account your fog installation will become broken.

Understand this linux user account fogproject (fog if you run 1.5.5 and earlier versions) is not the same as the default WebGUI administrator of the same name (fog). We are discussing resetting fog’s linux service account fogproject.

You will typically see this error when trying to capture an image to the FOG server. FOG will throw an error like:

Reattempting to update Database.... Failed

or

Message: ftp_login(): Login incorrect., Host: xx.xx.xx.xx, Username: fogproject

The following is the procedure for resyncing the fog service account. This must be done while logged in using a linux user account other than fogproject

1. Review the file /opt/fog/.fogsettings (this is a hidden file)
2. In that file there is a entry called password=
3. Capture that password. You will need it to reset the FOG server.
   Hint: I can tell you its much easier to do these steps by connecting to your fog server using putty from a windows computer. Copy and paste works great using putty (free terminal program).
4. Now reset the linux user fogproject’s password with sudo passwd fogproject
5. Now go to the FOG WebGUI and FOG Configuration->FOG Settings->TFTP Server and ensure the password listed in FOG_TFTP_FTP_PASSWORD matches the password you collected in step 2.
6. While still in the FOG WebGUI goto Storage Management->All Storage Nodes select the default or storage node in question.
7. Ensure that Management Password matches the password you collected in step 2.
8. Now finally back in the linux console of the fog server, navigate to where your fog installer files are (typ either /root/fogproject or /opt/fogproject) and rerun the fog installer (./bin/installfog.sh) to realign the remaining bits…

Once these steps have been completed your FOG server should be happy with you again.

@Sebastian-Roth I would think is OK. Can we comment out the ipxe.efi and leave it in the config, but then add the snponly.efi to the installer? As long as people are deploying contemporary computers snp is value, but if the fog tech has primarily an old fleet just being able to uncomment one and comment the other would be an easy instruction fix from a support standpoint.

@Sebastian-Roth FWIW, I read (somewhere) the Mac T2 compatibility was going mainstream in the 6.x series of linux kernels, so this one-off patched version shouldn’t be necessary once we have the linux kernel 6.x version in FOS Linux. It looks like 6.1.x is in long term support now.

@fagner-patricio OK so you have the latest version of the kernel. So lets debug a bit more.

Manually register this computer with FOG. You will need the mac address of the network adapter. You will create a host definition file with this action. Connect the host to an image (doesn’t matter which one at the moment as long as it exists).

Now schedule a deployment task to this computer. But before you hit the schedule task button, tick the debug checkbox. Now schedule the deployment task.

PXE boot the target computer. The computer should go right into imaging and not stop at the fog iPXE menu. After a few screens of text that you have to clear with the enter key you will be dropped to the FOS Linux command prompt on the target computer. NOTE: You will probably see the same errors as before, but in debug mode it should let you get to the command prompt.

Now at the FOS Linux command prompt key in the following.

ip a s
lspci -nn | grep -i net
grep -i firm /var/log/syslog

Snap a clear picture of the output and we will decide the next steps.

@brian-mainake said in ACPI Error during Image capture:

FOG Boot Settings > Kernel Log Level = 4.

That’s what happens when you use your memory of the settings and not the actual values. Yes the kernel log level. Set it to 7 and the kernel will be very verbose when it boots. The real error message should be displayed,

The other thing I didn’t see mentioned here was the version of the FOS Linux kernel you are using. WebUI->FOG Configuration->Kernel update. You should make sure you are running 5.15.x series. If you have FOG 1.5.9 your kernel may still be of the 4.19.x series if you have not updated it.

@brian-mainake As Sebasitan said those ACPI messages are typically nuisance messages and typically do not impact the quality of image deployment.

We can try to turn off acpi to see if that addresses the issue or not. In the host definition for this target computer, there is a kernel parameter field. Enter the following into that field acpi=off safe the definition and then…

I’m suspecting that the acpi messages are a distraction from the real error. Lets boost the logging level of FOS linux. In the FOG WebUI->FOG Settings->FOG Configuration Hit the expand all button. Search for Logging If I remember right the default logging level is 4. Change that to level 7 save the fog configuration.

Now schedule a deployment. You should see a bunch of text now on the pxe booting computer related to its booting. This may give us an idea of what is really happening.

Also make sure the firmware is updated on the target computer too.

Finally what is the manufacturer and model of the computer that’s doing this.?

@pauleb There is a lot of info in here to unpack so lets start with the easy stuff.

UEFI exit modes. There are only two. rEFInd and EXIT. All other modes are for BIOS computers.

So if you change the firmware to boot off the hard drive does it work correctly after imaging?

When deploying the Win 10 Image it gets written on the disk, and on installation it hangs with “Einen Moment bitte …” (A moment please …) and sometimes shows the “Why did my PC reboot” screen. I’m sorry that I probably miss the english titles of the screens, I just did the german installation.

I have seen bad drivers do this, OR leaving the fog client service enabled before you sysprep the computer. A bad driver install may cause the computer to spontaneous reboot before winsetup/oobe finishes. You will get that botched install message. OR if you leave the fog client service enabled, as soon as the fog service connects back to the fog server after imaging, it will start its tasks for renaming the computer, connecting to AD, or what ever else. You only want the FOG Client to do that after winsetup/oobe is finished. Typically you would disable the fog client service before sysprep and then reenable it in the setupcomplete. cmd batch file that is run at the end of winsetup and before the login screen is presented.

@Kureebow It sounds like you crated the fogproject directory using the tarball and not the git clone method?

@Flyer said in Dual boot (2 disks) unable to boot grub:

As a side note, is there a way to drop into a shell in the OS some time between when the image is written and reboot? I guess the postdownload script could just invoke a shell? Would be useful for debugging without have to re-image repeatedly.

When I’m debugging post install scripts I do this in debug mode. You actually will go through image deployment but is a bit faster.

Schedule a deploy task, but before you hit the schedule task button, tick the debug checkbox. Then schedule the task. pxe boot the target computer. This will drop your to a command prompt after a few screens of text that you need to clear with the enter key.

Sidebar for remote editing: now that you are at the fos linux command prompt. Get the IP address of the machine with ip a s command. Give root a password with passwd command. Make the password something simple like hello. Now you can connect to the target computer using putty or ssh from a comfortable location.

At the FOS Linux command prompt key in fog to start the imaging process. You will have to hit enter at every breakpoint in the deployment script. Hint: add a custom echo comment at the beginning of your post install script so you know when it starts. Use debugPause breakpoints in your script at important locations. If needed you can open up a new command shell either via the console or new ssh connection. If you get to a point where your script fails, hit ctrl-c to exit the deployment. Fix what you need then enter fog again to start the deployment over again. Hint: it helps if you have a small image for deployment testing to make the deployment part go quicker.

@Flyer You can do quite a lot with post install scripts to decode the hardware so if you need to make hardware specific changes in your script you can.

I have a few tutorials on this. In this example you can get the model number and system manufacturer of the computer the script is running on using dmidecode.
https://forums.fogproject.org/post/88293

Also here is a post install script for installing the proper windows drivers onto the target hardware: https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection The point of this script isn’t to show you how to inject drivers, but the method to extract data to make your post install script more flexible.

This post here is just random snippets of code that look at IP address and how to get fog run time variables into your post install script. https://forums.fogproject.org/post/69725

While I agree that having a post install script per host might be a good idea, I think it would only be a very edge case and be more of a management nightmare if you had a campus with 1000s of hosts.

@Flyer Yes that page might need to be updated to include references to snp.efi driver. If your hardware model is really new you have a better chance that snp will work well. If your hardware is older then ipxe.efi will work well. It takes the ipxe developers time to update iPXE to support the latest and greatest network drivers for the ipxe.efi boot loader. snp is built into the latest and greatest network boards from the factory.