Hey Tom, Thanks for all your work on fog btw. I was just updating the database on my own directly through the console.[S] I’m not sure how to use the schema update. I did a quick search and didnt come up with anything.[/S]

I guess i should also ask if you are working on adding LDAP support for users to log in?

edit: So i just had a quick peek at the schemaupdater php file and realized how to use it. I’m still not clear as to why the direct database editing didnt work but i’ll take what i can get.

I don’t understand what you’re wanting.

You want to get an automated report of the user tracker, using FOG’s Report system?

The URL you’ve got get’s the all systems the userid has logged in. The userid is base64 encoded to help you out. but the “rest” of the url is actually from when you click on the PDF or CSV Icon’s. It parses the displayed information to give you the PDF or CSV file.

The host=0 does not mean all hosts the user has logged into, it’s just a “place” holder though when you do choose.

You’ll likely have better luck if you generate your own report to obtain the information you need. For example, being able to specify a group. How to export autonomously is a little more “technical” than I can think of, but a simple means, I think, would be to simply have the needed parts of the report (the table start and information within) generate on it’s own page. THen you could script htmldoc to read that page to generate the PDF.

Just to update you, I have just tested updating the image in fog 1.1.2 which uses part clone to capture and the progress bar is now working. 😉

Thanks for the help, appreciated. 🙂

Right now, drkpool website is no longer server. Chuck is working to rebuild the fogpackage.zip project with the new information.

What line 287 and such are for, is to detect the filesystem format and create the partition image file. This means if it’s not one of the known supported types, it’s just going to create a raw image of that partition, but all other partitions will be able to use the partclone.{$fstype} file.

If you’re interested, it is actually fully possible to do this over the web, but as Jaymes says, would require some customization. I believe, have not tested this means, that all you’d have to do is change all the references of IPs to hostnames. In /tftpboot/default.ipxe there’s one line that would need to be changed on the server. You either change it to the externally accessible IP or FQDN. On the fog GUI side you’d need to change the IP of storage management page on your node to the externally accessible IP or FQDN. Finally you’d make the change in FOG Configuration->FOG Settings->tftp server and web server to be that of the externally accessible IP or FQDN. This should enable uploading across the internet as well as downloading images, or any task for that matter.

Again, I haven’t tested it fully, but it already exists with minimal changes. It looks like a long block of text but in steps its really only 4 items to change.

Is there anyway to password protect this option. Might be kinda dangerous to leave this unprotected in my live environment

Ok.

Thank you very much.

I’ll take a look at the installer and see if I can do anything about that.

found the trouble: Location table is not not up to date with nfsgroups* tables in database… manual update of the table location solves the problem

just need to check in the gui how to solve it

Thanks Tom, a restart solved the problem.

Thanks!

I don’t know if it is any consolation but I use the Intel PRO MT desktop version and set promiscuous mode to allow all.

I greatly agree on Debian 7.

checking your DHCP leases for ‘NEWDEPLOY’ hostnames is a quick way I get to know if PCs are still in the process of joining domain etc… or if they have failed to do so.

No Problems deleting the partition. restored just fine.

I think the best option for you would be to make a backup of you Images folder and your database, and then scrub out 0.32 completely. Then install 0.33 from scratch, import your database and images folders, and then do the database modifications laid out in the wiki. Finally, run the installer one more time, then and only then, log in to the web gui. The only thing that I ran into after that is the TFTP settings that needed correction and for any clients that did not have an image associated I needed to open each host and select an image or the top dropdown option for none.

Yeah, $part is the correct variable. I saw this issue in 0.33 as well, and have since changed the calling to $part over $win7sys.

The error message you’re reporting is about USB, not about FOG or space.