Posts made by RobTitian16

RobTitian16

@Tom-Elliott Updated correctly now - not sure why it wasn’t working the other day. Thanks for the help once again!

RobTitian16

@Tom-Elliott Yep, it’s the same as the screenshot above again.

RobTitian16

Server

FOG Version: 1.3.0-RC-26
OS: Ubuntu 14.04
SVN Revision: 6021

Description

Hi all,

I’m wondering if anything has changed in the FOG updates recently that would cause FOG to not run the postdownload script? As some of you may recall, we created a script called fog.postclient which would copy across the FOG client MSI and the SetupComplete.cmd was set-up to run it after imaging was complete. I now find it’s not working anymore, and I’m unsure why. Below is a copy of the script I currently have:

. /usr/share/fog/lib/funcs.sh

case $osid in
    5|6|7|9)
        clear
        [[ ! -d /ntfs ]] && mkdir -p /ntfs
        getHardDisk
        if [[ -z $hd ]]; then
            handleError "Could not find hdd to use"
        fi
        getPartitions $hd
        for part in $parts; do
            umount /ntfs >/dev/null 2>&1
            fsTypeSetting "$part"
            case $fstype in
                ntfs)
                    dots "Testing partition $part"
                    ntfs-3g -o force,rw $part /ntfs
                    ntfsstatus="$?"
                    if [[ ! $ntfsstatus -eq 0 ]]; then
                        echo "Skipped"
                        continue
                    fi
                    if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
                        echo "Not found"
                        umount /ntf >/dev/null 2>&1
                        continue
                    fi
                    echo "Success"
                    break
                    ;;
                *)
                    echo " * Partition $part not NTFS filesystem"
                    ;;
            esac
        done
        if [[ ! $ntfsstatus -eq 0 ]]; then
            echo "Failed"
            debugPause
            handleError "Failed to mount $part ($0)\n    Args: $*"
                        # Give the reader a chance to see what the error was
            sleep 12;
            # Terminate the post install script
            exit 1;
        fi

        # This next section determines the IP of the host system, cuts the last two octects and sets the FOGIP variable to
        # the correct IP address of the FOG server depending on the location (as the subnets are designed by location - i.e.
        # 10.1 is for the UK, 10.2 is for the US, etc.)

        myip=$(ip route get 8.8.8.8 | awk 'NR==1 {print $NF}' | cut -d "." -f1-2)

        case "${myip}" in
                10.1)
                        sitecode="UK";
                        timezone="Greenwich Mean Time";
                        FOGIP="10.1.0.102";
                        sitelocal="en-GB";
                        uilang="en-US";
						;; 
				10.2)
                        sitecode="US";
                        timezone="Eastern Standard Time";
                        FOGIP="10.2.1.103";
                        sitelocal="en-US";
                        uilang="en-US";
                        ;;
                *)
                        # Default code for the unknowns - we set the FOGIP to the development server in the UK.
                        sitecode="CompanyName";
                        timezone="Greenwich Mean Time";
                        FOGIP="10.1.0.102";
                        sitelocal="en-GB";
                        uilang="en-GB";
                        ;;
        esac

        # Check if the direcotry /ntfs/Windows/Setup/Scripts exists, and if not then create it.
        if [ ! -d "ntfs/Windows/Setup/Scripts" ]
        then
                mkdir /ntfs/Windows/Setup/Scripts
        fi

        # Copy the FOGService.msi across to the target computer.
        [[ -f ${postdownpath}FOGService.msi ]] && cp ${postdownpath}FOGService.msi "/ntfs/Windows/Setup/Scripts/FOGService.msi"


        # Check if the file SetupComplete.cmd exists in the source folder and then copy it to the destination on
        # the C: drive.

        if [ -f "/images/drivers/Common/SetupComplete.cmd" ]; then
                cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
                        # append the msiexec command to the end of the setupComplete.cmd file
                        echo "msiexec.exe /i %windir%\Setup\Scripts\FOGService.msi  /quiet USETRAY=\"0\" WEBADDRESS=\"${FOGIP}\" " >> /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
                        # Re-enable the FOGService and then reboot the computer
                        echo "sc config FOGService start= auto
                        shutdown -t 0 -r" >> /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
                        # just in case we edited the setupcomplete.cmd file in unix lets filter it to make it DOS compatible
                        unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
        fi

                # now lets use the timezone variable and update the unattend.xml file. You may need to edit the variable to
                # point to where your unattend.xml file exists. Remember case IS important.
                unattendfile="/ntfs/Windows/Panther/unattend.xml";
                sed -i -e "s#<TimeZone>\([^<][^<]*\)</TimeZone>#<TimeZone>$timezone</TimeZone>#gi" $unattendfile

                # now lets deal with the internationalization stuff in the unattend.xml file
                sed -i -e "s#<InputLocale>\([^<][^<]*\)</InputLocale>#<InputLocale>$sitelocal</InputLocale>#gi" $unattendfile
                sed -i -e "s#<SystemLocale>\([^<][^<]*\)</SystemLocale>#<SystemLocale>$sitelocal</SystemLocale>#gi" $unattendfile
                sed -i -e "s#<UILanguage>\([^<][^<]*\)</UILanguage>#<UILanguage>$uilang</UILanguage>#gi" $unattendfile
                sed -i -e "s#<UserLocale>\([^<][^<]*\)</UserLocale>#<UserLocale>$sitelocal</UserLocale>#gi" $unattendfile
        ;;
    *)
        echo "Non-Windows Deployment"
        debugPause
        return
        ;;
esac

I can confirm this is called in the fog.postdownload script.
Also, I’ve noticed a few bugs:
When booting from the network and I select ‘boot from hard drive’ in the FOG menu, a message will come up saying chainloading has failed.
Also, when performing a full registration and setting the system to be imaged (when it asks if I want it to be imaged after registering with the FOG server), it only registers and doesn’t start imaging. I have to then select ‘Deploy Image’ from the FOG menu.

Any help with these issues would be greatly appreciated

RobTitian16

@Tom-Elliott Same problem again, I’m afraid. I just tried upgrading to trunk and it’s not displaying the schema Installer/Updater button.

RobTitian16

@Tom-Elliott Resolved - thanks a lot!

RobTitian16

@Tom-Elliott

var runInterval;
$(function() {
    runDBCheck();
    $('form').submit(function(e) {
        clearInterval(runInterval);
    });
});
function runDBCheck() {
    $.ajax({
        url: '../status/dbrunning.php',
        dataType: 'json',
        success: function(data) {
            if (data.running === false) {
                $('#dbNotRunning').show();
                $('#dbRunning').hide();
            } else {
                $('#dbNotRunning').hide();
                $('#dbRunning').show();
            }
        },
        complete: function() {
            setTimeout(runDBCheck, 1000 - ((new Date().getTime() - startTime) % 1000));
    });
}

It says line 23 is wrong - seems like there are one too many brackets, or not enough.

RobTitian16

@george1421 Here is the log result:

[Fri Dec 30 06:44:08.080615 2016] [mpm_prefork:notice] [pid 1451] AH00163: Apache/2.4.23 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
[Fri Dec 30 06:44:08.080647 2016] [core:notice] [pid 1451] AH00094: Command line: '/usr/sbin/apache2'
[Fri Dec 30 13:03:05.052894 2016] [core:warn] [pid 1451] AH00045: child process 51905 still did not exit, sending a SIGTERM
[Fri Dec 30 13:03:07.053599 2016] [core:warn] [pid 1451] AH00045: child process 51905 still did not exit, sending a SIGTERM
[Fri Dec 30 13:03:09.054656 2016] [core:warn] [pid 1451] AH00045: child process 51905 still did not exit, sending a SIGTERM
[Fri Dec 30 13:03:11.055334 2016] [core:error] [pid 1451] AH00046: child process 51905 still did not exit, sending a SIGKILL
[Fri Dec 30 13:03:12.055927 2016] [mpm_prefork:notice] [pid 1451] AH00169: caught SIGTERM, shutting down
[Fri Dec 30 13:03:38.963672 2016] [mpm_prefork:notice] [pid 62960] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
[Fri Dec 30 13:03:38.963740 2016] [core:notice] [pid 62960] AH00094: Command line: '/usr/sbin/apache2'
[Fri Dec 30 13:16:02.326855 2016] [mpm_prefork:notice] [pid 62960] AH00169: caught SIGTERM, shutting down
[Fri Dec 30 13:16:03.860704 2016] [mpm_prefork:notice] [pid 8504] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
[Fri Dec 30 13:16:03.860767 2016] [core:notice] [pid 8504] AH00094: Command line: '/usr/sbin/apache2'
[Fri Dec 30 13:29:21.914129 2016] [mpm_prefork:notice] [pid 1093] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
[Fri Dec 30 13:29:21.921437 2016] [core:notice] [pid 1093] AH00094: Command line: '/usr/sbin/apache2'
[Fri Dec 30 13:55:26.301303 2016] [mpm_prefork:notice] [pid 1093] AH00169: caught SIGTERM, shutting down
[Fri Dec 30 13:55:48.781576 2016] [mpm_prefork:notice] [pid 12171] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
[Fri Dec 30 13:55:48.781634 2016] [core:notice] [pid 12171] AH00094: Command line: '/usr/sbin/apache2'
[Fri Dec 30 13:56:47.437312 2016] [mpm_prefork:notice] [pid 12171] AH00169: caught SIGTERM, shutting down
[Fri Dec 30 13:57:35.348797 2016] [mpm_prefork:notice] [pid 24506] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
[Fri Dec 30 13:57:35.348861 2016] [core:notice] [pid 24506] AH00094: Command line: '/usr/sbin/apache2'

@Tom-Elliott Here’s what I see under the console tab, which looks like the cause of the issue:

RobTitian16

Server

FOG Version: 1.3.0 (Revision 15)
OS: Ubuntu 14.04 & 16.04

Client

Service Version:
OS:

Description

Hi all,

I’m currently trying to upgrade my FOG installation to the latest trunk version, but every time I try it, my fog/management page looks like the below, with no means of updating the schema. Has anyone run into this issue before?
I thought it might be a problem with Ubuntu 14.04, so I upgraded to 16.04 to no avail.

Any help with this would be greatly appreciated.

RobTitian16

@george1421 Still no dice with getting this to run with the legacy boot option.
I’ve cloned my FOG server for UEFI testing but the laptops don’t boot using IPV4 - they just hang. or say that the file is not found (going by the previous posts).

EDIT:
It seems to be working on a Dell E7270. I’ll test after the holidays with the other Dell laptop
Thanks for the help, George and everyone else! Much appreciated as always!

RobTitian16

@george1421 Thanks, George. I’ll give this a go with one of the other laptops to see if I can get it to work.

RobTitian16

@george1421

Sorry about the delay - it’s been hectic this past week. Here’s the latest pcap:

0_1481287363618_output.pcap

Interestingly, what @sudburr said earlier rings true as the very system I was trying to get Bitlocker to work on earlier died and had the motherboard replaced by Dell. Once the motherboard was replaced, Bitlocker could then be enabled without any issue.

RobTitian16

@george1421 Yep, I removed those this morning.
I had to revert back to a previous build of my FOG server as I needed to image a VM for our production environment. I’ll go through the dnsmasq set-up again and then provide a pcap when the issue occurs again (likely to be on Monday now).

RobTitian16

@RobTitian16 I’ve also found this has stopped my ability to image VMs on Hyper-V:

0_1480672488015_upload-f55fc67f-b107-457c-baa6-9dfba5bbe4e4

RobTitian16

@george1421 We seem one step further
It now boots from the network, but gets stuck on “iPXE initialising devices…”
I’ve tried the suggestions here: (https://forums.fogproject.org/topic/6133/intel-nuc-dc53427hye-stuck-at-ipxe-initialising-devices/6) to no avail. It’s a Dell Latitude 6430 and I can see here (https://wiki.fogproject.org/wiki/index.php/WorkingDevices) that it looks like it may not work anyway.

RobTitian16

@Wayne-Workman I’m not trying to capture an image from a system that’s using BitLocker - I’m trying to enable it after the system has been imaged. From the forum post linked in my other reply, it says it needs to be imaged in UEFI mode (effectively) to enable BitLocker to run correctly.

RobTitian16

@sudburr I read online that UEFI has to be enabled to run BitLocker. (Source: http://www.dell-forum.com/windows/bitlocker-cannot-be-enabled-when-changing-the-boot-sequence-to-legacy-mode/).
It does exactly what it says in that forum post - asks for a key every time the system is booted, which can be incredibly cumbersome when you have to dig out the key from a file share (using another system). I suppose we could supply everyone with USB keys, but that might not be a very good idea from a security standpoint if the USB keys are with the users all the time.

When enabling BitLocker, I enable the check and it returns after restarting saying that it could not activate BitLocker because it could not connect to the TPM chip.

RobTitian16

@george1421 0_1480609373367_output.pcap

It’s right at the end - 10.1.2.32 is the target host.
10.1.0.102 is the FOG Server.

RobTitian16

@george1421 Thanks, George.
From what I can see, the system I’m trying to boot with is requesting the ipxe.0 from the FOG server, but that’s where the log ends.

RobTitian16

@george1421 Okay, I’m now using exactly the same file as your tutorial:

port=0

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

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

# 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,,10.1.0.102
dhcp-boot=net:UEFI,ipxe.efi,,10.1.0.102
dhcp-boot=net:UEFI64,ipxe.efi,,10.1.0.102

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,10.1.0.102

# 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

dhcp-range=10.1.0.102,proxy

However, when booting from a UEFI boot on a Dell Latitude E6430, the system is still saying the same thing.

Start PXE over IPv4
Station IP address is 10.1.x.x
Server IP address is 10.1.x.x
NBP filename is ipxe.0
NBP filesize is 0 Bytes
PXE-E23: Client received TFTP error from server.

RobTitian16

@Wayne-Workman I can confirm this is now working - I just had to re-image the system and sysprep it again. It’s now uploading fine.
Thanks for the help and suggestions