foguserguide - fogproject wiki

From FOGProject Wiki

A guide to deployment, management, And concept overview For FOG.

Based on a document by: Thomas J. Munn CISSP

1 Introduction1.1 Preface1.2 Background on FOG1.3 Fundamental Concepts

1.3.1 Unicast1.3.2 Multicast1.3.3 Torrent-Cast

2 Installing FOG2.1 Requirements2.2 Installation on different distributions of Linux

3 Network Integration3.1 Basic Network Setup3.2 Advanced Network Setup

3.2.1 Integrating FOG Server with Existing Network Systems in non intrusive mode using MACfiltration3.2.2 Integrating FOG server into an existing network in non intrusive mode using ProxyDHCP3.2.3 Wake On Lan (WOL)3.2.4 Multicast/UDPCast3.2.5 Full Listing of Ports used by FOG server and client

4 Getting Started4.1 Quick Start - Basic Tasks4.2 Tips

5 Preparing a HOST for Cloning6 FOG Benchmarks

6.1 Internal Benchmarks7 Managing FOG

7.1 The Main Managing FOG Document8 FOG Tasks

8.1 Delayed Tasks, or Scheduling Tasks in the future8.2 Adding Printers to FOG

9 The FOG Client Service9.1 Installing the FOG Client9.2 Advanced Description of FOG Services9.3 Firewall Exceptions9.4 Updating the FOG Client9.5 The FOG Tray9.6 Troubleshooting the FOG Client

10 Snap-ins11 FOG Plugins

FOGUserGuide - FOGProject Wiki http://www.fogproject.org/wiki/index.php?title=FOGUserGuide

1 of 15 1/14/2015 10:35 AM

11.1 LDAP Plugin11.2 Location Plugin11.3 Access Control Plugin11.4 Capone Plugin11.5 WOL Broadcast Plugin11.6 Example Plugin

12 FOG Server Maintenance13 Advanced Installations

13.1 Separate TFTP and DHCP Server13.2 Additional TFTP / DHCP Server on separate subnet13.3 Separate NFS Server13.4 Change NFS location

14 Upgrading to Trunk15 Other Advanced Topics16 Troubleshooting

16.1 Troubleshooting Installation and Configuration Issues17 Appendix C: Alternative Resources18 About the Developers and other influences

18.1 FOG Project Leads (Creators and Developers too)18.1.1 Chuck Syperski18.1.2 Jian Zhang

18.2 Community Managers18.2.1 Chad-bsid18.2.2 falko18.2.3 andyroo5418.2.4 BryceZ18.2.5 Kevin

18.3 FOG Developers18.3.1 Jaymes Driver18.3.2 Tom Elliott18.3.3 Fernando Gietz18.3.4 Peter Gilchrist18.3.5 Greg Grammon18.3.6 Curtis Larsen18.3.7 Gilles Pietri18.3.8 Lee Rowlett18.3.9 Joe Schmitt18.3.10 John Shaw18.3.11 Travis Vlaminck18.3.12 Dan Younkin

18.4 Notorious Beta Testers18.4.1 Andy Abplanalp18.4.2 Ian Allison18.4.3 Lane Garland18.4.4 Greg Plamondon

Preface

This document is intended to be modified by FOG users, in fact it is based on a document created by a FOG user. If you feel


2 of 15 1/14/2015 10:35 AM

something could be said better or put more clearly, it is encouraged that you make changes to this document. We just askthat you keep it constructive and in good taste. In order to edit the wiki you are now required to create an account, asspamming of the forum has gotten pretty bad recently.

What is FOG?FOG is a Linux-based, free and open source computer imaging solution for Windows XP, Windows Vista, Windows 7,Windows 8, and Linux (limited) that ties together a few open-source tools with a php-based web interface. FOGdoesn't use any boot disks, or CDs; everything is done via TFTP and PXE. Your PC boots via PXE and automaticallydownloads a small Linux client. From there you can select many activities on the PC, including imaging the harddrive. Also with FOG many network drivers are built into the Linux client's kernel, so you don't really need to worryabout nic drivers (unless there isn't kernel support for it yet). FOG also supports putting an image that came from acomputer with a 80GB partition onto a machine with a 40GB hard drive as long as the data is less than 40GB. FOGsupports multi-casting, meaning that you can image many PCs from the same stream. So it should be as fast whetheryou are imaging 1 PC or 20 PCs.

How should FOG be implemented?FOG is best implemented on a dedicated server, any spare machine you have. We recommend that you have sufficienthard drive space as each image you make is usually between 5 and 10 GB. Using a RAID array allows imagingmultiple computers simultaneously without much performance degradation. A gigabit NIC is recommended. Forfaster image compression and decompression, provide as much processor and RAM as you can make available.

What features are included with FOG?FOG is more than just an imaging solution, FOG has grown into an imaging/cloning and network managementsolution. FOG now performs tasks like installing and managing printers, tracking user access to computers, installingapplications remotely via snap-ins, automatic user log offs and computer shutdown on idle timeouts. If a computer isbadly infected with a virus or malware, you can boot FOG in AV mode and have it remove the viruses. You can wipeyour disks, destroying all information that was on them, restore deleted files, or scan the disk for bad blocks.

How much does FOG cost?FOG is an Open Source project and licensed under the GPL which means that you are free to use FOG on as manycomputers as you like for free. This also means that if you want to make any changes to the source code you are freeto do so. The creators of FOG make no profits from this project with the exception of donations. FOG comes withabsolutely NO WARRANTY and the creators of FOG are in NO WAY RESPONSIBLE FOR ANY DAMAGE ORLOSS CAUSED BY FOG! Please see the license file included with the FOG release for more information. With thatbeing said we attempt to do a very good job of supporting our users, in fact it is one of the goals of FOG to have bettersupport than most commercial products. All support requests should be placed through the FOG's forum which islocated at: http://fogproject.org/forum/ Thanks for supporting open source software and enjoy!

Background on FOG

Why FOG?Working in an educational environment our organization's techs very often re-imaged computers in their day to dayactivities. For a long time we used a commercial product that in many ways didn't meet our needs. It wasn't webbased, and you needed to create driver disks, floppys or USB drives. Other things were very difficult, such assearching for a host by MAC address and the product was expensive, even with an educational discount. So we startedto investigate ways in which we could do things better, and as our organization struggled to make a commercialproduct work better by trying to pxe boot dos, and testing it in Windows PE, we, the FOG Team started to build linuxbased solution on our own time. We finally got a working version and decided to release it as open source since weuse many other open source products, and figured we should give back to the community.

Fundamental Concepts


3 of 15 1/14/2015 10:35 AM

This section provides some basic concepts that the FOG Project uses.

Unicast

Accessible from Host Management --> Select Host --> Basic TasksAccessible from Group Management --> Select Group --> Basic TasksAccessible from Fog iPXE MenuThis occurs when scheduling a "Download" task, "Quick Image", or during "Full Registration" the user selects imageafter registration. The server (or storage node) will directly send packets (the image) to that Host's MAC address.(aka.TCP) This is excellent for directing network traffic. This can be performed under Groups running multiple unicasts tomultiple hosts. However, all the hosts will not finish at exactly the same time.Since unicast does not rely or communicate with others in a group it is unaffected by "hung up" host

Multicast

Accessible from Group Management --> Select Group --> Basic TasksAccessible Image Management --> Multicast ImageThis occurs when scheduling a "Multi-Cast" task from Groups. The server (or storage node) will wait for all Hostcomputers to be network booted. Once all hosts have registered for the task the packets will be sent out out to theentire network.(aka. UDP) Packets are sent and received exactly the same. Image may not complete exactly the sametimeDown side to this is if one host gets hung up then the entire process is stopped till that host catches upMulticasting

Torrent-Cast

Currently not working.Accessible from Host Management --> Select Host --> Basic Tasks --> AdvancedAccessible from Group Management --> Select Group --> Basic Tasks --> AdvancedThe image is broken down into chunks and indexed to create a torrent file.The server (or storage node) beings creates the torrent and starts seeding. The hosts request the torrent and startdownloading chunks for the torrent. Once a chunk is received then the hosts will seed that chunk to other hosts. Oncetorrent is done downloading it will start imaging. Then the partition is rewritten to accomidate the size needed todownload the files originally.If one host gets "hung up" the other host are not affected, but marginal time and speed are lost.

PXE Network Bootstrap loadingWhat is iPXE and the difference between the files? Check out the iPXE page.</li></UL>

FOG is a typical LAMP (http://en.wikipedia.org/wiki/LAMP_%28software_bundle%29) software bundle, so the main serveris a Linux box. The rest of the components: Apache, MySQL, PHP, and several other services, are automaticallydownloaded and installed by the FOG installation script.

Requirements

This listing is for informational purposes only, as the required components will be automatically downloaded and installedby the FOG installation script.

PHP 5.3.0+MySql 5+Apache 2+


4 of 15 1/14/2015 10:35 AM

The LAMP setup can also be easily adjusted for a "WAMP (Windows Apache MySQL PHP) system" though will require abit more knowledge of what packages to use and how to integrate with the FOG system.

Installation on different distributions of Linux

Click below for step-by-step guides written for your favorite flavor of Linux:

Basic Network Setup

The FOG setup script asks several questions which might not be obvious. These sections describe only the most genericsettings.

Isolated NetworkThe easiest method to image machines and get started using FOG is on a small, isolated network. The FOG setupprogram will configure all the necessary services for you completely automatically. This section covers only thosebasic steps.See FOG on an Isolated Network

Integrating FOG Server with Existing Network SystemsSlightly more complicated is the task of integrating FOG into your existing network infrastructure. This sectionattempts to describe the steps to link FOG with a fairly generic enterprise system.See Integrating FOG into an Existing Network

Advanced Network Setup

Integrating FOG Server with Existing Network Systems in non intrusive mode using MAC filtration

This methods allows to use Fog in existing network without the need of controlling existing DHCP server. Requires you toinput the MAC address of FOG clients. See Integrating FOG into an Existing Network in non intrusive mode

Integrating FOG server into an existing network in non intrusive mode using ProxyDHCP

This methods allows to use Fog in existing network without the need of controlling existing DHCP server. Does NOTrequired you to input the MAC addresses of FOG clients. See Setting up ProxyDHCP.

Wake On Lan (WOL)

Cisco WOL - Layer 3ProCurve WOL

Multicast/UDPCast

Cisco Multicast - Layer 3

HP Multicast - Layer 2&3

Full Listing of Ports used by FOG server and client

FTP – tcp 20,21


5 of 15 1/14/2015 10:35 AM

SSH – tcp 22TFTP – udp 69HTTP(s) – tcp 80,443Portmap – tcp/udp 111NFS – tcp/udp 2049Transfer ports – tcp/udp 1024 – 65535As found at: http://fogproject.org/forum/threads/firewall-config.27/

Quick Start - Basic Tasks

So you have a FOG server installed and setup, now what do you do? Below are a few common "Getting Started" items.

Booting into FOG and Uploading your first Image1. Deploying your Image a single client2. Deploying your Image a group of clients3.

Tips

FOG requires that all hosts be entered in the FOG Database for imaging. The most important part is getting the MACaddress of the host right. FOG uses the MAC for targeting image installs and acquires. Using the wrong MAC couldresult in unpredictable results, including the complete erasure of the wrong pc! The IP address isn’t that important,and the ‘name’ field is more for the user. Mac address format is 00:12:3F:C4:57:0C . Using dashes, spaces, or noitems at all will result in the GUI not accepting the host.

1.

After hosts are entered, it is wise to group them together by function, hardware, or common image. The image will beshared among all members of a particular group. This occurs within the ‘hosts’ screen, and NOT on the groups screen.This is a little confusing, so it helps to think of the ‘groups’ screen as a task generator, rather than controlling groupmemberships.

2.

For importing hosts in a .csv file follow the format below: 1 line per host:

"00:c0:4f:18:62:63","Hostname","1.1.1.1","Your description","XP/Vista","Image filename to use"

3.

Hosts are then configured to boot via PXE boot by going into the BIOS. Make sure PXE boot is the FIRST option,NOT the hard disk, or things won’t work.

4.

Configure your ‘master’ pc for the first image. Probably a good idea to run ‘sysprep (http://support.microsoft.com/kb/302577) ’ prior to imaging, but not necessary. Sysprep will make your imaging life easier, if hardware is different,etc. See Microsoft.com for more details on using sysprep.

5.

Key Term: Host --> The computer that will be registered to FOG and imaged(upload/download). Client usually refersto the Client service later described in this guide.

FOG's strength can be better harnessed if some time and work is put into preparing a master image that fits the needs of yourenvironment.This section covers Host preparation steps that will save you time and headaches like:

Setting a Default User ProfileInstalling Windows UpdatesPre-Installing the FOG service, etc.

It also covers more advanced ideas that are guaranteed to cause headaches, like:


6 of 15 1/14/2015 10:35 AM

Sysprep, Hardware-Independent Images (HAL), and Driver integration.

Read more about Host Setup

Internal Benchmarks

The FOG web interface is your primary management console. It is very well-documented in the pages linked below:

The Main Managing FOG Document

The link above opens the Main Managing FOG document and has a Table of Contents of its own.Subcategories within the Managing Fog section include the following sections:

Understanding the FOG DashboardProvides an overview of the GUI and explains the symbols used on the Menu Bar.Managing HostsThis section covers management tasks such as: Adding a new host, Managing Hosts, Host Status, and Creating HostGroups.Managing Groups of HostsThis section provides an Overview of sorting hosts into useful Groups, and provides instruction on Managing Groups.Defining and Managing ImagesDefines types of images: Single Partition | Multiple Partition - Single Disk | Multiple Partition - All Disks | RawImageAlso describes Creating, Modifying Image Objects, and Adding Images to Existing Objects.Storage Management - adding additional Storage NodesThis section introduces the concept of Storage Nodes, which provide scalability to FOG with the ability to "share theload of computers being imaged."Also covered are Adding Storage Nodes, Monitoring Image Replication between nodes, and Understanding the role ofthe "Master Node" in a group.In addition, this section details the necessary steps to include PXE and TFTP Services for a node located on a remotenetwork segment.Defining types of Administrative FOG UsersThe difference between a regular FOG user and a Mobile userAlso covered are Creating and Modifying FOG user accounts

This is a major section of FOG Management because all day-to-day client management is initiated within the FOG Taskssection.The Overview Section provides a quick list of tasks available within FOG.General Tasks - Basic Imaging Tasks:

Uploading an image (includes video tutorial)Deploying an imageMulticasting

Advanced Tasks - Describes tasks other than imaging:

Debug


7 of 15 1/14/2015 10:35 AM

Upload - Unicast (Debug)Send - Unicast (Debug)Send - Unicast (Without Snapins)Deploy All SnapinsDeploy Single SnapinMemory TestWake UpFast WipeNormal WipeFull WipeDisk Surface TestFile RecoveryVirus ScanHardware InventoryDonateTorrent-Cast

Delayed Tasks, or Scheduling Tasks in the future

Describes advanced settings available for scheduling tasks including Shutdown after Execution, Single Task scheduling, andsetting a CRON-Style Task.

Adding Printers to FOG

How to add printers to FOG. This allows the FOG Service to manage printers on FOG Clients

A service that runs on client computers allowing FOG to better manage them. Provides AD Integration, the ability to changea Hostname, Green Power management, Snap-in installation, User tracking, Printer Management, and more. See theOverview for a more complete list.The FOG client can be partially or fully-enabled by modifying the ini file.

Installing the FOG Client

A typical client installation, Silent installation, and a video tutorial.

Advanced Description of FOG Services

More detail on:

Auto Log OutHostname ChangerHost RegisterTask RebootDirectory CleanerDisplay ManagerGreen FOGSnapin ClientUser TrackerUser CleanupPrinter ManagerClient Updater


8 of 15 1/14/2015 10:35 AM

Firewall Exceptions

Run these in Administrative Command Prompt(cmd) on the host to allow communication between the FOG ClientService installed on the Host and the FOG ServerPast setups suggested disabling the firewall and is less secure

netsh advfirewall firewall add rule name="Fog Client" dir=in action=allow program="C:\Program Files\FOG\FOGService.exe" netsh advfirewall firewall add rule name="Fog Service" dir=in action=allow program="C:\Program Files\FOG\FOGServiceConfig netsh advfirewall firewall add rule name="Fog Tray" dir=in action=allow program="C:\Program Files\FOG\FOGTray.exe"

Updating the FOG Client

How to update the FOG client.

The FOG Tray

Describes the Windows application that runs in the taskbar

Troubleshooting the FOG Client

Log file location

A FOG Snap-in is anything that can be run on a Windows client. This can be just about anything, including: installingapplications like Firefox or Microsoft Office, adding an icon or shortcut to the desktop, or tweaking a registry key.This section covers Creating a Snap-in, adjusting the FOG server to handle snap-ins larger than 2MB, Uploading theSnap-in into the FOG system, and Linking the Snap-in to hosts.

Plugins enhance FOG's functionality. See Plugins to activate and manage plugins.

LDAP Plugin

Allows you to link with a LDAP server to add an user validationYou can add mulitple LDAP serversYou can config the DN base and the port of the LDAP ServerIf FOG can not connect with the LDAP Server, FOG tries to do a local validationIf the user does not exist, FOG create one with the mobile profile

Location Plugin

Allows you to direct hosts at separate locations and manage through a centralized serverHosts will be imaged from their location setup, rather than trying to pull from a random node/server across,potentially, WAN linksSame works for "Tftp" in that it will direct the host to get it's kernel and init from it's related locationCan also be used to direct the host to download it's snapins from the relevant location

Access Control Plugin

NOT Currently ready


9 of 15 1/14/2015 10:35 AM

To give a layer of security and control over the task and imaging processes as well as limit the GUI items from"designated" controlsFor Example: IT vs. Regular User

Capone Plugin

Ideally for retail markets and computer shopsThe Capone plugin allows FOG to recognize similar hardware platforms and push your specified image to them withminimal (or no) interactionIn FOG terms a "Quick Image" without any registrationObsolete As of FOG v1.3.0-r2651 the fog user can now add Quick Image to the Fog iPXE Menu(For All Hosts) andthen select the exact image desired without having to do any registration. BUT intervention is still required to startimaging.

WOL Broadcast Plugin

Allowing the Fog user to specify different broadcast address on your networkWOL will use those set values to send the WOL Packets to the broadcast addresses, rather than staying only on layer 2WOL packets operate at the layer 2 of a network meaning that it can only reach it's "Subnet"WOL Broadcast directly tells a packet to send to other broadcast addresses so that it network passes on the traffic

Example Plugin

If you would like to create your own plugins here is a template to follow.

Backing up FOGRestoring FOG from BackupUpgrading the FOG Server

Separate TFTP and DHCP Server

In this setup, the TFTP server and the DHCP server are hosted on a separate server. The TFTP server holds the PXE bootfiles including the Linux Kernel, boot file system image, and pxe config files. The DHCP server is the server that assigns theclients with IP addresses and network connection information.

Click here for detailed steps:Separate TFTP and DHCP Server

Additional TFTP / DHCP Server on separate subnet

This setup allows FOG to manage systems at a remote network location by installing the necessary services to allow clientsto PXE boot to a Storage Node:Including multiple PXE / TFTP servers

This extends the work done in the above article, Including multiple PXE / TFTP servers, and extends it a bit to allow forFOG nodes to be used in various locations that pull from a central server.Using remote FOG nodes for distributed deployment


10 of 15 1/14/2015 10:35 AM

Separate NFS Server

Edit the storage node definition with the IP address of your NFS server and set the image location to the path on the nfsserver. Make sure it has a file called .mntcheck in the root of the share, a directory called dev and a .mntcheck file in the devfolder.

if you want to mount it on the fog server too, follow these steps:-

mv /images /imagesoldmkdir /imagesedit /etc/fstab

For example if your server name is mynfsserver and the share on it is called fogimages

mynfsserver:/fogimages /images nfs defaults 0 0

then type

mount -a

KNOWN ISSUE You will get an error "Ftp connection to storage server has failed" at the end of uploading images though.You will have to manually rename and move the file from the dev directory to the directory below.

If your NFS server supports ftp as well, enable ftp on it too with the username and password specified in the storage serversettings and this message will go away.

Hopefully someone will re-write POST_Stage2.php to change this at some point as if you already have the NFS sharemounted why do we do this bit with ftp?

You may also get an infinite loop of the following message:-

"Unable to find a valid task ID based on the clients mac address of: <mac address>".

if you add an @ sign before the ftp commands it appears to have fixed the issue.

so line 133 of /var/www/fog/service/Post_Stage2.php would look like this

if (@ftp_rename ( $ftp, $src, $dest ) || @ftp_rename ( $ftp, $srcdd, $dest ))

Change NFS location

This is not about a seperate NFS server in general, but about how to change the local storage directory and export itcorrectly.

See Change NFS location for more.

Trunk installs are almost always buggy. This is bleeding edge and if you wish to update to trunk be prepared to updateat least once a week or even once a day. At all times developers are making changes to correct problemsUpgrade_to_trunk


11 of 15 1/14/2015 10:35 AM

Building a Custom KernelCreating Custom FOG Service ModulesModifying the Init ImageTranslating FOGFog TweaksBypass Host RegistrationBuilding undionly.kpxeChainloading PXE to iPXE using pxelinux.0Auto driver Install

This section is intended to bring together the most common issues from the forums (http://www.fogproject.org/forum) .

Troubleshooting Installation and Configuration Issues

Knowledge BasePassword CentralTroubleshooting an image push to a clientTroubleshooting an image uploadTroubleshooting a multicastTroubleshooting Driver IssuesSpeeding up the Graphical User InterfaceBottleneck / Imaging Speed IssuesAdvanced_Boot_Menu_Configuration_optionsTroubleshooting Host Management Showing Hosts as Down

For Microsoft sysprep information, see this page: http://vernalex.com/guides/sysprep/video.shtml

FOG install HOWTO: http://www.howtoforge.com/installing-fog-computer-imaging-solution-on-fedora8

FOG sourceforge page: http://freeghost.sf.net/

Deployment Forum at Edugeek contains many Fog related threads http://www.edugeek.net/forums/o-s-deployment/

Chuck Syperski

Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and networkintegration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science inComputer Science from the University of Illinois and is half way done with his master's degree :). He specializes in Java,jsp, jsf, objective C, C, C++, C#, perl and php. You can contact Chuck Syperski directly via sourceforge as the followinglink:


12 of 15 1/14/2015 10:35 AM

http://sourceforge.net/users/microleaks/

Chuck Syperski releases other software titles through his company CWS Software LLC (http://cwssoft.com)

His username on the FOG forums is Chuck Syperski

Jian Zhang

No Content

His username on the FOG forums is Jian Zhang

Chad-bsid

No Content

falko

No Content

andyroo54

No Content

BryceZ

No Content

Kevin

No Content

Jaymes Driver

Jaymes "loves dnsmasq" Driver

Jaymes is an aspiring software engineer and Ubuntu nut. He began working on his degree at University of AdvancingTechnology in Tempe, AZ but currently works as a Technology Support Specialist for Seymour Community SchoolCorporation out of Seymour, IN. Jaymes spends his time breaking what isn't broken, and working on private projects thatdeal in html, php, and mysql. You can contact Jaymes by using the FOG forums.

His username on the FOG forums is Jaymes Driver

Tom Elliott

Senior Developer

Tom Elliott is the Senior Developer for FOG computer imaging solution. He is a technical support specialist for BurlingtonSchool District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information


13 of 15 1/14/2015 10:35 AM

Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years activeduty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email [email protected], [email protected], or on the FOG Forums.

His username on the FOG forums is Tom Elliott

Fernando Gietz

LDAP Plugin Creator

No Content

His username on the FOG forums is Fernando Geitz

Peter Gilchrist

No Content

Greg Grammon

Greg Grammon a PC Support Technician for Fort Hays State University in Hays, KS. Greg Grammon has a Bachelor ofScience in Information Networking and Telecommunications from Fort Hays State University.

His username on the FOG forums is Junkhacker.

Curtis Larsen

No Content

His username on the FOG forums is fractal13

Gilles Pietri

Gilles helps developping FOG (Web UI, and linux client code) and provides insights on how to drive the project. He isspecialized in IT administration and virtualization, and provides training and consulting for FOG through a training center inFrance (in Paris, Nantes, Lille, Lyon, Toulouse...). You can find DAWAN's training offer here: http://www.dawan.fr/formations/reseaux/deploiement/fog--deploiement-d-images-initiation-approfondissement

His username on the FOG forums is Gilou

Lee Rowlett

Location Patch Creator (Now migrated to the Location Plugin)

Lee currently works for the NHS Ambulance Service as a Senior IT Engineer. Most of his contributions to the FOG projectare related to new feature developments and help drive modular style imaging.

His username on the FOG forums is Lee Rowlett

Joe Schmitt

Lead developer of the Client.

Joe Schmitt is currently working towards a degree in Computer Engineering. You can contact him directly via email [email protected] or on the forums.


14 of 15 1/14/2015 10:35 AM

His username on the FOG forums is Jbob

John Shaw

No Content

His username on the FOG forums is jbsclm

Travis Vlaminck

Travis works for a public school district as a computer support specialist. Most of his contributions to the FOG project arerelated to feature integration and coding on the web UI.

His username on the FOG forums is BPSTravis

Dan Younkin

Dan works for a public school district in Rockwood, PA, USA as a Technology Assistant. His titles include too many tocount and if he takes a day off there are mass panics. Most of his contributions are testing new features, masstroubleshooting and confirming bugs, wiki updates, and suggesting more a simpler streamline FOG. It is his hope FOG willexpand and compete with other streamline imaging software and systems.

His username on the FOG forums is Wolfbane8653

Andy Abplanalp

No Content

His username on the FOG forums is tamatech

Ian Allison

No Content

His username on the FOG forums is ianabc

Lane Garland

No Content

His username on the FOG forums is need2

Greg Plamondon

No Content

His username on the FOG forums is Greg Plamondon

Retrieved from "http://www.fogproject.org/wiki/index.php?title=FOGUserGuide&oldid=8975"

This page was last modified on 13 January 2015, at 14:14.Content is available under Public Domain.


15 of 15 1/14/2015 10:35 AM

foguserguide - fogproject wiki

Documents