{"id":379,"date":"2010-06-04T10:11:55","date_gmt":"2010-06-04T17:11:55","guid":{"rendered":"http:\/\/wp.natsci.colostate.edu\/bioit\/?p=379"},"modified":"2020-12-07T12:31:32","modified_gmt":"2020-12-07T19:31:32","slug":"fog-server-has-arrived","status":"publish","type":"post","link":"https:\/\/cnsit.colostate.edu\/kb\/fog-server-has-arrived\/","title":{"rendered":"FOG Server Has Arrived!"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-386\" style=\"float: right;\" title=\"FOG_logo\" src=\"https:\/\/cnsit.colostate.edu\/kb\/wp-content\/uploads\/2010\/06\/FOG_logo.jpg\" alt=\"\" width=\"287\" height=\"69\" \/>So, some of you may have been aware that I was in the market for a new computer imaging and cloning solution for our computer labs, teaching wet laboratories, and special general purpose rooms.\u00a0 Overall I have just over 100 computers that need image management on a fairly routine basis.<\/p>\n<p><strong>How I was doing it<\/strong>: I was using a VERY old version of Symantec Ghost that was purchased before I started here at CSU &#8211; so in short, I was probably not using them 100% legally, AND it was a pain in the butt getting newer network cards to work and the imaging process was so crazy slow I needed relief.<\/p>\n<p><strong>The Options<\/strong>: Symantec products are always an option, but I am frugal, and really like using FOSS to save us some money &#8211; so I chose a couple of the popular ones and began to compare.\u00a0 The two were Clonezilla (<a href=\"http:\/\/clonezilla.org\/\">http:\/\/clonezilla.org<\/a>) and FOG (<a href=\"http:\/\/www.fogproject.org\">http:\/\/www.fogproject.org<\/a>).\u00a0 First off, Clonezilla and FOG both have great reviews and very loyal followers &#8211; however, I needed to look at what was going to work best in my environment, and then apply the standard subjectivity &#8211; like how pretty it looks.<\/p>\n<p>In short, I chose FOG due to the fact that it allows followup imaging tasks (software installations) and printer installations, uses a windows service to allow client-server communication to schedule tasks, and images through PXE boot so no boot media needed!\u00a0 Oh, and FOG looks much nicer and is rather intuitive when compared the the occasionally confusing Clonezilla.\u00a0 Yes, I know there are other commercial products out there &#8211; but this one is FREE!<\/p>\n<p><!--more--><\/p>\n<p><strong>My Experiences:<\/strong> I waited until May 25th to give this a try so that I could also play with the new Fedora 13 (very nice by the way).\u00a0 Once I had the fresh OS installed &#8211; and the newest FOG package installed (.29 at this time) I was ready to get started.\u00a0 First off, the installation was a breeze &#8211; the questions you needed to answer were in plain language, and not overly needy &#8211; I only strayed from the default choices as I wanted to use our existing DHCP server instead of having the FOG installer set up one for me.<\/p>\n<p><strong>After The Installation<\/strong>: After the installer completed, I was ready to go, and this pretty much meant I was done working at the FOG server console.\u00a0 So, I settled back in front of my main office workstation, and brought up the web management front end &#8211; and apart from from some very minor customizations required on the server end, I will use this exclusively for the remainder of my testing!\u00a0 The first thing I did was to create a test image and configure a test client to work with FOG &#8211; setting up the image and client in the management web front end was a breeze as long as you have the client&#8217;s hostname, IP and MAC address.\u00a0 Having this client work with FOG really only requires two items.\u00a0 One, I needed to install the FOG windows service and configure it properly (IP of the FOG server for the most part).\u00a0 Once this was set, I needed to change the boot order within BIOS to have the network card with PXE attempt the first boot.\u00a0 All set!<\/p>\n<p>On my fist attempt I ran into some NSF routing errors.\u00a0 Looking into these messages on the FOG support forums and FOG User Guide (great resources for most gotchas) I discovered that a slew of firewall ports needed opening as well as the deactivation of SELinux.\u00a0 A quick restart of the server and we were creating an image successfully!<\/p>\n<p>Image deployment was also a breeze &#8211; and I played around with scheduling through the web interface which also worked great &#8211; 5 minutes after setting the task as &#8216;forced&#8217; the machine automatically restarted, booted via PXE, and was imaging!<\/p>\n<p>One of the great things the Windows Service on the client side can handle is that automatic host name changing and Active Directory binding.\u00a0 This took some hunting and I found a solution here (Link Dead): https:\/\/sourceforge.net\/projects\/freeghost\/forums\/forum\/716419\/topic\/3469402<\/p>\n<p>I also got a &#8216;Snapin&#8217; working properly for adding registry entries (.reg file) so that a domain user automatically logs in once on boot!\u00a0 Information on that here (Link Dead): https:\/\/sourceforge.net\/projects\/freeghost\/forums\/forum\/716418\/topic\/3681306<\/p>\n<p>Aren&#8217;t those support forums great!?\u00a0 All in all I have the few things I needed to accomplish and play with more of the &#8216;bonus&#8217; items soon.\u00a0 I hope you take a look at FOG for your next deployment software change &#8211; it works and looks great!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>So, some of you may have been aware that I was in the market for a new computer imaging and cloning solution for our computer labs, teaching wet laboratories, and special general purpose rooms.\u00a0 Overall I have just over 100 computers that need image management on a fairly routine basis. How I was doing it: [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-379","post","type-post","status-publish","format-standard","hentry","category-general-cnsit"],"_links":{"self":[{"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/posts\/379","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/comments?post=379"}],"version-history":[{"count":1,"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/posts\/379\/revisions"}],"predecessor-version":[{"id":3704,"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/posts\/379\/revisions\/3704"}],"wp:attachment":[{"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/media?parent=379"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/categories?post=379"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cnsit.colostate.edu\/kb\/wp-json\/wp\/v2\/tags?post=379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}