For the record, Dell normally has Linux based firmware update packages. You could update firmware with fog using postdownloadscripts.

@george1421worked perfectly. thanks!

UEFI is just a hell lot more complex than legacy BIOS is. This does not make it slower per se but on top of that a lot of the UEFI implementations are badly flawed. Feel free to take a tour through the iPXE code and see all the things that need to be done to properly boot UEFI machines…

So simple. Thanks!

@Joe-Schmitt, that was what I imagined the case to be, thank you for the clarification.

-Anthony

Note 2:

The only reason why I had a swap partition I believe was because initially I added a new drive to my VM and initially moved all my images over to that drive… I ended up transferring my images back to the original drive and removing the second drive all together. Despite removing the drive the Swap remained.

Here’s instructions on that. https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

@iyoung Yes. Make a new thread, put it in tutorials.

There are no scheduled release dates. FOG is entirely worked in free time of the developers, so it would be impossible to schedule any target dates, realistically.

That being said 1.3 is on RC11 right now, so you can perhaps draw some conclusions from that.

Soon TM

@Wayne-Workman absolutely weird.
I used the same technique with snap in pack on different folder and it worked without issue in the past. Only this time around with system32 folder.

I even tried with xcopy!

Anyway, thanks for your help, appreciate it and I will check further to see if AV is a culprit here.

Cheers

@george1421 I prefer /etc/sysconfig/network-scripts/ifcfg-xxx now after I learned more. Before that yes I clung to the cli graphical tool for dear life.

@wcheung said in Host Machine and images:

What i find interesting is that Lenovo X1 Carbons (Gen 1 - 4) do not have ethernet ports, it used a proprietary connector OR a USB3.0 ethernet adapter that have a MAC id on them.

Fog can work with these devices fine. They have Wifi MAC addresses that would be used for management through FOG after imaging is over. If you have many of these devices there will be a little more effort for re-imaging if you’re environment is not mega-automated. If your environment is not mega-automated then the workload is not higher.

@Tom-Elliott 46MB

@sourcaffeine At the bottom of this document: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client search for sysprep.

@jflanagin again, that article I posted below would help you setup what George just explained.

@cschneider.tech For the record, the instructions in the wiki do work, many people have used them before.

@Wayne-Workman Here is an updated working centos boot code that works for using your own downloaded repo as well as the online repo.

I downloaded my own repo using command <wget -r -l 0 ./LOCAL-DIR WEBSITE-URL> in Ubuntu.
once downloaded
I then copied the repo from my home directory to the /bootimgs folder.
I then modified the boot code originally provided by @george1421 from:
:centos
initrd http://${fog-ip}/bootimgs/centos/images/pxeboot/initrd.img
chain http://${fog-ip}/bootimgs/centos/images/pxeboot/vmlinuz initrd=initrd.img method=http://${fog-ip}/bootimgs/centos/ devfs=nomount ip=dhcp
boot || goto MENU

to

initrd http://${fog-ip}/bootimgs/centos/images/pxeboot/initrd.img
chain http://${fog-ip}/bootimgs/centos/images/pxeboot/vmlinuz initrd=initrd.img root=live:http://${fog-ip}/bootimgs/centos/LiveOS/squashfs.img ip=dhcp repo=http://192.168.1.109/bootimgs/centosrepo/mirror.nodeshosting.com/centos/7.2.1511/os/x86_64 splash quiet – || read void
boot || goto MENU

the end result is that now I have my own home repo that works even if my machine is not connected to the internet. I assume this is good for corporate or environments where the admin is not wanting to use much data from or restrict the net.

it also makes short work of the install time.

I hope this makes someone’s life a bit more easier

0_1473836274949_cent os boot complete.png

thanks for all the reply. I will give it try and see how I go with it.

Thanks!

Now stated working properly…Not sure where was the problem

I did once again trunk update…reconfigured