@devsamit Alright. We can help you sort this out. First, I congratulate you on trying to setup FOG yourself, and I congratulate you again about seeking help here. That said, I would recommend you install (not upgrade) Ubuntu 16.04 on the laptop, and then install FOG 1.3.0 Release Candidate onto it. There are many reasons for this that I’d be glad to explain, but it’s quite a long list of reasons.

• So, install Ubuntu 16.04 (not upgrade).
• Then install FOG 1.3.0 RC via these instructions: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
• You can adjust your existing DHCP server to give DHCP option 066 and 067. 066 is the FOG Server’s IP address. 067 should be undionly.kkpxe There is documentation on this process here: https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG

These steps if done without delay might take an hour.

Try to turn off secure boot.

Would you be willing to upgrade to Trunk to see if this resolves your problem?
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

Bumping this thread for @Jbob

Try different exit types is the only thing I could suggest.

@RileyG said:

@Wayne-Workman Hard to tell. This lab was imaged last year from a single and then all set individually touched to update and change names etc. Did you catch the update? The machine is reporting BOOTMGR is missing. I may pull the drive and check it as a USB attached to see what is has on it.

@TheKoR uses FOG Trunk, and so do I at both my work and home. I think there would be a good chance that your issue would be resolved if you moved to FOG Trunk.

My reasoning for this is the extra 100MB partition you’re seeing. There was a bug in 1.2.0 that didn’t work well with manufacturer’s custom MBRs (specifically Lenovo and Dell). You’re affected by this issue, and it’s mostly resolved in the current FOG Trunk, so I think you’d have good odds with upgrading.

As before any update, save your DB and your hosts prior to this. FOG Configuration -> Configuration Save -> Export. Host Management -> Export -> Export.

Here is the article about upgrading to trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

@techpromise said:

@Trevelyan Awesome, Thanks!!

Just curious however, we have many images, is there an automated way to do this via some kind of SQL dump and import into the new server?

There is.

FOG Configuration -> Configuration Save -> Export/Import.

That’ll dump / load your ENTIRE database.

I export mine EVERY Friday, along with all my images too. AND I make snapshots of my FOG server every Friday, AND I do a complete windows server backup every Friday… AND I have live replication enabled on my virtual FOG server…

If I go down, it won’t be for long lol.

@Quantum I do apologize. I didn’t know what you were talking about and mistakenly thought you were referring to auto registration. @Jbob explained it to me and I think what you’ve suggested is a great idea. Again, I do apologize.

Also, Welcome to the FOG community.

@george1421 said in UEFI PXE Boot how to do it?:

If the wiki would have had that this mentioned this thread would not exist

It does, at the very top:

“The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting.”

You have to specify that the NIC is a USB adapter with a kernel parameter on the host’s general page. YOu must set the ‘has_usb_nic=1’ kernel parameter.

So, it should look like this:

But, I believe that Surface 3s are UEFI, so you will need to use an .efi boot file. All the boot files available are in the /tftpboot directory, I suggest trying ipxe.efi first.

Past these things, you will need to upgrade to trunk, I believe, for better Windows Tablet support. There’s been a lot of work done in this area in FOG Trunk. You will still need to use the .efi files and the kernel arguments with fog trunk, but you might have better odds with getting it working and getting all the partitions to recognize correctly. Here’s info on FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

Please report your findings - this is how you give back to the fog project - by reporting back with details.

You need to troubleshoot TFTP and FTP both, it sounds like.

Check these out. If you have questions, come back here and we will help.
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

There’s links in the TFTP one for DHCP, that needs looked at too, probably.

@george1421

I think killing any existing lftp instances is possible with scripting.

for instance,

kill -9 $(pidof lftp)

Or this way:

kill $(ps aux | grep 'lftp' | awk '{print $2}')

Shamelessly Googled and found here:
http://askubuntu.com/questions/239923/shell-script-to-9-kill-based-on-name
http://stackoverflow.com/questions/3510673/find-and-kill-a-process-in-one-line-using-bash-and-regex

@x23piracy said in [SOLVED] UEFI PXE Boot how to do it?:

Is there an overview about the efi files, what they support and so on?

Yes:
https://wiki.fogproject.org/wiki/index.php?title=Filename_Information

hash tagging this so I can find it later for addition to the wiki.
EDIT: Added

@need2 said:

Also ensure your 7020s are on the latest BIOS release. I have seen a number of PXE issues in Dell systems that are on early editions of their BIOS, especially in 3020, 7020, and 9020s.

The newer optiplexes (in my experience) auto update their bios. there’s a dell utility that, if installed, will keep it updated.

@Tom-Elliott Awesome.

@george1421 I briefly read over the params article over at the ipxe website, and did some playing around and was able to hack it together. The ##params variable is just expanded into get variables on the URL. The below worked for me.

http://10.0.0.3/fog/service/ipxe/boot.php?mac=aa:bb:cc:dd:ee:ff&arch=x86&username=wayne&password=MyAmazingPassword&qihost=1

Going to that URL on my FOG server gives me this, which looks good:

#!ipxe
set fog-ip 10.0.0.3
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
goto MENU
:MENU
menu
item Acerbase Acer-base
item CentOS7VM CentOS7-VM
item compaq_cq60_Ubuntu16 compaq_cq60_Ubuntu16
item Optiplex380CentOS7 Optiplex-380-CentOS7
item Windows10 Win10Machine
item Win2012R2 Win2012R2
item Win7 Win7
item return Return to menu
choose target && goto ${target}
:Acerbase
set imageID 9
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:CentOS7VM
set imageID 8
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:compaq_cq60_Ubuntu16
set imageID 10
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:Optiplex380CentOS7
set imageID 3
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:Windows10
set imageID 4
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:Win2012R2
set imageID 11
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:Win7
set imageID 1
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:return
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://10.0.0.3/fog/service/ipxe/boot.php##params
goto MENU

Added to the WkKi’s working hardware list here: https://wiki.fogproject.org/wiki/index.php/WorkingDevices

For the record - I do not want the legacy client dropped.

The new client has yet to work for me.

@george1421 I agree. Default should be “Replication - disabled/unchecked”

FOG Users - when they see that checkbox, they will immediately know what it does. So no worries of confusion.