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

@carrjd Have you considered the project I made that makes FOG completely mobile? It’s designed specifically for your use case - you’ll be able to do more than one at a time.
https://github.com/wayneworkman/FOGUpdateIP

@kwetiaw Well, dnsmasq in proxy mode might be a different story. I have to admit that I read your initial post about using dnsmasq because you are not allowed to touch the real DHCP servers but somehow wasn’t aware of that fact when posting my answer.

From the dnsmasq man page:

For directly connected networks (ie, networks on which the machine running dnsmasq has an interface) the netmask is optional: dnsmasq will determine it from the interface configuration. For networks which receive DHCP service via a relay agent, dnsmasq cannot determine the netmask itself, so it should be specified, otherwise dnsmasq will have to guess, based on the class (A, B or C) of the network address.

So we are back to my question on how is you server (running dnsmasq) connected to those two networks?

Maybe this could work (if you have two different NICs for those two networks - please post the full output of ip a s on that server):

dhcp-range=eth0,10.3.0.1,proxy dhcp-range=eth1,10.40.0.1,proxy

@Avaryan Thanks matey.

I shouldve mentioned my environment on my post. Windows 10 Enterprise and I just tested with the powershell script you mentioned.

WORKED FLAWLESSLY!!!

Thanks and really really appreciated!

All set - it was the files being sent to a single filename * - that was just a syntax error on my part for using the Windows cli too often.

@Wayne-Workman - i had to change my /opt/fog/.fogsettings file back to pointing the storage at ‘/images’ because the entire imaging process breaks. Also re-added my /etc/fstab line to point /images to the home directory where the 177G volume is. I understand you think my system will fail if I fill up more than the 50G available on the root drive, I’m confident it won’t. Thank you greatly for your assistance, it was the file copy problem.

@dureal99d Really nice, thank you!!