any of the developers can maybe confirm if there has been any changes made to the way storage nodes operate between 0.32 and 1.2… if it hasn’t and the process is exactly the same then would be even more useful.

Testing 1.2 in my environment, but will be on 0.32 for a while yet.

It’s seem to be OK, but no mass update with groups 😛

user access controls is a feature that is currently under development, but it is unknown how long it will take to complete.

Use Webin ([url=“http://www.webmin.com”]www.webmin.com[/url], free of charge) and you can easily set up both cron jobs and automatic database backups, and a lot more as well. The best server admin software there is!

No SSD drives, they are standard Optiplex 3010’s. Will give the delayed started trick a go.

Why is an option needed? It’s assumed that /images (which you can change at install time) is the default location. At this point, it’s already assumed that the disk space and requirements are already available. I’m not going to try guessing what type of filesystem needs to be mounted, and I’m also not going to keep adding options to the installer simply because you think that’s just how it should be.

Do you know what it would really entail to assume mounting of filesystems/disks during this phase? I know you think it’s something small, but our guesses are that it’s unrelated to mounting at all. If you have special configurations to take to get things working, you need to get them sorted out.

Storage being one of those things.

Last logged in user hasn’t just been talked about but has existed since I believe 0.29. It even tells you the times they login and log out. Knowing a system is powered on could be performed by enabling host lookup and allowing the systems firewall to respond to icmp requests.

That did work!! Hallelujah! Thanks vinyard and Tom!! I ran the following commands and now its uploading that first image:

systemctl status nfs-server
systemctl enable nfs-server
systemctl start nfs-server

Thanks guys, success at last!

to expand on what Tom said and clarify what kind of time frame we’re talking about, 1.3.0 is our next release point (weeks to months, expected), and 1.4.0 would be the next major release point (months to years away).

I’ll see what I can do, where it does something similar to how image association or location association is done. It basically just adds the info based on if all the hosts in the group have the same data. If so, it display’s that in the list, but for multiple items, this is rather difficult to accomplish programmatically, so I’ll see what I can do, but don’t hold your breath too long okay?

[quote=“Tom Elliott, post: 39714, member: 7271”]If what I’m reading makes sense, you’re requesting a custom background for the partclone screen? This isn’t really simple…or practical. It’s very very difficult as the info you’re seeing is programmed by another source, not me. So much coding is in it that I doubt it’ll be something I can ever figure out.[/quote]

I am aware of this…just thought i would bring it up just in case FOG ever expands to the point where you guys have a big DEV team that would be capable to do something like this…just throwing an idea out there, that is all. 🙂

Or here was another thought…

Maybe we can set the “Join to group” option so that when a particular new machine gets joined to a group, it automatically pulls down the group settings for that group. (IE AD OU stuff)?

I know changing it to 3 for me has cut my upload times in half.

[quote=“loosus456, post: 38867, member: 26317”]
So, here would be the requests:
[LIST]
[]A way in the FOG web console to determine which computer(s) are holding up the rest. Is there a way that FOG can determine which computer(s) are the problem?
[]Once it has been determined which computer(s) are the problem, a way to kill off just these computers from the multicast task and let the other computers continue imaging at the higher speed.
[/LIST]
Are these realistic?[/quote]

I use Iperf to determine wich computer have bad bandwith. I’ll try to added iperf on iPXE.

Regards,
Ch3i.

[quote=“Tom Elliott, post: 38874, member: 7271”]There already is that feature, under the host and under reports.[/quote]

OK… I left my brain in my bed, I think… 😄

if the only reason you want to use custom init’s is because of the xp imaging issue, that problem is fixed in the development version of fog. just use the latest dev version and your problem should go away.

redo backup / ghost / acronis trueimage etc can all do this 🙂

fog is a very good piece of software for imaging networked PCs.

slightly problematic are laptops that are normally wireless but these are things you accept.

possibly if the developers spent all their time creating what has already been created the main product (network booting and imaging) might suffer.

also… if this is windows your imaging you could use the windows tools to make an unattended USB that automatically installs windows.

I love the direction fog is going 🙂

I already saw, merged, and fixed in both git and svn.

I’ve created a table in FOG that does, more or this, exactly what’s being requested.

Because of this, for the most accurate of data, please use the proper filenames as it’s the best method I can come up with.

If you’re interested in finding out what files work and such, hence the idea behind the generation of this table, rather than setting your dhcp filename option to undionly.kpxe, start out with ipxe.pxe. Test your systems, and find out if the systems can boot under ipxe.pxe.

If they can, there’s little more you need to do.

If not all your systems work, then try the undionly.kpxe file. The table will read the new file name and create a new entry if it makes it into the menu. If it doesn’t make it into the menu it won’t enter it.

The basic construct of the table currently is:

Product, Manufacturer, Boot file, and mac address.

It will not keep making entries in the table for every mac address. It will only make new entries if the filename, product, and the manufacturer does not already exist.

This way, let’s say you changed undionly.kpxe to ipxe, you may end up with an entry for the same model of system for multiple files.

The ideology of this table is to eventually allow centralized place for fog and the ipxe team to better know what systems work and with which files.

Of course, when this gets entered, it will be completely optional to send this data to us.

Once we have the “central” table setup, the table will allow us (the developers) to hopefully code in what systems and what files to use for those systems.

For example, if we know the ipxe.pxe works for the Dell ts1700, and you’re booting to undionly.kpxe, We can supposedly cause the undionly.kpxe to rechain to ipxe.pxe. This would allow better operation of the nic during the ipxe state.