Posts made by chief

I’ve tested and it still doesn’t copy the drivers when they are there?

I have been installing the FOGservice.msi before sysprep. This, I believe, doesn’t install the service until after reboot? Or the service isn’t there to disable.

It is probably a separate issue, as the original issue from this post is resolved with the exit type setting.

Found the exit type option in the settings and set to GRUB_FIRST_HDD. This worked, but now the PC isn’t joining the domain.

Server

• FOG Version: 1.4.3
• OS: Ubuntu 16.04

Client

• Service Version: 0.11.12
• OS: Windows 10 1703

Description

We’ve been creating a new Windows 10 image for the 1703 update. I have a strange issue when the test pc I have imaged boots to pxe and the fog menu. After the menu it boots to hard drive and does an error beep and won’t boot. Bypassing the pxe boot after image and booting straight to the hard drive works fine.

The bios is set to legacy boot as it has been previously for the 1607 Windows update, which worked fine. Otherwise, the image is just a standard install, boot to Audit Mode, then install Fog and a couple of other bits of software and sysprep.

Has anyone else come across this error?

@george1421 Actually. I have tested on another machine and it’s not copying the drivers across now if they are on the server. Is there any other way around it?

@george1421 Thanks. That seems to have solved it.

Server

• FOG Version: 1.4.3
• OS: Ubuntu 16.04

Client

• Service Version: 0.11.12
• OS: Windows 10

Description

I’m trying to set up a new Windows 10 image and inject drivers with the fog.drivers script I got from this forum. Any PC without drivers seems to fail to image if there isn’t a drivers folder on the fogserver. Is there a way to bypass the drivers copy and just image the machine, if the folder is missing on fog? The files I use are below.

fog.postdownload

#!/bin/bash
case $osid in
    [5-7]|9)
        clearScreen
        getHardDisk
        getPartitions $hd
        if [[ ! -d /ntfs ]]; then
            mkdir -p /ntfs >/dev/null 2>&1
            [[ ! $? -eq 0 ]] && echo " * Failed to Mount Device"
        fi
        for part in $parts; do
            umount /ntfs >/dev/null 2>&1
            ntfs-3g -o remove_hiberfile,rw $part /ntfs >/dev/null 2>&1
            [[ ! $? -eq 0 ]] && continue
        done
        . ${postdownpath}fog.drivers
        umount /fog /ntfs /images >/dev/null 2>&1
        ;;
esac

fog.drivers

#!/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)
        ;;
    *)
        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)
clientdriverpath="/ntfs/Windows/DRV"
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]"


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 :-)"

We’re using the creative update version. I’ve installed the smartinstaller.exe and that works as expected. It seems that anything that installs services, such as AVG, when doing the sysprep, fails.

It appears to fail when running the FOGService.msi. Works ok with the SmartInstaller.exe. Am running a test image now to see if all works as it should.

You would presume so, but it says you can’t install this software. Has anyone else had this issue?

I’ll have a look at the .cmd

Server

• FOG Version: 1.4.3
• OS: Windows 10

Client

• Service Version: 0.11.12
• OS: Windows 10

Description

We’re doing a new image for Windows 10 Enterprise. For this we are booting the source VM into Audit Mode to create. This doesn’t allow me to install any software. How do you install the Fog client so that on install it will boot, connect to AD etc?

@george1421 Putting a dumb switch in between fixes the issue.
We have Dell switches with portfast enabled and a bpdufilter. After a bit of googling, I think the bpdufilter should allow the dhcp through the switches.

@george1421 Thanks for help. Was off for a few days over the holiday period.

Yes, Windows 2012r2 DHCP server. The FOG server and PXE client are on same VLAN/Subnet.

Will test the network issues.

@george1421 I have moved the FOG server into the same VLAN and IP subnet. I have the DHCP set up as per the BIOS and UEFI co existence post. I am now getting PXE boot on windows, but it fails with a “No configuration methods succeeded”

The screenshot is from Virtualbox, but I’ve tested on phyical Dell laptops with same issue.

It is going between subnets. From server to PC subnets/VLAN.

I have changed the DHCP environment to bios and uefi. So this windows PC should boot to the bios undionly.kpxe

We only have one DHCP server. No dnsmasq

I think the issue is with something else. The cable is connected. DHCP for OS working fine.

On booting a windows pc I get “No configration methods succeeded”

The pcap file on the windows pc booting is here
https://drive.google.com/file/d/0B1xRaaq2F0-JNUhXb3N2UTZSRm8/view?usp=sharing

@Wayne-Workman the option 067 is set to ipxe.efi at the moment.

Will set up like the guide. Do I just need to add PXEClient:Arch:00002 etc or others for a MAC?

No. First time testing a mac. Fog server on version 1.3.0-RC-36.
It works for PCs. DHCP is controlled by a windows 2012r2 server.

OK. So holding N doesn’t boot to network, just to the OS. Option N I just get a flashing world icon. Are there any settings in FOG I am missing to get it to boot from the network?