FOG 0.33 - What's coming?
-
And where 3.2.4 ?
-
-
3.2.4 can be downloaded from here, [url]http://sourceforge.net/projects/freeghost/files/Kernels/Kernel-3.2.4.core/Kernel-3.2.4.core/download[/url]
-
Then you need to backup bzImage in /tftpboot/fog/kernel. so I renamed mine bzImage.backup (If this doesn’t work, either log into the computer under the FOG account, or chmod the folder)
-
When you copy the 3.2.4 kernel to this location rename it to bzImage (note that the case is important) and you should be all set.
-
-
OK Thank
-
what’s news in this version ?
-
the 3.2.4 kernel should support the EXT4 filesystem. All the other changes for version .33 of FOG are listed in the first post of this thread.
-
[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]Those features sound good but i would like to know (it may help others also) is a explanation of these new features like it was done on the[URL=‘http://www.fogproject.org/wiki/index.php?title=Main_Page’] fog wiki’s change log page [/URL]
-
[quote=“Kevin, post: 1665, member: 3”]the 3.2.4 kernel should support the EXT4 filesystem. All the other changes for version .33 of FOG are listed in the first post of this thread.[/quote]
Upgraded to 3.2.4 kernel and can in fact image my linux box with ext4 now, though because it is multiple partitions, it takes a long time to do it.Looking fwd to .33 to work/play with!
-
Any updates to the release of 0.33? After evaluating 0.32 at my company and getting extremely favorable results, I’m waiting to take what I’ve learned from 0.32 and apply to 0.33 and invest in a major multisite system imagin rollout.
Will the “patch” for multisite storage nodes across WAN links be included with 0.33. That is a “MUST HAVE” feature. A colleague and I have worked the existing software to allow TFTP/PXE in multiple sites and leverage Windows DFS to replicate the images.
Keep up the outstanding work.
-
I have just changed jobs. In my old job I deployed 300 desktops using FOG. My new job has 600 desktops and the company uses Symantec Alitiris. Can I have FOG back please? FOG just needs a way to deploy individual packages via the fog service and it will be complete
-
Any news on a release on .33, I am looking to upgrade from .28 but I don’t want to clean install to .32 and then have to upgrade to .33. I would much rather just go straight to .33
-
This post is deleted! -
Kernel 3.2.4 not supported EXT4 in LVM, i not possibled clone my computer with centos 6.1
-
This post is deleted! -
[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]
Sorry about the delayed reply. I do not join the domain on my image at any time until after deployment. That way it gets a new unique machine SID on joining. Ive not had any issues with group policy this way and hence havent bothered with sysprep.
-
[quote=“MikeyMike, post: 2252, member: 493”]Sorry about the delayed reply. I do not join the domain on my image at any time until after deployment. That way it gets a new unique machine SID on joining. Ive not had any issues with group policy this way and hence havent bothered with sysprep.[/quote]
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.
-
Incorrect. I use KMS both for Windows 7 and Office 2010 and I do not have any problems with it. My network is over 250 machines from HP, Dell, Acer and Ipex. I have been using Fog and Windows 7 since January 2011 using 4 different types of base images and have not yet used sysprep. After connecting to domain I run a batch file that points the client to the kms server and authenticates and it works fine.
Sysprep is definately not a must on windows 7 domain machines as long as you have never connected the image to the domain.
[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]
-
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]