Latest FOG 0.33b
-
Good luck, and if there’s any pertinent issues, just let me know.
Thanks,
-
Tom your a MACHINE with these updates!!
-
[quote=“falko, post: 18095, member: 48”]Tom your a MACHINE with these updates!![/quote]
I think that’s what I was born to do. I know there’s plenty more to do, but I am also starting to see the light at the end of the tunnel with 0.33 release. I have to try to figure out about this sysprep thing with Windows 7. I understand the reasoning, but at the same time I think imaging a system should just be upload image, deploy when needed, presto/chango complete with imaging process. I not a huge fan of: make master, sysprep, upload, verify sysprep didn’t screw up activation (as necessary of course), then try again until you know you’re good, then deploy.
-
Fixed the weirdness with the fog.css file and scroll bars, especially on the dashboard page. Hopefully you all are liking the fixed elements. r957 out.
-
r958 is out, apparently it didn’t take earlier with my move of processlogin to commons. This also has a processmobile login page just to ensure that is there.
-
I know I skipped two, just trust me.
r960 is out.
With it comes a new link on the host management page to view all groups associated with a host. From here, you can remove the association and join other groups. I hope this is what you wanted per feature requests.
-
This post is deleted! -
Trying to install this latest release. Everything appears to install correctly, but I get this when loading management interface:
FOG ERROR: DatabaseManager: Failed: DatabaseManager->__construct(): Error: Host not set
FOG ERROR: DatabaseManager: Failed: DatabaseManager->connect(): Error: Class not constructed correctly
Not sure what the deal is. My /etc/apache2/httpd.conf file is totally blank also. I don’t know if that’s supposed to be the case. Tried both the svn and the bz2. -
I receive same error, Ubuntu server 10.04
Also the fog sql database didn’t seem to be created using 960
-
r961 is out as a quick fix to hopefully get you back rolling with install. I was trying to have it set the database values (username, host, password) from the GUI for both. Will update bz2 shortly.
-
r963 is out, addresses many more of the changes and allows redirect action in DatabaseManager.class.php to operate properly.
-
If you have a sysprep your using for tests, could you post it? I’m in the process of putting one together… one of the new places i’m working with need to sysprep… and unfortunately they don’t currently have an unattend.xml
-
[QUOTE] I have to try to figure out about this sysprep thing with Windows 7. I understand the reasoning, but at the same time I think imaging a system should just be upload image, deploy when needed, presto/chango complete with imaging process. I not a huge fan of: make master, sysprep, upload, verify sysprep didn’t screw up activation (as necessary of course), then try again until you know you’re good, then deploy.[/QUOTE]
Oh man, if you can find some way to either eliminate the need for sysprep or integrate it into FOG that would be awesome! Keep up the good work, I am glad to see this project is still active. I am preparing to use FOG in an environment with around 300 computers right now.
-
r966 has a few fixes to issues that were quite troubling to figure out. I can only hope all works properly now. You should work properly now. I’ve tested on centos 6.4 and ubuntu 12.04. I’m nearly certain it will work. I’m sorry if this troubled you all!
-
r968 is out, had to revert to 899 functions.sh files for ubuntu and redhat, added back the fedora 19 specific stuff for redhat/functions.sh.
-
r970 is out.
Added to the FOG Settings part, to allow it to redirect and inform the user that their stuff has been changed rather than redirect to the index and no input whatsoever. Also made some changes to text field sizes.
-
[quote=“VincentJ, post: 18176, member: 8935”]If you have a sysprep your using for tests, could you post it? I’m in the process of putting one together… one of the new places i’m working with need to sysprep… and unfortunately they don’t currently have an unattend.xml[/quote]
I’d post my unattend, but it has the key we need for our tasks and the administrator password is in there as well. If you can, try finding andyroo’s post for hardware independent setup, I’ll try to post the look soon. It explains how to create an unattend file for your organization.
[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]
You don’t have to follow all the instructions, but follow the stuff for creating the unattend.
-
Hi Tom,
You’re not human, you’re an alien!
Regards -
r972 now released. With this comes the same fixes as before, but now, you can join a host to multiple groups at the same time, and cross-wise, you can From the groups page, add hosts to a group. Hopefully you all enjoy.
-
r973 is out, just makes the system where you can’t have two hostnames the same. I know this may hurt initially, but it will enforce we keep our inventories sort of clean. I know at my workplace, we had a huge issue when we had to replace a system, and we located it by hostname and found 7 generations of systems all with the same name.
