[quote=“Tom Elliott, post: 26766, member: 7271”]r1622 adds this minor feature.
It works in two steps, first it gives a checkbox to allow “deleting all the hosts”. If that checkbox is selected, it will print off the hosts in the group and ask if you want to delete the hosts. If you submit, it will delete all hosts as well as the group.
Hope this helps.[/quote]
Thanks a lot, it works like a sharm 
Broken in the same meaning as posted a couple of days ago. See screenshot: [url]http://awesomescreenshot.com/0812rutycf[/url]
If you need to test with many hosts please import enclosed file.
[url=“/_imported_xf_attachments/0/722_host_export(1).txt?:”]host_export(1).txt[/url]
Hi! I agree this is not a problem for those of us who understand Linux. I just thought this could be a good idea for all those less Linux experienced out there starting to upgrade from 0.32 to 1.0.0. If they dont run their own dhcp server the central dhcp server needs to be updated to reflect the new PXE filename, which is often a job for some external IT department. I also know that involving IT departments around in large organisations is a pain. The less we have to involve them the better is my experience.
If there was an option as suggested I think we could avoid some questions in the forum. I have not said this necessarily is a good idea, I just want to start a discussion about it If no one else think this could be a good idea I can of cource live with my cp command in Linux.
I have central DHCP server in my organization which I do not manage. It is set up to work with the old PXE boot system in FOG, i.e. it asks for the file pxelinux.0.
Fog 1.0.0 uses iPXE and the file name is now named undionly.kpxe
In this forum I am told all I have to do is to rename undionly.kpxe to pxelinux.0. This works but I have to do this each time I upgrade FOG. Could there be a setting to turn on/off some dhcp-compatibility-mode?
Could be solved in the install script by checking if the file pxelinux.0 exists. If it exists installer could ask if user want to keep compatibility with old dhcp settings. if YES rename the file. Thoughts?
Mass deleting hosts? There is no simple way to delete a lot of hosts. Deleting one by one is very time consuming. In 0.32 I solved this by selecting hosts I wanted to delete in host list and then put them in a tmp group. I could then delete the tmp group. When deleting the tmp group I was asked if I wanted to delete hosts as well as the group. I cannot fint this possibility in 1.0.0. right? A most welcome feature I guess?
GUI is broken in groups. To reproduce, goto Groups, select a group and select e.g. Membership. I run r1621. Same happens on others like Image Association …
More info: Does not happen on all my groups. A group with 5 hosts is OK while a group containing 245 hosts makes the GUI broke.
And you have set password for the linux user “fog” as this: “passwd fog” ?
r1608: the graphs are ok now, but there is still a problem with adding hosts to a group. Works fine from list mode, but not when I search for hosts first and then try to add all found hosts into a new group.
Give this a try:
Works for me on rev 1573, from host and group menu. What OS are you using ? Have you checked your logs for mysql/php errors ?[/quote]
If you refer to the add hosts to group it is correct it worked in provious releases, but has been broken lately.
When showing list of active tasks the bar is put on top of the client in the list first. After the first update the graph is put under the client in the list.
To reproduce: Start a task (upload/download). Show active tasks. Then you will see how the graph is suddenly moving from top to bottum of the client info.
Downloaded and installed svn r1605 but it is still not possible to add hosts to a group.
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.
There are still problems with groups. The problem when searching for hosts and no group options in buttom of the list is still there. The fix is to show complete list first, then search again. The options to add to existing or create new group then appears as expected.
The big issue is it is not possible to add hosts to a new group. I get this error:
Failed to Associate Hosts with Group
No Hosts were selected
Running latest release of today on Centos 5.
The possibility to put hosts into a group is missing: When running the latest 1.0.0 and trying to put hosts into a new group the group options in the bottom of the screen are missing. Not always, but when I search for hosts first. This does not happen all the time. If I start by searching the group options are missing. If I list all hosts first and then seach it shows up.
Broken GUI when editing a group. Running latest 1.0.0 I do the following: Group Management -> List All Groups -> hit one of my groups and the GUI layout is broken as screenshot shows: [url]http://awesomescreenshot.com/0e82r39741[/url]
As you wanted the old 0.33 bug thread to be closed I report here: The problem with deploying win7 reported a week ago is solved in version 1.0.0 and it works like a sharm. No problems with upload or download.
There is one small thing which could be sorted out: FOG Configuration tells [SIZE=4][FONT=arial][COLOR=red][B]You are not running the most current version of FOG! Latest version is 0.32[/B][/COLOR][/FONT][/SIZE]
I have been criticized for mixing bug reports, feature requests and questions in this forum - and for making too many threads etc. I hope a bug tracking system like [url=“http://www.mantis.org”]www.mantis.org[/url] could be considered instead of the forum for reporting bugs (or what the reporter thinks is a bug).
The forum could be used for more general questions, discussions, feature requests etc. I can set up the bug tracker on one of my servers if developers find this to be a good idea.
Again, no critizism about 0.33B. It is very nice and powerful and a lot better than 0.32. I just try to find out how it works. All my questions/feedbacks are not because I dislike/disagree how it works now, but more a question if it works as expected or if it is a bug. It is a beta/release candidate and I thought feedbacks were welcome even if they not always are bugs…