FOG 0.33 - What's coming?
-
I am currently checking out .33
I have been loitering around the support forums and finally decided to join in. I would like to give many thanks to all working on the FOG project and those who support it. There is a great community and lets keep it alive!
I have been using 0.32 since release and have a pretty good feel for it considering i am not a Linux guru. I wouldn’t be where I am at without the support here. Good work!
Cheers
-
When can we expect to see a final .33 release? Loving this project so far. I just wish that it could boot up systems with nVidia graphic cards. Maybe i am just doing something wrong though.
Keep up the great work!
-
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.
-
This post is deleted! -
This post is deleted! -
@Kevin, thanks for the reply
i will check out the beta and report any bugs if i come across any, and i appreciate it will be ready when its ready!! i also do software development so i know how it works… again thanksWill
-
Yu yo, 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.
-
@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? -
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 textnet user administrator xxxxxxx
;sets password for local admin accountnet user administrator /active:yes
;enables the local admin accountAdd-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 -
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 ! -
[quote=“Blackout, post: 49, member: 1”][B]What’s coming?[/B]
[LIST]
[]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
[/LIST]
[COLOR=#808080][SIZE=2][I]Disclaimer[/I][I]: This list may change[/I][/SIZE][/COLOR][/quote]
will possibly have hot/live capture or deployment -
“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
-
That’s awesome. Can you tell me how you do that?
-
There is already a tutorial, admittedly abit lengthy:
[url]http://fogproject.org/forum/threads/hostname-change-joining-domain-before-sysprep-runs-xp-win7.3332/#post-7964[/url]I can talk you through it if you want.
-
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.
-
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.
-
[quote=“BryceZ, post: 8935, member: 2”]The testing thread is [url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631[/url]. 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?
-
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
-
Have the core Fog developers thought about moving or mirroring the code repository to [url]https://github.com/[/url] ?
Github gets way more traffic than sourceforge nowadays, I think it would lessen the barrier for others to submit issues, patches, and general improvements.
-
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.
