FOG 0.33 - What's coming?
-
It sounds like it depends on the specific implementation.
For me, my source PC is on the domain and I disjoin it before uploading to Fog. I don’t Sysprep. After imaging, I don’t have to run any batch scripts or do any other authentication wonkiness. Using the Fog client, the machines authenticate with KMS and join to the domain without any further action.
-
[quote=“silentsoul, post: 2269, member: 538”]If you ever use a KMS server on those machines you will still have problems. I was doing it the same way, and found out the GUID is likely the same on all the machines so they will not authenticate to the KMS server.
Sysprep is a MUST on windows 7 domain machines.[/quote]
I can confirm this to be [U]INCORRECT[/U], I have a fog deployment of about 1000 desktop/notebooks all of which are windows 7 using KMS.
Never used Sysprep.All I do is unbind from the domain (and disable host rename in fog for the master computer)
ensure the KMS server is set correctly (using the slmgr commands)
Upload.
Download to clients.
no scripts needed, the fog service will deal with renaming/binding.However I have had issues on an old acer where the kms refused to work.
Turns out windows 7 Licencing system uses some special function in the BIOS. A BIOS update rectified the issue. -
This is great news, but i’m a little sceptic.
We’ve had many problems while running fog .0.29 and not using sysprep.
The cloned computers had the same CMID and the KMS server didn’t recognize them as individuals.
Because of that the license count didn’t reach 25, which causes the cloned computers to deactivate.So i’m curious, what is it the fog service does exactly to change the CMID?
And since which version of fog has this been implemented? -
[LEFT]As far as I know fog has nothing to do with the KMS system. [/LEFT]
[LEFT] [/LEFT]
[LEFT]Il check what the CMIDs are on my computers when I get the chance. (slmgr /dlv )[/LEFT]
[LEFT]from what the internet says:[/LEFT]
[LEFT]you need to ether run sysprep on the master or run “slmgr /rearm” then “slmgr /ato” on the clients after imaging.[/LEFT]
[LEFT] [/LEFT]
[LEFT]While Iv never needed to do this, I am using an unlimited KMS server so I guess our results may vary.[/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT] -
I just got my fog server up and running, but like [COLOR=#003366][B][URL=‘http://fogproject.org/forum/members/pluneau.583/’][COLOR=#003366]pluneau[/COLOR][/URL][/B][/COLOR] I am having a problem with a couple of my Linux systems that are using EXT4. The systems are running Linux Mint 12 and wen I go to deploy the image, the client states that the volume couldn’t be found and asks for me to type another. I am going to try to update the kernel to 3.2.4 like [B][COLOR=#003366][SIZE=3][URL=‘http://fogproject.org/forum/members/pluneau.583/’][COLOR=#003366]K[/COLOR][/URL][/SIZE][/COLOR][/B][SIZE=3][B][COLOR=#003366][COLOR=#003366]evin[/COLOR][/COLOR][/B][/SIZE] suggests and see if that fixes the problem. I am still very anxious about 0.33. You guy’s on the FOG team are absolutely awesome!
-There’s no place like 127.0.0.1-
-
[quote=“Kevin, post: 1645, member: 3”]So I have to ask, if you’ve never used sysprep, how do you image the computers with a standard image (software/updates etc) without the image having the same name for everything?[/quote]
I let the fog client rename the machines after imaging and then join the clients to the domain after they’ve been renamed.
-
[quote=“CamC, post: 2330, member: 34”]I can confirm this to be [U]INCORRECT[/U], I have a fog deployment of about 1000 desktop/notebooks all of which are windows 7 using KMS.
Never used Sysprep.[/quote]
I have read some technet blogs saying syspreping isnt required anymore. Personally i dont put too much faith in any technet blogs.
I’m sure in most cases this could be true, but i have ran into issues that have been solved by syspreping the images.
If this is really true, why did Windows 7 ship with a sysprep tool pre-installed?Syspreping will also alert you to problems (not literately, but by failing) long before you roll your image out.
IMHO, spend the extra 10minutes and save your self some time.
[quote=“Markverg, post: 2337, member: 383”]So i’m curious, what is it the fog service does exactly to change the CMID?[/quote]
FOG does not alter any UUID information. -
Hey Blackout. I’m sure that you have gotten this question a lot and I hate to be that guy, but how close is 0.33 to being available?
-
I stand by my assertion that you don’t [I]NEED[/I] to Sysprep, but its certainly a good idea.
According to Microsoft using Sysprep is the only supported method to clone windows. -
[quote=“Blackout, post: 49, member: 1”]We are aiming for a FOG 0.33 RC1 release at the end of January 2012
[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]How this version coming ? I need this one ASAP that Advanced Format is killing us, we’ve had to go back to install os from scratch and pushing out snap’ins cause i can’t image these type of drives
-
Woo, first post in April on this thread
But, any news/updates that can be said about .33? -
[FONT=Tahoma] Hi fog [/FONT][FONT=Tahoma]team Love the Project[/FONT][FONT=Tahoma] how close is 0.33 to being available, if u have in counted a bug in 0.33 that u are finding hard to iron out. Throw it out to the ever growing fog community. Maybe one of us can help. Thanks for all the hard work. [/FONT]
-
There has been some updates recently in the svn.
Hopefully when the time is right for the devs we will see an RC or beta for the ever growing community to test and feedback to nail any bugs -
Things have slowed down recently due to the fact that the devs have real jobs and FOG doesn’t pay the bills. But if anyone is interested in taking the time to pull from the SVN and do some initial bug testing, keeping in mind that it is NOT production ready, then feel free to post any bugs you find in the [URL=‘http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/’]Bugs in FOG 0.33[/URL] thread. This isn’t really a beta or RC yet, but it’s getting close, and adventurous devs or sysadmins might be able to help move things along.
-
Well, except helping with the code,
Where is the donation button?:)-Edit - I found it, thought there isn’t any.
-
[url]http://www.fogproject.org/wiki/index.php?title=Support_FOG[/url]
very bottom.
-
Any update to version 0.33?
-
Sadly due to my lack of free time, i have not been able to keep to the time schedule i wanted.
The code is close to completion. I have rewritten most of the Core code and I’m about 70% way through the Web UI code.
I have not posted as i do not want to promise a time schedule i cannot keep.
That being said, the latest code is available in our SVN repo. ([url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/[/url])
If you would like to BETA test and [U][URL=‘http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/’]post BUG reports[/URL][/U] that would be most helpful.
[U]I would create a test VM for this as 0.33 performs database changes that makes it incompatible with the 0.32 code.[/U]
-
The SVN Log keeps track of all updates to the FOG code.
Since my last post there have been a lot of code updates.
FOG SVN Log: [url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/trunk/?view=log[/url]
Keep the bug reports coming
-
FOG is my favourite imaging tool, but I have to remember to make the base image an ext3 partition each time, so if you could make it support ext4, it will be super helpful!!!
Thanks!
