Latest FOG 0.33b
-
Or create a “Storage Group” special for NAS ! :rolleyes:
-
There is a small problem with the page “Report Management-> host list”
[CODE]/var/log/httpd/error_log
[Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: array_unique() expects parameter 1 to be array, null given in /var/www/html/fog/management/reports/Imaging Log.php on line 119, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
[Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: rsort() expects parameter 1 to be array, null given in /var/www/html/fog/management/reports/Imaging Log.php on line 120, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
[Thu Mar 20 14:09:42 2014] [error] [client 172.16.8.167] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/fog/management/reports/Imaging Log.php on line 121, referer: http://srvfog.cavp.fr/fog/management/index.php?node=report
[/CODE][url=“/_imported_xf_attachments/0/605_Capture.JPG?:”]Capture.JPG[/url]
-
Once again, set your image and os id records on your hosts.
-
[quote=“Tom Elliott, post: 24487, member: 7271”]Once again, set your image and os id records on your hosts.[/quote]
Yes maybe but it is a “csv” import of hosts, and it may be that all is not specified, but I still think these messages should not be there. -
This is because you have debug enabled on the pages. If you don’t want the errors, find the relevant pages and turn off debug.
We have this enabled for tracking down BUGS specifically, but it’s also useful to know where some of your issues may lie.
-
Since we passed the boot “PXE” to “iPXE” option “Shutdown Schedule Effective task completion” does not work anymore.
[url=“/_imported_xf_attachments/0/606_Capture.JPG?:”]Capture.JPG[/url]
-
I’m aware of that. Still working on fix for the moment. It’s simple, but requires schema update. Trying for a better route if possible.
-
r1353 released.
Fixes the display on logout of mobile page. Also fixes the shutdown issue reported above. Updates schema to version 80.
Thank you,
-
r1354 released.
Fixes the Debug messages thrown if Host doesn’t have an image set for the Host List report.
-
r1355 released.
Disables the unsetting (completely) of image if the host is part of a tasking job.
Thank you,
-
r1355 - > I could not attach “Host image” on the “Host management”
-
In FOG Configuration->MAC Address Manufacturer Listing, when i “Update Current Listing” there is message “Unable to locate file: ./other/oui.txt”
[url=“/_imported_xf_attachments/0/607_Capture.JPG?:”]Capture.JPG[/url]
-
r1356 released.
Simply adds alt tags to the main menu icons for both the main and mobile sites.
-
r1357 released.
Fixes the kernel parameter so you can specify a kernel to a host. If it’s specified, it will use that kernel so make sure you have the right case and name. bzimage and bzImage are two completely different things in the linux world.
-
r1358 released.
Just removes more excessive php tags especially in schemaupdater. Removes chkdsk if it’s disabled.
-
r1359 released.
Fixes kernel generating parameter so it works all the time, not just when the host is valid. -
r1360 released.
One more fix, this type should be much better, sorry. Makes sure kernel is set by host if it’s set for the host. Also, if there was no task generated, you wouldn’t be able to update the kernel parameter on the host. This is now corrected for as well.
Thank you,
-
Hostname changer: When the Hostname changer service module if ON, will a client change hostname during the last stage of Deplaying? Or is it necessary to run the FOG client on the client? I run 0.32 at the moment and several clients do not change name during deplayment on Windows 7. It seems quite random to me, which client change hostname and which does not. It this is a problem with 0.32, has it been improved in the 0.33 betas?
-
I haven’t tested quite that thoroughly, but it seems better in 0.33b yes. That said, do your systems join to a domain? If they do, the hostname changer service is what handles the joining as well as the hostname change. I don’t know what will make this work 100% of the time though as it’s done through registry keys. If you’re not sysprepping the machines I assume things should work perfectly fine, but if you’ve sysprepped an image, then it’s really up to the unattend.xml file for the rename.
-
Thanks. My systems do not join domain and I do not use Sysprep. Good to hear it problably works better in 0.33b. I will do some testing when I get time to set up a test server.
