Fog_0.32 on Ubuntu 12.04
-
be sure to read this tutorial also [url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]
in terms of the kernel issue, you can update the kernel through the FOG Web Interface. Go to the ‘Other Information’ page and on the right select Kernel Updates.
try 3.3.3 core, also try the one i posted above 3.4 core (by copying it to tftpboot/fog/kernel and name it: bzImage )
On the Host Management page leave the Host Kernel section blank and it will default to whatever kernel is bzImage
-
Thank you for the link to the new kernel. I have been reading everything I can about the 0.32 version of fog and had seen the link to the 3.4 kernel. I will try it when I head back to work on Tuesday.
On the Host Management page, where you can enter a Host Kernel, can I just add a kernel name in that window if I have to use multiple kernels for the wide variety of machines I may be using? -
nope, you need to add it like this… Host Kernel: fog/kernel/<name_of_kernel>
all those with blank fields will default to the kernel you have set as bzImageNote: In the screenshot below the kernel is called acer-aspire
[IMG]http://community.spiceworks.com/images/how_to_steps/0000/6034/hostview.png[/IMG]
check links
[url]http://community.spiceworks.com/how_to/show/2338[/url][url]http://fogproject.org/forum/threads/deployment-freezing.356/#post-1506[/url]
-
Thanks again, so absolute pathname is required for my extra kernels to be found.
You have been most helpful:)
-
yes full pathname is required for extra kernels,
your welcome, please like my comments if you find them helpful
-
also i see that you had trouble with wake-on-lan
In FOG Web UI go to the OTHER INFORMATION page, on the right hand side go to FOG SETTINGS, then scroll down to General Settings (about 2/3 of the way down) under this you will then see some FOG_WOL settings,
check that FOG_WOL_HOST is set to the static IP that you gave your FOG Server.
check that FOG_WOL_Interface is set to the network interface you are using. Usually eth0
-
have you had any issues with memory, it seems like I have a memory leak! when we do a group task it goes from like 172 m of ram to like 3gb in a matter of minutes! whats wrong! then the task just drops and all connections to the server are lost. should I just backup fog and start fresh with ubuntu 10.04?
thanks -
[quote=“jmwalton, post: 3877, member: 697”]have you had any issues with memory, it seems like I have a memory leak! when we do a group task it goes from like 172 m of ram to like 3gb in a matter of minutes! whats wrong! then the task just drops and all connections to the server are lost. should I just backup fog and start fresh with ubuntu 10.04?
thanks[/quote]
I havent got a chance to try any imaging other than one Master Image system sitting on the tech bench. I will be imaging roughly 50 systems around the end of July, but I may use our old fog_0.29 to do it untill im sure this new version is working properly. I will try to keep you posted of my progress. -
Thank you Falko, I was trying to use a different (per host) kernel last week and was scratching my head not realising that a full path to the new kernel was required… appreciated
-
[quote=“Robin Commander, post: 3879, member: 64”]Thank you Falko, I was trying to use a different (per host) kernel last week and was scratching my head not realising that a full path to the new kernel was required… appreciated :-)[/quote]
No worries, glad you got it working -
[quote=“jmwalton, post: 3877, member: 697”]have you had any issues with memory, it seems like I have a memory leak! when we do a group task it goes from like 172 m of ram to like 3gb in a matter of minutes! whats wrong! then the task just drops and all connections to the server are lost. should I just backup fog and start fresh with ubuntu 10.04?
thanks[/quote]Is your fog server fully updated?
-
[quote=“falko, post: 3830, member: 48”]give this kernel a shot its 3.4 core, provided by astrouga
[URL=‘http://www.filedropper.com/bzimage34’]http://www.filedropper.com/bzimage34[/quote[/URL]]
The 3.4 core kernel was not the secret to PXE booting my Dell Optiplex 330’s and 740’s, I managed to get both machines to boot using the 2.6.33.3 PS kernel.[/quote]
-
Would I need to create an unattended install file to name a computer after pushing a syspreped image? I have found some blurbs about FOG service, and even found a download for it, but not a whole lot of information. I have a image that has 3 user accounts that is roughly a 60GB system image. Right now I can image machines, create a dummy user name and name the PC what it needs to be and then go delete the dummy account, and my computer is almost ready. We run DeepFreeze so after I push the thawed image the machine needs to be booted in frozen mode, then my install is complete. I have managed to narrow it down to those final steps, but would like to be able to clean them all up so I can just setup a CRON job and come back and turn the FOG server off and be done.
-
From what I have had a chance to read this week, it looks like not many people are having any luck with renaming a syspreped windows machine without an answer file being used.
If you have any information about this I would love to hear about it.
Also if anyone uses faronics deepfreeze on their machines I would be interested in any information you might have on ways to be able to make changes to an image that was frozen when it was taken.
-
i rename by machines using FOG to rename them as per the name i register them with
-
Yes, don’t try to rename the machine with sysprep, just let the Fog client do the rename and join to the domain if you need. I tried to use sysprep for domain joines, but it joined the domain before the rename and things got stupid real fast.
-
I am working on my presentation for the IT department, and I thought I would start off the show by deploying an image using the Computer Science departments ipod to initiate the deployment. In order for the image to deploy rapidly I will be creating a very small image, probably Windows 7 Pro 64 bit with security essentials. In the lab where I will be doing the presentation there are 14 of one type of computer and 11 of another type. In order to deploy just one image the master image is an OOBE syspreped image.
What I would like to have happen for my presentation is the machines to be ready for me to reboot them in a frozen state. For that to happen the computers will need to be named, as after the sysprep the machine no longer has one. I have not had a chance to play with version 0.32 out in the lab yet other than to image 1 or 2 computers to verify I have the correct version of kernel to do the job.
I have been holding off on a large test deployment until the IT department gets our labs moved to a new VLAN. I am also waiting to see if any new computers arrive this month.
I am just a little lost as to how computers are named in a deployment of an image by FOG. I know that by roaming around in the GUI I have found checkboxs that say renaming is enabled. I was just not sure what I need to do on my end to make it happen.
Thanks for all the support
-
Globally enable the host name changer module in the Fog web UI. Install the Fog Client on a computer before you upload the image. Make sure when you install the client you leave the host name changer enabled.
I think in 0.32, Fog changes a registry setting as one of the last steps before completing the image deployment if the host name changer option is enabled and you have fast rename enabled (other Settings - fog settings - general settings)
-
Thanks Chad that pointed me in the right direction. I will fire up a few computers in the lab and try to see if I have it all figured out tomorrow.
In the past we kept 2 master image machines and simply pushed 2, non-syspreped, images to the different computers. then we had to go in and manually rename the computers and reboot them for the changes to take effect then we could do our deepfreeze setup and be ready for class.
We, to my knowledge, have never used fog prep either. -
I used sysprep on my Windows 7 laptops that will be frozen with DeepFreeze, but only so I could “copyprofile” some settings over from the administrator profile to the default profile. I did the windows setup, hit the hotkeys to reboot into audit mode, and load/setup the computer how I want. Then I sysprep + copyprofile to overwrite the default profile with my custom settings for background and some app options. Reboot after sysprep and finish installing.
Basically, I don’t sysprep right before uploading the image. With Windows 7 and Fog 0.32, it’s not necessary; Fog now takes care of the FogPrep steps to avoid boot up problems. You only have to sysprep to achieve a specific goal only attainable through sysprep. Booting a clean windows 7 image does not require sysprep/fogprep.
For my labs, which are currently running Windows XP, I do not sysprep. I load 1 machine up with all the software I need, join it to the domain and get the policies applied and all the updates ( have to join to domain to get windows update to work ). Once it’s complete, I remove it from the domain and shutdown. I register the device if not already registered and I schedule an upload task. Once it’s complete, I can use the image to push to the rest of the lab and Fog will rename each client based on the name it was registered with. If I have Active Directory integration enabled, it will join them back to the domain for me after they are renamed.
Once they show they are joined to the domain, I freeze them using deep freeze console or manually logging into each one if I don’t have access to the console.
