Please search the forums. Numerous people have asked on how to boot ISO files from FOG PXE menu and there are heaps of answers and code snippets on how to do this.

In short: Yes it can be done and it is easier if you use the current (unstable) development version of FOG because PXE menu can be configured within the web interface. With FOG 1.2.0 you’ll have to edit a PHP file to do this…

[quote=“Reagan Kirby, post: 43227, member: 28838”]Thank you for your response. If I am running a PXE server already would this not be the same as just turning on each PC and selecting PXE boot?[/quote]

the difference is, usually usb boot is enabled as an option even when pxe boot is not, so you often don’t need to enter bios. the cctk also sets more than just the pxe for me, so it’s less keystrokes in the bios.

On my current Fog server, Ubuntu 12.04 and Fog 1.2.0, I updated the bzImage files and saw that there are downloads for the the init files as well. Are we supposed to update the init files? If so, how? If not, why is there an option to download them?

Thanks,
Reub

Uploading an image to FOG will not harm the computer being ‘captured’. All data will still be intact. Just make sure the image type is Re-sizable so that FOG can handle the change is storage size.

Hi dl550,
I can’t see how this is related to the other posts in the thread!? To be honest I don’t really understand what you are asking for! Probably a good idea to open up a complete new post and describe what exactly goes wrong. Are you trying to have french keyboard layout?

the option to resize partitions is done by simply choosing the “single disk - resizeable” Image Type. the rest is done automatically for you. i can’t remember if ext resizing is implemented in 1.2.0, but it is in the svn version that will become the next release.

I did a fresh installation of FOG 1.2.0 (without updating svn) and chainloading pxe is working now.
I think there may be some updates in the svn which stop chainloading pxe. o_O

Partclone has an logging option (–logfile) and you could write that log to the same place where your images are (NFS mounted to /images on the client)… Just an idea.

[quote=“Tom Elliott, post: 42523, member: 7271”]Right now I only know of one person who’s natively capable of imaging Mac’s with fog.[/quote]

Make it two on your list Tom! I’ve successfully tested imaging our mac minis with FOG and I am in the process of making it all working in our normal lab scenario.

So to answer the initial question: Yes it can be done and I love it for the exact same reason (mixed linux, win, macos environment!). HFS+ is not an issue (anymore). Network booting is a bit different to PC-BIOS style but can be done en mass! WOL is even more tricky. 🙂

Please let me know if you run into trouble and I’ll point you the way.

If he was reffering to the windows storage node, he is partly correct. While FOG is not installed on the windows server, the windows server can be used as a storage node. You will need to set up a few things for nfs and ftp to communicate correctly but using windows as a storage node is possible. BUT FOG on windows is not possible at this time.

Found it !
[url]http://fogproject.org/forum/threads/image-size-on-server-always-2gb-dashboard.11289/#post-34635[/url]

Thank you

Ok, thank you for your replies, I will try thursday and will return the result 🙂

^^Tom got’s it lol yeah yea I know this is an old post but I’m running CentOS 6.6 and all is good in the hood?! 😉

i have a suggestion that will make it so that you don’t need an isolated network for testing. what i do is redirect the boot.php requests for my test clients to my test server in the default.ipxe of my production fog server file, like so:
[CODE]#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

:bootme

redirected to dev server for test environments

##test-3020 optiplex 3020
iseq ${serial} F8HLK02 && chain http://<dev-server-ip-address>/fog/service/ipxe/boot.php##params ||
##testing VM
iseq ${net0/mac} 00:0c:29:ce:74:46 && chain http://<dev-server-ip-address>/fog/service/ipxe/boot.php##params ||

normal fog server

chain http://<normal-server-ip-address>/fog/service/ipxe/boot.php##params
[/CODE]

[URL=‘http://fogproject.org/wiki/index.php?search=snapins&title=Special%3ASearch’]http://fogproject.org/wiki/index.php?search=snapins&title=Special:Search[/URL]

A little wiki searching goes a long way.

[url]http://fogproject.org/wiki/index.php/Make_Snapins_Using_FOSS[/url]

Not a good day to be building a new server… ack

I also noticed the new site. It’s very nice and I’m glad the development continues. Keep up the good work

[quote=“Junkhacker, post: 41710, member: 21583”][url]http://fogproject.org/wiki/index.php/Modifying_the_Init_Image#Version_1.0.0_and_up[/url][/quote]

Thanks for the information, I’ve had a poke around and couldn’t locate the [I][SIZE=12px]fog.reg.man [/SIZE][/I]script. Are you able to point me in the right direction?

Thanks!

Edit

Found it!

[url]http://<ip[/url] of server>/fog/management/index.php?node=about&sub=mac-list

is there a approve all macs?

FYI: Wireless macs show up for hosts if the client is installed. Also to install snapins client must be installed.
FYI2: New Client will be more useful for snapins and other exciting options.

YES the trick was [SIZE=5][B][FONT=Consolas]next-server <ip of PXE Server>[/FONT][/B][/SIZE]