FOG 0.33 - What's coming?


  • Developer

    [B]What’s coming?[/B]

    • Rewritten PHP code base to be fully Objected Oriented - easier to develop & maintain
    • Developer Tools - create your own FOG Page’s to suit your needs
    • Hook System - manipulate data & structure easily
    • Web UI update - tabs, style updates, lots of code updates & bug fixes
    • Mobile UI update - revamped structure & styles
    • Partclone - EXT4 & Extended Partition support
    • Advanced Format Drive support - 4k sector support

    %(#808080][I]Disclaimer[/I][I])[]


  • Senior Developer

    Add the caveat now to Fedora 19, being that they changed the database (mysql) to mariadb. All works, but requires minor changes in the script. I’ve already created a thread pointing out the issue with Fedora 19 and a fixed tarball for it based on FOG 0.33b, though the same changes could just be made in 0.32.


  • Senior Developer

    @mlb2009, post: 15451, member: 13741 said:

    in fog 0.33 it will be installing and working for fedora,right

    From my knowledge it is all set and should work for all the Distro’s it nativally supports (Redhat/Centos/Fedora)([X]Ubuntu Based)

    For non-standard distro’s you could get it to work, though it might take a little extra work.



  • in fog 0.33 it will be installing and working for fedora,right



  • @nicked check out link below for status of 0.33

    http://fogproject.org/forum/threads/fog-status.4515/



  • Any Idea when 0.33 will be in final release?



  • Quick update: Yes, 0.33 is still under development. Work has been stuck for a while due to the schedule of the developers and the fact that the one big remaining issue is UEFI. If anyone out there is interested in pushing things forward and has the time to spare, the devs could really use some help working out the whole UEFI booting.

    Other than that, the rest is just fixing little things throughout the UI. FOG 0.33 didn’t start with a solid bug tracker, and the dev that did most of the rewrite has had to step back from the project, so there are pages that didn’t get finished but they’re not all documented in one place. So if anyone wants to systematically go through each page and track down all the little pieces that don’t load properly it would help a lot.

    If I get some time today I’ll try to read back through these posts and answer individual questions that I know the answers to; like Stephen DiCato’s question about GitHub: they’re waiting for 0.33 to finish before migrating to GitHub.



  • Hi Devs! Firstly, let me start by saying you’ve done a fantastic job with this project. I was introduced to it about 3 months ago and I’m totally in love with it! That being said, I recently decided to give 0.33B (rev 899) a shot to check out the ext4 support along with other perks that seem to be coming along nicely. But, when I attempt to upload a ext4 image, it is still seen as ‘raw’ and sometimes doesn’t upload the partition at all (only about 914 bytes, actually). However, if I’m uploading an LVM or encrypted partition (also ‘raw’) it seems to work fine. Is this something that should not be happening with 0.33B or did I somehow b0rk the install?

    Again, great work on such such an awesome project! Thank you all very much for continuing the development.



  • Have the core Fog developers thought about moving or mirroring the code repository to https://github.com/ ?

    Github gets way more traffic than sourceforge nowadays, I think it would lessen the barrier for others to submit issues, patches, and general improvements.


  • Developer

    Everything is still in development, Everyone that works on this project does it in their free time.

    0.33 is a serious re-write of code so it is taking some time to complete.

    I can assure the project is still in development, the developers just have lives :)



  • http://fogproject.org/forum/threads/bugs-in-fog-0-33.631. Feel free to jump in and give a hand, just make sure you’re not cluttering up the thread with useless questions (search before you ask).

    As for a release date… when it’s ready. I know that’s not the answer most people are looking for, but it’s the truth. There are three FOG developers, each with real jobs that keep them busy. If more people help with testing then the devs can spend less of their own time tracking down bugs and more time fixing them.[/quote]

    Is this still a work in progress? or is it dying?



  • Any way it would be possible to allow addon images? It would definitely help with driver deployment to have an addon image that is downloaded to C:\drivers that is specific to the machine and separate from the windows image. Otherwise .33 beta is installed and running for us right now, upgraded from .32 without issue.



  • That’s OK. I enjoy a good mystery novel and I will remember it better if I work through it. Thanks for pointing me in the right direction.


  • Developer

    There is already a tutorial, admittedly abit lengthy:
    http://fogproject.org/forum/threads/hostname-change-joining-domain-before-sysprep-runs-xp-win7.3332/#post-7964

    I can talk you through it if you want. :)



  • That’s awesome. Can you tell me how you do that?


  • Developer

    “re: “It would be awesome to include the option of tweaking sysprep.inf / unattend.xml to change the hostname and join an AD before booting the computer after deployment.” We use Powershell for that. The Unattend.xml does it all, we log into the desktop and run our Finalize.ps1 which enables and sets a password for the local administrator account, joins the computer to the domain and restarts the computer.”

    I use FOG to change the unattend.xml before it reboots after imaging so before it even boots into sysprep all options are set as needed and jsut let sysprep take care of it all - never fails and requires no additional reboots after imaging (like changing hostname, adding to domain) because it’s already all correct before booting into windows :-)



  • @Blackout, post: 49, member: 1 said:

    [B]What’s coming?[/B]

    • Rewritten PHP code base to be fully Objected Oriented - easier to develop & maintain
    • Developer Tools - create your own FOG Page’s to suit your needs
    • Hook System - manipulate data & structure easily
    • Web UI update - tabs, style updates, lots of code updates & bug fixes
    • Mobile UI update - revamped structure & styles
    • Partclone - EXT4 & Extended Partition support
    • Advanced Format Drive support - 4k sector support

    %(#808080][I]Disclaimer[/I][I])[]
    will possibly have hot/live capture or deployment



  • hello
    just to thank again for your work !
    i’m using 0.32 and when i can test 0.33 i’ll do it (busy job too). Congrats to the team !



  • Correct. This allows us to set the computer name, etc. before we join.

    Finalize.ps1:

    reg import c:\deluser.reg
    ;imports a reg branch that tells it to run a batch file at next boot. The batch file deletes the temp user account created by sysprep and also deletes the finalize.ps1 file as it contains the local admin password in plain text

    net user administrator xxxxxxx
    ;sets password for local admin account

    net user administrator /active:yes
    ;enables the local admin account

    Add-Computer -DomainName “student.emcc.edu” -credential student.emcc.edu\itadmin
    ;adds conputer ro student domain (prompts for credentials of domain admin account)

    restart-computer
    ;reboots to complete



  • @Steve: So you deploy the computer “out of the domain”, with a LogonCount=1 in your unattend, and join the domain once it has logged in, right?
    Can you post your Finalize.ps1? (Hiding your sensitive data, of course ;) ). It goes on C:\Windows\Scripts, as your SetupComplete.cmd, right?


Log in to reply
 

418
Online

38920
Users

10688
Topics

101407
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.