Do backup. Please. Just always do backups before you do such things.

[quote=“DanielJay, post: 24805, member: 23088”]I decided to try downloading the image to one machine using unicast and that has failed. I am getting:
“Storage Node ‘DefaultMember’ is open, but has recently failed for this HOST
Unable to find a suitable Storage Node for transfer!”

I have since opened my /opt/fog/.fogsettings file and copied the value of password into the password field of my default storage node. I have also copied that same password into the TFTP settings on the config page.
After all of that was ran I restarted my NFS and TFTP servers. I am able to open up FileZilla and FTP to the FOG server using the fog user and that same password.

Any suggestions on this issue?[/quote]

Jaymes,
Any idea what might be causing this above issue?

Great thanks! I have ended up doing so but wanted to find out if there was a “best way” of doing this.

When you installed FOG did you install the language stuff with it?

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.