[quote=“buckITall, post: 1521, member: 101”]
As for the 1st question…looks like it might not work since all HD are different sizes as well. That’s ok it shouldn’t take too long to create images…(job security) ;)[/quote]
Yeah if i have different size drives, I use the smallest drive use all of the space. Then on the bigger drives set it up exactly like the smaller drive, leaving the extra space unallocated
But it sucks because you loose that extra space on the bigger drives.
I would say try to upgrade to .32 prior to .33. There might be a good amount of changes in the .33 code which could cause complications. However, I have my personal FOG server at home, .32, ready to be upgraded. And I have our backup FOG server at work, .32, ready to be upgraded to .33. So once that update comes out, i’ll be testing away.
You could probably make a script or something, you could run in the PXE boot menu, that will just look at the ip address that computer got, send it to fog and have fog automatically remove it from the last group and add it to the new group that is assigned to the IP range. Then send a re image task using the image assigned to the new group to the computer.
I am just talking out loud here, I really don’t know much about how the programing works in fog, I am more of a network guy.
Well I got FOG .32 installed and configured, went with 10.4 LTS and 1) I was amazed at how stupid-simple the installation was. 2) love the dashboard interface.
Now I just need to get our network guy to get the pxe boot options straightened out on our DHCP server and I’ll be ready to start messing with this more in-depth. Essentially, it looks like he set the IP phone settings via server options which set them globally, but if I can get him to limit that to just the scope of IP phones, then my stuff shouldn’t be a problem for the PCs. I just don’t know at this point if there’s a specific reason he did it globally. Doesn’t seem like it should need to be. Even caused problems earlier in the year when some of our network printers stopped working (had to turn off bootp in their settings menu to get them to pull valid IPs)
Thanks for the support thusfar, if things continue to progress, I’m sure you’ll be seeing me around the forum more as I get settled in.
On the wiki there’s info how you can add mulitple servers for load balancing but what I have done is added little more RAM to my workstation to improve performance and I have imaged about 7 computers at a time and haven’t had problems. I am not sure why you are using such a powerfull system when I have FOG on a quad core HP5800 workstation with 4gb of ram and haven’t had any problems. I have a 1tb drive as local sotrage and when I need to backup, I copy them to our extrnal USB drive that goes offsite. No performance downgrade whatsoever. Still deploys image at a gigabit speed.
You can deploy to multiple workstation and what you do is create a txt file with the MAC addresses, then upload to fog. The MAC addresses will be in the FOG database then you create a group if you want and deploy.
Or you can go thourgh the fog webinterface, register each workstation and then put them in a group and deploy without having to create the txt file.
I did not install DHCP service on the FOG server and correctly pointed to the DHCP server on a different subnet. The firewalls, ufw and SELinux are both off, I’m out of ideas. Now learning how to use and read wireshark to help understand where the file is getting blocked. Not looking forward to re-installing again…even thou it was pretty easy.
If anyone has ideas or guess that would be great, otherwise I’ll post any findings if I find them.
I posted this “patch” for Ubuntu servers a while back and i’ve used it multiple times without any problems. Maybe you want to check the code in there to see if something isn’t quite right in the code that you have.
Given the information that you have provided, there are some good things and some bad. FOG shouldn’t have any problem imaging the Dell/HP computers. I am unsure about the MPC/OmniTech systems though. However, as long as they are 2000/XP/Vista/7 or Linux, they shouldn’t be a problem. The issue that you will run into are the Apple computers. FOG natively can’t image Apple computers, but there is a work around. I know this works as we currently have this implemented on our system, you can follow the directions from here, [url]http://www.fogproject.org/wiki/index.php?title=How_to_get_Macintosh’s_Netboot_working_with_your_FOG_server[/url], to be able to image Apple computers. The long and short of that site is that you need to have a working DeployStudio server setup on a Mac server, and then FOG will point to that server for the images.
I’ve never tried imaging a computer that is a dual boot, so someone else might have to chime in on that. I do know that FOG supports multiple partitions, but it might be possible to copy the drives using the “Raw Image” function which copies the drive on a “sector to sector”. Also, given that you have several computer labs, you should be able to take advantage of multicasting though FOG, if you’re networking gear supports it.
At the end of step 5 when you pick what you want installed, I just did a ctrl+f (or edit find) and searched for vmware, and checked “VMware PVSCSI driver support”. then saved it then went on to setup 6 in the instructions