Option to set minimizes or mazimized graphs in Task Management? The graphs used in task management to show progress in a task is set to a minimized format. User has to hoover over the graph to get the full info and full graph. An option in FOG setting to choose between this hoover (minimized) functionality and a full graph would be nice.

This one seems to be very handy [url]https://datatables.net/[/url]

It makes the lists fantastic: sortable and it removes the need of the search function. The filter function is much better.

Clamav does have a default installer, though the location of the configuration changes depending on using epel or CentOS base repositories. I don’t know about making them “selectable” persay, but I could have the FOG stuff not check whether they’re installed / configured so it doesn’t fail out of installation if they don’t get installed.

For right now, though, I’d still recommend installing the relevant repositories.

0.33 now has these parameters. The imageSize is now working properly. It also pulls the information from disk and gets the file size in GiB.

Thanks.

Too many changes needed for this to be included for right now. May look back into after stable release.

“Feature” added.

This “Feature” has now been added.

Thanks, Tom! Big help!! My image names are really long, and they usually take up 2-3 lines of space. So, having the shading helps me in telling where one image name ends and the other begins… 🙂

+1

😉

No i did not tried it yet but i will…

I have this added to my PXE-menu:
LABEL System Rescue CD “Live Image”
MENU PASSWD m0nd30
LINUX sysrescue/rescue32
INITRD sysrescue/initram.igz
APPEND scandelay=1 docache netboot=nfs://10.187.38.3:/images/sysrescue setkmap=uk
TEXT
SystemRescueCD network boot image (recovery)
ENDTEXT
\n
Then you just need to mount the iso from your OS.

that’s possible… but please let’s focus on 0.33 working before adding stuff 🙂
It could be done by using syslinux to boot the init.gz + kernel of FOG, and modifying a bit its code to tell it to look for a file on the disk rather than on a server… interesting…

Thanks for the update on this Tom 😉

Or if you know the macs of the systems just add a simple if statement and perform the task right from ipxe.

Hi there,

from what I understand from your post you want FOG to be able to get the MAC address of the IPMI interface and add it to the inventory.

From what I know about the supermicro IPMI would not be possible without integrating some form of IPMI driver into the linux kernel FOG boots to gather this inventory.

The actual machine doesn’t see the IPMI as a network card as such, only a device in device manager (if it was windows)

When the kernel boots and gathers its inventory you might be able to get some information from dmidecode once said driver is installed but I imagine it would be limited information as its meant to go the other way ie get information about the system while logged in via IPMI interface, not the other way which could also be a security risk.

let us know how you get on as I have thought about this same issue with HP iLO before and could be handy to have a link to the IPMI/iLO from inside FOG inventory

i may have messed up the formatting of the ipxe boot menu when i sent it to you last. here’s what should be in the php file.
note: the first line ipxe sees must be #!ipxe

[url=“/_imported_xf_attachments/0/540_boot.php.txt?:”]boot.php.txt[/url]

You could always use Acronis to load an image on a machine (register it to FOG and load your image from Acronis) but BEFORE booting the OS (that way you won’t have to sysprep again), upload the image to FOG. This would make an exact copy of your current set up and load it to the FOG server in a format it can understand.

I realize that this is very cumbersome if you have multiple images, but it is a work around 🙂

The “Image Size” I’ve been providing is directly how large partclone is reporting the Device Size is. So you would need a drive with at least that size + a little more. There’s no way, for now, to pull all the image size (rec.img.000) size AND (sys.img.000) size, or d1p#.img sizes. It’s not 100% accurate, but should give a fairly good indication of the size needs.

BCD I’m aware of that, but it would mean, image, mount proper drive location, interject the bcd where necessary, and much verification. I’ll try to take time this weekend and test that it works, but it’s no guarantee.

User Management is a goalgoal. I plan to introduce some types of RBAC for users and, maybe later on, groupings of rbacs similar to AD, but less complex.

I don’t have a goals/progress. I’m just a guy who started trying to get the community back up and excited. I’ve been working fairly hard, but I don’t know what all the expectations are. I know the main feature to add before a “stable” release is Windows 8 support. That’s where I’m stuck and I’m sure others are as well.