@Wayne-Workman Well yeah, I don’t want to hold up 1.3, hence the plugin/module idea.

Then let’s get rid of the FogCrypt download link also.

Moved to Feature Requests.

When people like @george1421 say things like “oh that’s easy, just carefully do this then this then this then this…” Chances are they can get it done within a few hours.

I myself don’t see how it’s easily possible because not all ISOs work exactly the same. The kernels are in different directories, inits might be in different directories. Some might just flat out not work with NFS like WinPE or similar. I got a DBAN ISO to work across HTTP for instance… While the NFS method might be easy to automate for the mounting and menu entry aspects - All the ohter aspects will prove to be very difficult to script… just because there are so many differences across different ISOs.

That and… it’s not the intention of FOG to deliver ISOs on a boot menu. The intention of FOG is to create a seamless imaging environment and to reduce the workload associated with that imaging. Anything extra is a big bonus.

The @Developers have already provided a highly advanced boot menu editing system. That’s their way of saying “Here, use this for all that other stuff you want to do.”

@TheOverseer Sorry, took me a while to get things sorted. Here you can find the current version on github now (still alpha): https://github.com/FOGProject/node-dhcproxy

Should run on linux and windows after installing node.js. Extract the archive and take a look at README file for some more details. Run as root on linux (needed to listen on port 67).

Would be great if you can give some feedback on how this is working for you.

@george1421 Room number (or room name) is most of time in group. That was my point. If you ask group before name (I know it’s stupid), you will be able to find out name I need using concatenation of the group name and a split on other computer in group taking the max of “name” less “group”.

New Host Name = Group Name + (max (Group Name removed from the list of other computer in group))

I don’t know if you understand me… lol
Something like this if name is “create” during registration.
Other way is just rename every host in group during registration base on registration date. Oldest get the lowest number.

I think we both like geeking ! lol

@Tom-Elliott I was referring to adding it now - if it was easy. I know 2.0 doesn’t use PHP. 🙂

@Jbob We use adminfog. 😉

@Jbob said:

@Scott-B we have something similar planned for FOG 2.0. However, for 1.X we don’t want to add any more features (this one would take some significant time). Our focus now is to solely get 1.X as stable as possible for a 1.3 release.

Sweet. I look forward to seeing it down the road.

While I didn’t agree with having this feature initially, it actually made sense so this has technically been added and done now.

Ultimately, I have put a feature hold on. While very minor (such as checkboxes) features may be added, I am not trying to start something as convoluted as this request.

While I understand the need for such a setup, I think it would be much better suited for a new FOG version.

1.3 is planned to be the last PHP version of FOG and while bug fixes and minor features may be backported, I think we should focus newer (and/or more complicated) features should be used to better the next version of fog.

Solved this thread.

@george1421 I will earn you that I did not update the package installation quite yet and I do plan to do this. Basically I just made it so storage nodes install the same way as normal mode does but I did not add the package installation or the same configuration checks. That’s likely the issue with the error displayed but as you said this should not have an impact on the installation process.

I’ve solved this thread as I’m limited to cell phone. If somebody could move this to a more appropriate area it’d be much appreciated. This issue is not a bug. This is more like a feature request buys it not one in going to add. It’s simple enough sure, but can also be accomplished using a hook and/or plugin.

Bump, hope we can find a way… @Tom-Elliott, @Wayne-Workman?

@Tom-Elliott I’ll reproduce and then let you know. I don’t think SELinux was on… This particular case is for a first-time installation on a new server build, I thought the -y option would auto update the DB for me, but it didn’t.

@larosejm If you don’t want to bother about DHCP at all you can even go and bless your Mac clients (see in the wiki article). We use it and it’s working great. But this needs to be done on every machine as the setting is saved in NVRAM.

Or you can go use the DHCP settings provided in the wiki and press ‘n’ on your clients (use stones if you want to multicast many) while booting. The DHCP config in section ‘fancy’ is working for most current devices I find. Don’t bother about the other config snippets.

+1 for this feature.

It would be very nice to have the option to set PXE menu items on Groups/Hosts.