Latest FOG 0.33b
-
yes… well you can set that up in capone to use certain dmi fields… but mine gets stuck reading dmi it seems like
-
We have a person who seems to have this working.
I’ve never used plugins but it seems that if your DMI field is set to Bios-version, and you type 1.0 in the DMI Field, all systems that match that would be assigned with the appropriate information such as: imageID, join domain, or what have you.
Again, I don’t really know how this all works so I could be talking out my *** here. Maybe somebody with knowledge/understanding of how this works can chime in?
-
+1 for the *** reference! On 32 Capone works BUT I did had to modify something, cannot remember what, but I was using system product, like optiplex620 assigned to a optiplex image, it works great.
-
r987 out. Its only a minor change but user tracking seems to work properly now in that you can change the date.
-
Silly question from a noob, i’d like to update my SVN version of FOG 0.33b (don’t remember the r*** number) to see if it can solve a problem with WindowsXP+Resizable problem (Partimage prompt a “Third argument invalid directory/fifo”), what’s the best way to do it ?
svn co on existing folder and relaunch install.sh ?
other idea ?I’d like to keep my actual installation which works fine.
Sincerly, Alex
-
What I’d recommend is just checkout what you need. You probably need the tftp folder which would be
[code]svn co https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp[/code]
Then just
[code]cp -r tftp/* /tftpboot[/code]Then you’ll need to edit the /tftpboot/pxelinux.cfg/default file to readjust for your server.
-
Hey all,
Just wanted to give you an update as to why I haven’t been making as many revisions as you’ve seen in the early past.
I assure you all I am still working on these things, but I was finally able to get 0.33b testing within my workplace. With this, I’m trying to test and fix specific things within.
I was able to get Printer Management working and am currently working on Snapin Dploy working. This is taking longer than I expected, but I’m just trying to make things operate properly. I hope you all understand.
-
Tom this sounds great, appreciate what you are achieving and doing for us FOG folk!!
-
Thanks Nathan for the support.
Also,
I wanted to try something as a test with this, but I am stuck testing within VM modes at work. Maybe I can get the community to test this part.
I’ve added, I think, recognition within the ClientServiceManager to look for additional MAC’s. Theoretically this should allow you to use the FOG Client even on wireless clients. I have NOT…I repeat…have NOT added wireless device recognition/adding for wireless MACs into the init.gz file. My worry with doing such a thing is make a kernel that’s just too large for a simple imaging solution. If I were to add Wireless adding of mac’s it could, potentially, add about 30-50 mb to the size of the kernel, not to mention the wireless tools needing to be built into the init.gz itself.
That said, however, I think I might be able to get the FOG Service hostregister utility to do this work for me. It isn’t added yet, but I with the addition of the hostname checking, I think I can have it, now, pull the information from the system and add it to the correct areas.
-
r988 out.
I doubt it’s fully complete, but it looks like I can finally view snapin jobs. I can’t tell if they’re actually working yet, but I’m almost certain I’m getting close.
-
Tom Elliot, i think i love you. :rolleyes:
Good to see the progress
-
While I appreciate the the sentiment there @tuxmania, I think my wife would say otherwise
r991 is out.
Just add’s a few fixes to things I noticed where problems.
-
r992 is out. Finally working towards refining methods. All service files now use, seemingly proper as well, the base.inc.php.
-
Finally going to get time to give 0.33b a try. Big thanks for ALL the hard work Tom.
[SIZE=6][B][FONT=Helvetica Neue][COLOR=#000000][SIZE=24px]“A Giant among men”[/SIZE][/COLOR][/FONT][/B][/SIZE] -
First of all, Tom it is great to see that they finally have someone like you working on the next version of fog, YOU ARE A MACHINE!!!
Anyway a quick question for you,
Is there any timeline of any kind that you may have on getting 0.33b to work on uefi bios devices?
This is the most crucial part of Fog that i need to work, as I am in the same boat as you with working at a school district and am looking at getting 100’s of new tablets (Dell Latitude 10) by the end of the school year. Getting Fog to work with these new devices would be a great plus as I ABSOLUTELY HATE USING WDS. So no pressure of any kind ;). -
Though I know there’s plenty more work to get the GUI at 100%, however I think I’ll start playing with partclone and see if I can get any status on this for everybody.
-
Awesome, I would like to seem some alternatives!
I would even like to see using the cloning portion as a “add-on” so that other can choose the derivative they want to go with. I’ve seen some people talking about using the Bittorrent to transfer, this would be a BAD idea for my environment, we have HEAVY restrictions against the torrents, but It would be nice to have an alternative for those that aren’t locked down as heavily as I.
Keep up the good work Tom, so far my 0.33b server is working beautifully, I should probably update it though, I’m still on 98something
! -
Torrent is one method I was suggesting… If the replication has an option to turn off so you can implement your own then those of us willing to build what works best will have an advantage.
What method would be best in your environment?
-
Hi Tom, I’ve been following your progress with 0.33b and finally decided to implement your revision onto a fresh ubuntu install. I have hit a snag with the auto register. Despite changing FOG_QUICKREG_AUTOPOP to 1, the client machine wont image after quick registration. Is there a config file somewhere that I can manipulate?
-
When changing the FOG_QUICKREG_AUTOPROP to 1, are you doing it from the <fogwebdir>/commons/config.php or are you doing it from the FOG GUI.
