Thanks jbsclm

Hi, There was an issue that we not in the app, this has now been updated. Should be rolled out in the next 48 hours.

What do you mean by, the snapins are host related by design? I don’t mind that I have to select them, but could you add a selection option in the Full Host Registration menu, through iPXE? I just want to be able to take a new machine out of the box, plug it in, boot to the FOG menu, go through Full Host Registration, add hostname, image ID, domain add option, and snapin option, then let it go on it’s merry way.

Right now, the only way I can achieve zero touch, is to manually create the host through the web interface. It would be nice to be able to select all the same settings though iPXE.

And in FOG we use Partclone and Partimage. The problem is we are using previously created services to complete the required task here. FOG is open source, it uses all open source pieces to complete the puzzle. These are free.

Ghost is a privately created and operated, it uses it’s own services specifically designed for Ghost, not a piece designed for something else but achieves the same goal. That is why ghost costs. They also have a development team… I know your heart is in the right place, but as long as you keep comparing FOG to another imaging solution that is maintained by a full team of devs, FOG is always going to seem to be lacking.

My corporation uses FOG because it is free and it is versatile.

Personally I tend to enjoy the fact of being able to over come my obstacles with my own knowledge of linux. I realize that not everyone has this experience, but if you continue to compare apples and oranges eventually your fruit will rot if you don’t eat it 🙂

THANK YOU GILOU!!!

This is excellent because you can customize and change the look of fog without actually changing the base code of FOG and “shouldn’t” break when updating FOG or at least be easy to re-implement your changes rather than hard coding them back in.

The registry hack works fine for 7, as far as I know. But it won’t help for sid/AD integration obviously 😉

[url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Full_Listing_of_Ports_used_by_FOG_server_and_client[/url]

[quote=“timcough, post: 11851, member: 40”]I have suggested the following in a different thread to allow a single snapin to be sent to multiple computers:

Add the following lines to the groups section of tasks.advanced.include.php:

[PHP]<tr>
<td class=“c”><a href=“?node=tasks&type=group&direction=onesnap&noconfirm=<?php print $groupid; ?>”><img src=“./images/snap.png” /><p><?php print _(‘Deploy Single Snapin’); ?></p></a></td>
<td><p><?php print _(‘This option allows you to send one of the snapins to the group without imaging the computers. (Requires FOG Service to be installed on client)’); ?></p></td>
</tr>[/PHP][/quote]

Thank you SO MUCH for this code. It has made snap-in deployment much easier. Has anyone figured out a way to make snap-in groups? It would be terrific to be able to put a number of snapins into a group for deployment to certain machines. ie. all 32 bit machines get a certain group of snapins, while 64 bit get a different group, etc.

Yeah, this is where the host CSV import comes in handy to migrate hosts. you could even export the inventory SQL table and import that into 0.33 aswell

[quote=“Tom Elliott, post: 22181, member: 7271”]need2,

If you want help, let me know.[/quote]

I may take you up on that in the near future. Involving FOG in my department’s three year plan, and I need to have full UEFI support. Long story short I would love to start experimenting with the 0.33 branch and UEFI. I’ve got other projects I need to finish first though.

I would really like to implement this solution as well, any chance of getting a complete tut?

That will get messy when I have more than 16 stations, but that sounds like it is what I need, thanks!

As I stated, I have gotten this working finally.

I figured it out and it took a lot of work. Hopefully it’s something that’s needed. Next phase to hopefully get multicast working.

well… if the user wanted to use bittorrent sync an easy way to avoid hassle would be to have a way of just turning off the current replication system. As long as the permissions will be correct in the folder then the images should just sync across.

The user would have to generate their own key and tell bittorrent sync where to sync the images.

I suppose the biggest advantage would be many to many replication. I would have to check if bittorrent sync can take parts of files from different hosts but at a minimum if you had 10 images and were putting in your 11th host… you could get away with transferring one image from each of the others. which could save you a ton of time if your doing things over a WAN.

Is there currently a way to easily disable replication and i’ll throw a couple of VMs on 0.33b and see if I can make it do something.

Does your wake button work for groups as well as hosts 🙂

Being able to boot up an entire lab for imaging all at once would save you even more time.

in the archive U can find:
MulticastTask.calss.php
the /bin/fog (present in mi Image.gz)

[url=“/_imported_xf_attachments/0/412_Archive.zip?:”]Archive.zip[/url]