Latest FOG 0.33b
-
r928 out. Contains Plugins again. Sorry I didn’t know they even existed.
-
Hostname changer doesn’t seem to be working in 33b.
Great work so far. things are looking great.
While your doing reconfiguration… could you try to add compression choices to the GUI?
-
I don’t know that compression choices could be set from GUI. The init.gz file performs the compression using pigz, but that doesn’t mean it couldn’t be using gzip or bzip compression, but I think that would be better suited on the client level from the fog script.
-
Also, how is it that you know hostnamechanger isn’t working? It isn’t changing the hostname after image upload? it isn’t joining active directory?
What exactly is letting you know hostname changer isn’t working?
-
Error in the log which got overwritten during troubleshooting, and none of the 4 VMs I was using would change their hostnames.
If nobody else is experiencing the issue, then maybe it’s just a one off. I was only able to run a few tests.
I can try to replicate it in a couple of days if needed. I have 0.33b saved in a snapshot.
-
Also, I’ve just reverted to fog 0.32 and the exact same VM booted and changed hostname as expected without issue.
-
As far as I can tell, the GUI side of this is working properly, but the client side may be having issues. I’ll test for sure, but I’m not certain how to rebuild the client.
-
There were a couple of issues and I’ve, seemingly, fixed them. Hope this helps you out.
Please redownload and test with r930
HostManager.class.php which does the update/insert for the hostname still was referencing hostOS which doesn’t exist.
-
r932 out.
With it comes Export Hosts, Fixes/Improvements to Printer Management, SnapinManagement, GroupManager.
It also display’s a primary group now on the hosts.
-
r933 is out.
It has the export.php file for the exporting of stuff. Just forewarning, I’ve got the base components of configuration export in place as well. To view it, goto:
[url]http://<fogIP>/fog/management/index.php?node=about&sub=config[/url]
It just has export so far and not quite a pretty thing, but please view and suggest.
-
r934 is out.
Import and Export is now there under FOG Configuration.
Hopefully it’s a start.
-
r935 is out.
I know it’s the little things I keep missing. It actually adds the menu option in FOG Configuration called Configuration save.
Also, with this, the oui.txt file is now redownloaded before updating the mac list. Hopefully to keep things up to date with new hardware.
-
Nice Tom, will need to update my vm and test. Can see you have been busy, think I’m on r923
-
I will give it a test
Great Work tom. -
Damn not only do we get updates almost daily, we can see you obviously spend a lot of time working on this, and we appreciate it!
Keep up the good Work Tom, time to update my VM as well
-
All,
r939 is out. With it everything that I accidentally broke from r927~ ish is now fixed. I moved the mainmenu.include.php file and forgot to add it to the commits. Again, I’m still getting used to svn so I’m very sorry. It’s all there now. It got moved from:
fog/management/includes/mainmenu.include.php to commons/mainmenu.php -
Hi Tom i’ve had that issue with mainmenu.php yesterday, i’ve made a fresh install from SVN repo and found the issue but I didn’t have an account on the forum, so I fixed it on my own hopping someone would report it…
I’ve also had issues with the FTP account, the fog+randomnumberpassword won’t work out of box, i had to “passwd fog” user and change settings in config files + in FOG webui.
Now i’m stuck with classic 0xc000000e hardware has changed, is FOGPrep still ok ?Keep up the good work!
Alexandre GAUVRIT
-
I changed the fog storage (database user) password so it randomly generates a number between 0-1000000 (or something ridiculous like that) so it would have a more secure base line. This password is not the password you should use for TFTP_FTP Password or the Storage node password. That password should be changed, to my knowledge, as you’ve described here with the sudo passwd fog or passwd fog if you’re already in as root. Make sure both spots, one under FOG Configuration->FOG Settings, and the one under your storage node match properly.
Also, I believe FOG Prep is still okay to use, but if your image is not of the same hardware, the hardware change is to be expected. I’ve never had to actually use FOG Prep where I work so I’m not sure exactly what it does. I do know, if you’re using 0.33b, you’re supposed to sysprep the image before uploading/deploying because that’s a change, I think, Chuck made to start allowing the support of Windows 8.
-
I think fogprep was used before uploading an image that wasn’t sysprepped. To be honest I a have not used it in the last two years so my memory is kinda vague on this
-
I agree with Falko, It was to my understanding that before the tweaks were made so that Win 7 and Win 8 could be uploaded you had to use FogPrep before uploading the image.
Now that we sysprep and the FOG server knows how to handle the partitions, I have not used FOGPrep.
To be honest I never used it on my XP images either
