Fog_0.32 on Ubuntu 12.04
-
[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.
-
I am curious to try it and see if it does what you say it will. In the past we had issuses as one machine has an AMD processor and the other has an intel processor, but we were also not using fog_0.32 either. Our lab is not part of a domain so no need to do that as of yet, that is on my list of things I would like to do.
I played around in VMware player today and managed to figure out the fog services. I now have my (virtual) setup here at home renaming hosts.
-
[quote=“chad-bisd, post: 4226, member: 18”]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.[/quote]
I went in and built a Virtual machine today to do some testing, I built a windows 7 VM in VMware player. I installed a AV on it and ran about 100 updates on it.
I thought I would follow the no need to sysprep as fog_0.32 would handle that. I fired up half of the lab as it gave me a variation of 7 Optiplex 740’s, 6 that run a dual monitor setup and one that runs a single monitor setup, and 5 Optiplex 330’s.
The Optiplex 330’s imaged just fine but the 740’s were an epic fail. The 330’s all imaged and renamed just fine though. I will play around with some variations of some images I have from my final image build process and see if I can find a combination that will work for both machines. -
One big different I have is that each model of computer we have has a complete and separate image for it. Like we have a lab of 42 computers, all identical hardware. They have 1 image. We have 120 teacher laptops, all identical hardware, they have 1 image.
I think I have about 11 different images. I have not ventured into the hardware independent image yet because each image usually has it’s own hardware and its own software requirements.
Sysprep has not been needed for me to image because I am not trying to clear out all the hardware info from windows before I make the image.
-
I am searching for a way to do unattended OS installs on a variety of hardware. Two of my labs have all identical equipment, but the one that has the biggest image has 2 differnt hardware platforms. Windows 7 is very good at having the proper drivers for most computers on the initial install. My problem is, my FOG servers are all hand me downs from the IT department with limited hard drive space. I have a 1TB external drive and will have to check and see if my old poweredge 1550 will even support this big of a drive, and possibly use it for image storage. I don’t think I can even fit 2 images on my server as the full image ends up at around 50GB. I guess I better start looking into ways to add storage to my old beater server.
-
Don’t know if this will help you I use one image at my college for all the different computers we have(running Windoiws 7). Before I sysprep the machine I run a utility call PnPUtil.exe this lets me add all the drivers for the different computers in the OS so USB3, NIC, Video, Accelometer, etc are loaded so when the computer restarts it has all the drivers it needs for that particular computer. My unattend file is basically to register windows and MS Office programs. FOG does the rest.
-
[quote=“Darrell Lanson, post: 4315, member: 1392”]Don’t know if this will help you I use one image at my college for all the different computers we have(running Windoiws 7). Before I sysprep the machine I run a utility call PnPUtil.exe this lets me add all the drivers for the different computers in the OS so USB3, NIC, Video, Accelometer, etc are loaded so when the computer restarts it has all the drivers it needs for that particular computer. My unattend file is basically to register windows and MS Office programs. FOG does the rest.[/quote]
I will look into this, thank you for giving me the info. I was wondering if I loaded windows onto one platform then use sysprep and pushed that image to the other platform if it would still retain the drivers from the first install. I was planning on testing my theory on Tuesday and will look into the PnPUtility.exe, as long as its free the college will pay for it.
The other thing I am running into is, if I use an individual image for my computers, they do not shut down after they have been imaged or when I upload an image. I think I may have to test out a few more kernels. -
When using the PnpUtil I found that if you use just -a switch it wouldnt work I had to use -a and -i Add and Install you just point it to the inf driver file and it will add it to C:\Windows\System32\DriverStore that way one image should work on any computer We have laptops and desktops and there all working off of one image about 6 different models and haven’t had a problem yet.
