FOG 0.33 - What's coming?
-
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=“Blackout, post: 4686, member: 1”]Any in particular?
Most of the core basic functions work (imaging etc) for all O/Ses with the exception of NTFS Re-sizable partitions.
With the latest updates (about a week ago, all in init.gz) these options work as intended, but there are still some bugs to work out with advanced format drives.
Right now I’m doing a lot of testing to get it all working - this eats up a lot of time waiting for Windows in VM on my slow ass workstation
Various GUIs need their POST save functions ported from the old code. i.e. FOG Configuration page
I’ve devoted today to FOG dev, we will see what happens :)[/quote]
I know how it is…
You rock sir, thanks for replying -
Any chance their may be support for Windows 8?
-
Windows 8 support is being tested.
-
[quote=“BryceZ, post: 9257, member: 2”]Windows 8 support is being tested.[/quote]
I hope this helps the progress. I set up a virtual machine running Windows 8 Enterprise with a single partition and uploaded it to FOG. I ran the fogprep exe which I had to modify because it does not support Windows 8 (I just commented where you check to make sure the machine is running Windows 7 because the registry keys being modified are exactly the same in Windows
and I ran sysprep with my unattended xml answer file. When I tried to download the image to another machine, I received an error at boot saying “Booting… Missing Operating System”. I dug into the fog source code with my boss and discovered that the issue that there is a method that checks the os and applies one of several mbr files that you have. Because Windows 8 is not supported and I selected Windows 7 as the host os on the fog web interface, it wrote the wrong mbr to the machine. After we copied the correct mbr and wrote it to the machine, it booted correctly. There still is a problem, however. The hard drive was not resized properly to the size of the new machine it was being imaged to. The new machine is showing only ~40GB which was the size of the actual fog image. Also, I am not sure that the fog client is working properly. It has not rebooted the machine yet to change the name and add it to the active directory. -
Thanks Jesus, the more testing the better. The thread for beta testing 0.33 is [url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631[/url], feel free to document your test results there.
-
Hi everyone,
First of all, thanks to all the developers who do such an awesome job.
My question is if auto-register from the client installation is going to be included in the new version. It was included in 0.28 and before, but for some reason exluded in versions 0.29 and after. I find it highly useful now that we are going to massively deploy clients in our institution.I am looking forward to seeing this new version! You are the greatest!
-
Hi, 1st off id like to say FOG is a brilliant solution, ive imaged about 600 PCs/Laptops so far, its massively amazing! this may have been asked many times and may be in other posts, so im sorry if thats the case, just wondering if there is any updates on the release of .33?
Thanks
-
I am very excited for .33! .32 has been great! It has made my life so much easier for deploying new PC’s, and refurbishing PC’s here at the office! Much better than any other cloning solution I have tried! Kudos to the developer! I am running uBuntu 10.4 on an old intel core 2 duo machine with a gigabit ethernet card & 4gb of ram. Has a 1TB HDD that has only a few images on it, but it is rock solid! I did have a problem with the latest kernel, but switching back to an older kernel was a breeze!
-
[LEFT]@maafty, unfortunately there is no projected release date for .33. This new version is a complete re-write of the code, and not a simple patch update. So the answer, although no one likes to hear it is, it’ll be ready when it’s ready :). It’s taking some time to get everything worked out. However, there is a beta that you can try and report any bugs you find in our Bugs forum. Just note that this is still a beta and there could be bugs. You can try the latest version by installing subversion on your machine and entering:[/LEFT]
[LEFT] [/LEFT]
svn checkout [url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk[/url]
(Make sure you are in a folder, this will download all the folders/files from FOG in your current directory)I’m glad to hear that FOG is working well for you!
-
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 !