OK, I’ll update, then report back. Thank you.

This feels much better!

Upgraded Fog to 1.4.4, and captured the image, deployed it, and was presented with my AD Login screen! It logged me in, then restarted… Then let me log in properly.

A couple things I need to change on the image, but over all, this is much better than where I was before! Thank you for the advice

This worked! Thanks!

I’m disappointed Microsoft’s method doesn’t work anymore, it was super helpful when we were testing Windows 10 at my previous site…

Sorry for the late reply… Tried on another computer, and I cannot get the FOG menu to appear (this computer has never registered on that FOG server).

@george1421 Yes I have. I found that document the first time I ran into the Netboot issue (posted above). I followed it, and the web interface loads (so I thought it was fine). It also let the computers that were stuck in a PXE boot-loop start up and boot into Windows. The current issue is that I can’t image this laptop, or even see the menu. Tomorrow when I’m back on site, I’ll test with another computer as well.

Possibly related to my old problem, but this is on a separate server.

Running Debian Jessie, I updated the IP address, and systems will boot into Windows if they boot from the NIC. That part is good.

I have a Dell laptop that will not load the menu. When I attempt to boot from the NIC, in BIOS mode (no UEFI), it presents me with a GRUB prompt after downloading the iPXE items (not sure what to call it). It will not launch FOG.

I log into the web interface, find this PC in the list, and start a Deploy (Debug) task, and it will boot me into the Fog OS. It looks good to me, so I type fog and press Enter, then it complains it can’t find the fog.postinit file.

It was running 1.3.0. I updated to the latest stable release from GIT, updated the MySQL tables in the web interface, and tried again - no change. I cannot load the FOG menu to select anything. I ran the tftp tests from another computer on the same switch, but no change.

Thoughts?

@Sebastian-Roth I added the new lines to my /etc/apache2/sites-enabled/001-fog file, entered my credentials and waited 10 minutes… No change, still getting an HTTP/503 response.

I downloaded the script to the FOG server, ran ./updateIP.sh, and got the following results:

Updating the IP Settings server-wide.
A password was not set in /opt/fog/.fogsettings for mysql use.
Updating the IP in /tftpboot/default.ipxe
Backing up /var/www/html//fog/lib/fog/config.class.php
Updating the IP inside /var/www/html//fog/lib/fog/config.class.php
Updating the fields inside of /opt/fog/.fogsettings

All done.

I tried to log in again, and it’s still spinning around (although, it’s only been 2 minutes since I ran the script and tried to log in).

EDIT: It’s working now! After running the script, I also restarted Apache, PHP and MySQL, then tried again:

systemctl restart php7.0-fpm.service apache2.service mysql.service

@Sebastian-Roth Output below:

# ss -antul | grep 9000
tcp    LISTEN     0      128    127.0.0.1:9000                  *:*

# cat /etc/apache2/sites-available/001-fog.conf
<VirtualHost *:80>
    <FilesMatch "\.php$">
        SetHandler "proxy:fcgi://127.0.0.1:9000/"
    </FilesMatch>
    KeepAlive Off
    ServerName 10.32.10.2
    DocumentRoot /var/www/html/
    <Directory /var/www/html/fog/>
        DirectoryIndex index.php index.html index.htm
    </Directory>
    RewriteEngine On
    RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
    RewriteRule .* - [F]
    RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
    RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-d
    RewriteRule ^/fog/(.*)$ /fog/api/index.php [QSA,L]
</VirtualHost>

And the config.class.php file looks normal to me.

My network address space changed from 192.168.0.0/23 to 10.32.10.0/23. I did nothing in the FOG config, but noticed PCs that were set to boot from the network first failed.

While searching for fixing it, I came across this page about changing the FOG server IP address. It was 1.5.5 before, so I expected the 1.3.0 instructions to work. I updated the ipaddress= parameter, and ran the installation. It completes successfully, and tells me to log in to the Management Interface in my web browser.

I type in my FOG username and password, and it hangs. I eventually get it to time out with a 503 error. When I check the Apache Error Log (/var/log/apache2/error.log), I see the following line:

[proxy_fcgi:error] [pid 597] (70007)The timeout specified has expired: [client 10.32.10.115:50251] AH01075: Error dispatching request to : (polling), referer: http://10.32.10.2/fog/management/

I have tried rebooting the server (Debian 9.8), but no change. I have checked the following as well:

• No firewall is running (iptables -L shows everything is Accept)
• Lots of free space on all partitions
• 250 MB of used memory, with 2.5 GB free
• No selinux installed or activated
• apt is updated, and all packages available are installed
• Checked /var/log/php7.0-fpm.log - the same four lines keep repeated:

    [25-Mar-2019 09:20:42] NOTICE: fpm is running, pid 6223
    [25-Mar-2019 09:20:42] NOTICE: ready to handle connections
    [25-Mar-2019 09:20:42] NOTICE: systemd monitor interval set to 10000ms
    [25-Mar-2019 09:25:27] NOTICE: Terminating ...
    [25-Mar-2019 09:25:27] NOTICE: exiting, bye-bye!
  

• Restarted apache2.service, mysql, and php7.0-fpm, no change.
• nginx is not installed, and has never been installed on this server.
• Attempted to run the latest stable installfog.sh script from Git Hub - no change

Where can I look next?

This worked! Thanks!

I’m disappointed Microsoft’s method doesn’t work anymore, it was super helpful when we were testing Windows 10 at my previous site…

@george1421 OK, I’m re-capturing my image, and then I’ll deploy it. I added the commands for PNPUTIL before turning on the Fog Service, as I know it took quite a while to run after I logged in. I’ll report back once I know whether or not this works.

I created an image based on the LTSB 1607 Windows 10. I can deploy it fine to the first of a fleet of new machines - Dell Latitude 5590’s.

I have the fog.drivers script running after imaging, and the C:\Drivers folder is populated, so I know FOG is copying the drivers.

However, Windows is not looking in that folder during the first boot up, and installing the drivers it needs.

unattend.xml (the part that mentions the Driver path):

...
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:action="add" wcm:keyValue="1">
                    <Path>C:\Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
...

The tree of files created (trimmed):

C:\
  Drivers\
    x64\
      audio\
      chipset\
...
      storage\
      video\

fog.drivers Script:

#!/bin/bash
ceol=`tput el`;
manu=`dmidecode -s system-manufacturer`;
case $manu in
    [Ll][Ee][Nn][Oo][Vv][Oo])
        machine=$(dmidecode -s system-version)
        ;;
    *[Dd][Ee][Ll][Ll]*)
        machine=$(dmidecode -s system-product-name) #pruduct is typo, just realized sorry :(
        ;;
    *)
        machine=$(dmidecode -s system-product-name) # Technically, we can remove the dell one as it's the "default"
        ;;
esac
[[ -z $machine ]] && return #assuming you want it to break if it is not lenovo or dell?
machine="${machine%"${machine##*[![:space:]]}"}" #Removes Trailing Spaces

#############################################
# Quick hack to find out if the installed OS image is a x86 or x64
system64="/ntfs/Windows/SysWOW64/regedit.exe" # sloppy detect if 64bit or not
[[ ! -f $system64 ]] && arch="x86" || arch="x64"

#############################################
#this section has been updated to bring the osn names in line
# with how the Dell CABs are defined
case $osid in
    5) osn="win7" ;;
    6) osn="win8" ;;
    7) osn="win8.1" ;;
    9) osn="win10" ;;
esac

#############################################
dots "Preparing Drivers"
# below creates local folder on imaged pc
# this can be anywhere you want just remember
# to make sure it matches throughout! (case IS important here)
if [ $osid -eq 9 ]
then
    clientdriverpath="/ntfs/Drivers"
else
    clientdriverpath="/ntfs/Windows/inf/Drivers"
fi
remotedriverpath="/images/drivers/$machine/$osn/$arch"

[[ ! -d $clientdriverpath ]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1
echo -n "In Progress"

#there's 3 ways you could handle this,
#driver cab file, extracted driver files or both
#so on the server put extracted driver files to match below folder tree
#i.e. Model Latitude E5410, Windows 7 x86 image would be:
#/fog/Drivers/Latitude E5410/win7/x86

rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1
[[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]"

#this next bit adds driver location on pc to devicepath in registry (so sysprep uses it to reference)
# remember to make devicepath= match the path you've used locally
#also do not remove %SystemRoot%\inf
#and to add more locations just use ; in between each location

regfile="/ntfs/Windows/System32/config/SOFTWARE"
key="\Microsoft\Windows\CurrentVersion\DevicePath"
devpath="%SystemRoot%\DRV;%SystemRoot%\inf;";
reged -e "$regfile" &>/dev/null <<EOFREG
ed $key
$devpath
q
y
EOFREG
echo -e "\b\b\b\b\b\b\b\b\b\b\b${ceol}Done"; # this just removes "In Progress and replaces it with done :-)"

What can I do to get my new images to detect the drivers, and automatically install them correctly?

@paulman9 Can you post the link of how you built that from source?