@george1421 Yep, they’re definitely on the same subnet.

This is my full config:

# Sample configuration for dnsmasq  to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCPserver is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

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

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

# Dnsmasq can also function as a TFTP server. You may uninstall tftpd-hpa if you like and uncomment the next line.
#enable-tftp

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

#The boot filename.
dhcp-boot=undionly.kpxe,,10.1.0.102

# rootpath option, for NFS
dhcp-option=17,/images

# kill multicast

dhcp-option=vendor:PXEclient,6,2b

# 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



# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# A boot service type of 0 is special, and will abort the net boot procedure and continue booting from the local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the 
# PXE client will search for a suitable boot service for that type on the 
# network. This search may be done by multicast or broadcast, or direct to a server if its IP address is provided.
# pxe-service=x86PC, "boot from Windows RIS server", 1

#This range(s) is for the public interface, where dnsmasq functions as a proxy DHCP server providing boot information but no IP leases.
# Any IP in the subnet will do, so you may just put your server NIC IP here. Since dnsmasq is not providing true DHCP services, you do not
# want it handing out IP addresses. Just put your servers' IP address for the interface that is connected to the nwtwork on which the FOG 
# client exists. If this setting is incorrect, the dnsmasq may not start, rednering your proxyDHCP ineffective.
dhcp-range=10.1.0.102,proxy

# This range(s) is for the private network on 2-NIC servers, where dnsmasq functions as a normal DHCP server, providing IP leases.
#dhcp-range=192.168.0.20,192.168.0.250,8h

#For static client IPs, and only for the private subnets, you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite 

And I think I’ve just realised what could be wrong… the “#The boot filename” section probably needs to be taken out, right? That’s from the previous installation of dnsmasq.

@george1421 Yep, I had dnsmasq installed. Then, I installed the 2.76 version. Then I configured the config file as you did in your post:

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

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

# 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=192.168.112.24,proxy

Am I missing a step somewhere?

@george1421 Is that an l (as in lower-case L) or a 1? I may have typed it incorrectly, which is why I got that error.

So far so good, although I’m running into an issue when starting PXE over IPv4 in UEFI:

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. 

I’m guessing it’s because the ipxe.0 file doesn’t actually exist. Where would I get this from?

@george1421 Ah, thanks. I got as far as “Make Install” but then ran into the following problem:

I’m running this on Ubuntu 14.04.

EDIT: I spoke too soon (as usual, doh!)
I just had to install the libidn package.

sudo apt-get install libidn11-dev

@Wayne-Workman I’ll try re-imaging it again and then upload it after I’ve made the changes.
When I tried to load it into Windows after sysprep, it was stuck on a black screen with the mouse cursor. It clearly shows something wasn’t right with the system and FOG must have picked up on it.

@Tom-Elliott Yep, here is the output as requested:

@george1421 Yep, we use Dell too and it’s just something I learnt today (learn something new…).

I was going by the wiki article I mentioned before as it seems like the UEFI network boot won’t load as it’s not given a file to boot from. In fact, it just sort of flashes and then disappears when I try to boot it that way. I’ll see what I can do with dnsmasq. Thanks!

@Tom-Elliott
Ah, thanks. That’s what I was looking for to boot it from the network.

As I said before though, I’m running Windows Server 2008 R2 so I’m guessing it’s not possible for me to boot from UEFI? Not unless I upgrade to Server 2012 R2.

@Tom-Elliott When booting into UEFI, the system says there are no devices to boot from. In order to get the network boot option, I have to disable secure boot, enable Legacy Boot and then either set the network boot as the priority in the boot order, or press F12 at the beginning of the boot cycle to get the option to boot from the network. So I suppose my first question is, how would I get the system to boot from the network in UEFI mode?

And if I created the image in a legacy boot mode, could I push it to a UEFI system without any issues?

Finally, I’m following the wiki article (https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence) on this, (EDIT) and I’m using Windows 2008 R2 for DHCP. I can see it says no-one has got it working yet, so I’m assuming it’s not possible for me at the moment either?

Server

• FOG Version: 1.3.0-RC-26
• OS: Ubuntu 14.04

Client

• Service Version:
• OS: Windows 10 Pro

Description

Hi all,

When imaging a system, I have to boot it into Legacy Mode in order to get the option to boot from the network. However, when I do this and image the system, I’ve now realised I can’t enable Bitlocker - the OS has to be installed when UEFI is enabled. Has anyone had this issue before? Is there a workaround or solution I’m unaware of?
Would rebuilding the image with UEFI mode enabled help at all?

@Quazz Yep, it’s now svn version 6021, sorry. I updated it on Monday evening.

@Tom-Elliott Sorry, meant to put: 1.3.0-RC-26
This is still happening even after updating FOG.

Server

• FOG Version: 6016
• OS: Ubuntu 14.04

Client

• Service
• OS: Windows 10

Description

Hi all,

I’m trying to upload an image to the FOG Server but I keep running into this problem which I haven’t seen before:

I’ve been able to upload images before from this VHD so I’m not sure why it won’t upload it now.
Any help would be appreciated as always

@george1421 Thanks George - I thought that would be the case. I’ll see if I can cook something up in the post installation script and test it out later when I have some more time

Hi all,

I was wondering if it’s possible to join a computer to a domain and put it in a specific OU depending on the location?
So, for example, when I image a system and I perform a full host regsitry & inventory and I set it to a location (say UK), is it then possible to link that to an OU? - i.e. Domain - CompanyName - Location (UK in this instance) - Computers.
Or is it simply a case of having to go into the web gui and remembering to set the OU before it joins the domain?

@george1421 +1 for a wiki page. This is really useful stuff and I only found out about it when coming onto the forums and talking with George. Without the forums, I wouldn’t have ever found this out/get it working.

@Quazz Simply because it removes some settings we like to keep, otherwise users can spend ages getting everything up and running again.

Anyway, thanks to everyone who pitched in with this It really is appreciated!
The original issue was answered some time ago and this thread has evolved with the problems associated with it. As such it can be marked as answered.

@george1421 I didn’t think the unattend.xml file would, considering you say in the tutorial:

“Note: the unattend.xml file is only used if the reference image was sysprep’d before image capture.”
Unless you’re basically saying to sysprep it. In which case… I guess I’ll have to as I can see the benefits of doing so now with this script, etc.
Thanks for the help and support as always! It’s been a challenging one, but hopefully one that will be immensely beneficial

@Tom-Elliott Ahh okay. Is there a way to run this without the image being sys-prepped?

@george1421 Indeed, this is something I’ve just found out - the SetupComplete.cmd is there with the FOGService.msi, but the .cmd is never actually executed. The target OS’s are always Windows 7/8/10/Server 2008/2012 R2/2016.
I’m currently testing this with a Windows 7 x64 OS.
I can’t see where the post install script is actually telling the SetupComplete.cmd to run, though. I can see it copies, but nothing tells it to run.