FOG Project - User contributions [en]

FOG Client

2016-07-04T22:22:43Z

Jbob.21733:

This article applies to the new FOG Client, version 0.10+

== The Different Installers ==

The different installers are located in your FOG server's web interface. The link is always at the very bottom of every page and are even available to you if you're not logged into the fog server.

[[File:Fog client link.png]]

[[File:New FOGClient download link.png]]

'''FOGService.msi''' - Windows only, and is ideal for network deployment.

'''SmartInstaller.exe''' - This is the new default installer. It will work on all platforms.

'''Debugger.exe''' - This is not listed in the web interface but is available from github [https://github.com/FOGProject/fog-client/releases here]. Only use this when the above two are not working. This build has more detailed logs that you can use for troubleshooting or a bug report.

== Installing - Windows ==

'''Prerequisites'''
* .NET Framework version 4.0+ (Note: .NET 4 client profile will NOT work)
You can download the framework from here:

[https://www.microsoft.com/en-us/download/details.aspx?id=40779 Microsoft .NET Framework 4.5.1 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows Server 2008 SP2 Windows Server 2008 R2 SP1 and Windows Server 2012]

Windows 10 comes with a version of .Net that will work.

'''Installation'''
* May use SmartInstaller or msi. Simply download either one of them and run.
* Reboot to complete installation.

'''Limitations'''
* CUPS printers are not yet supported

== Installing - Linux ==

Installation instructions derived from [http://www.mono-project.com/docs/getting-started/install/linux/ http://www.mono-project.com/docs/getting-started/install/linux/]

'''Prerequisites'''
* Mono (latest stable build)
* xprintidle - This dependency is optional. If not installed AutoLogOut will not run. xprintidle basically just returns the idle time of an x window, therefore on a system without a GUI it is not needed and should not be installed. It should be available in standard package managers. E.G. apt-get, yum, or dnf

'''Installing Mono'''
Many distributions come with an out of date version of mono in their package manager. Therefore, do not attempt to install via your package manager without the below modifications

=== Debian 8+, Ubuntu 13.10+, and derivatives ===

To install:

<pre>
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update
sudo apt-get install mono-complete
sudo apt-get install xprintidle
</pre>

* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log

The service is automatically configured to run on startup. To manually start and stop the service:

<pre>
sudo service FOGService start
</pre>
<pre>
sudo service FOGService stop
</pre>

To uninstall:

<pre>
sudo service FOGService stop
sudo mono SmartInstaller.exe uninstall
</pre>

=== CentOS 7, Fedora 19 (and later), and derivatives ===

To install:

<pre>
yum install yum-utils
rpm --import "http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF"
yum-config-manager --add-repo http://download.mono-project.com/repo/centos/
yum install mono-complete
yum install xprintidle
</pre>

* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log

The service is automatically configured to run on startup. To manually start and stop the service:

<pre>
sudo systemctl start FOGService
</pre>
<pre>
sudo systemctl stop FOGService
</pre>

To uninstall:

<pre>
sudo systemctl stop FOGService
sudo mono SmartInstaller.exe uninstall
</pre>

=== openSUSE and SLES ===

You can install mono using SUSE One-Click files: [http://download.mono-project.com/repo/mono-complete.ymp http://download.mono-project.com/repo/mono-complete.ymp]

=== Other ===

The FOG Client can be installed on any platform that can run the latest stable build of mono.

To install:

* Check your package manager for mono-complete. After installing it run mono --version. Ensure the version is at least 4.2._ . If it not, remove the package.
* If your package manager had an old version of mono, see [http://www.mono-project.com/docs/compiling-mono/linux/ here] for how to compile mono

* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log

If your system either has systemd or initd the client will be automatically configured to run on startup. If your system does not have either, you will need to configure your system to run the manual start command below on startup.

To manually start and stop the service:

<pre>
sudo /opt/fog-service/control.sh start
</pre>
<pre>
sudo /opt/fog-service/control.sh stop
</pre>

===Limitations===
* The FOG Tray is currently incompatible on linux systems. Regardless of what you set during installation, it will not run.
* The follow modules / features are not yet supported
** Active Directory joining
** PrinterManager

== Installing - OSX ==

'''Prerequisites'''
* Mono (latest stable build)

'''Installing Mono'''
* If you are running El Capitan, navigate to [http://www.mono-project.com/download/#download-mac http://www.mono-project.com/download/#download-mac] and download Mono Universal Installer
* Otherwise, navigate to [http://www.mono-project.com/download/#download-mac http://www.mono-project.com/download/#download-mac] and download Mono 32-bit

'''Installation'''
* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log
* Reboot the system to complete the installation.

The service is automatically configured to run on startup. To manually start and stop the service:

<pre>
sudo launchctl load -w /Library/LaunchDaemons/org.freeghost.daemon.plist
</pre>
<pre>
sudo launchctl unload -w /Library/LaunchDaemons/org.freeghost.daemon.plist
</pre>

To uninstall:

<pre>
sudo launchctl unload -w /Library/LaunchDaemons/org.freeghost.daemon.plist
sudo mono SmartInstaller.exe uninstall
</pre>

'''Limitations'''
* The follow modules / features are not yet supported
** PrinterManager

'''Logging'''

You can find the client log file in /opt/fog-service/fog.log

== Additional Details ==

=== Features overview ===

The purpose of the FOG Client is multi-fold.

The client allows the host to automatically:
* Auto logout -- Enables auto logout of users if inactive for specified period of time. 5 minute's is the minimum time as all others are way too soon, sometimes people may just be on a phone, or had to step out for a bathroom break.

* Client Updater -- (Only on legacy clients) Allows the client to update it's modules if you had to customize things, or found a more recent build was needed for your environment.

* Directory Cleaner -- (Only on legacy clients -- Only worked with Windows XP) Enables the client to remove directories on the host automatically. It lost operation after Windows XP due to UAC controls and better security mechanisms especially needed. Removed completely from the New client.

* Display Manager -- (Legacy clients and at least through 0.9.12 of the new client, might come back if the need is strong enough though you can achieve the same results using a snap in.) Enables the client to adjust the resolution of the system on a per system basis, or global basis.

* Power Management -- Allows you to specify a shutdown, WOL, or restart on a per-host basis. Format for the scheduling is CRON, and can be done on an individual host or through groups. There is no limit to the number of scheduled power tasks.

* Host Registration -- Registers additional mac addresses to a pre-existing host if registered. The New client will also register the host under a pending status if the host is not already registered.

* Hostname Changer -- Changes the hostname and joins the domain automatically.

* Printer Manager -- Manages Printers for the host. Legacy client only added printer or added/removed printers. The No management for both new and legacy simply does nothing. Will remove all printers under Add/Remove type and only add back the printers as needed (Only Assigned Printers). Under Add Only (now FOG Managed Printers) only manages printers that are listed under the printer's GUI and those that are assigned to that host. In legacy client, it only added printers and never removed. Under the new client, it will ONLY manage printers assigned meaning if you remove a printer from a host, the new client will remove that printer.

* Snapins -- Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy.

* Task Reboot -- This will just check if the client is in a tasking (other than a snapin tasking). If it is in a tasking, and the module is enabled, the host will be told to reboot. There is a third portion though in that if the user is logged in, and enforce is not enabled nothing will happen.

* User Cleanup -- (Legacy clients only and again only on Windows XP). Works similar to Directory Cleanup but the entries you make are "safe" user profiles. If the user is not under this listing, it will be deleted. Will not work with the new client, and even legacy clients will not work on anything beyond Windows XP due to UAC and Interactive Service utilities.

* User Tracker -- Just tracks who logs in/out of a client.

=== Security Design ===

Communications between the FOG Client (0.9.9+) and the FOG Server (1.3.0+) are secured using public key infrastructure.

A Certificate Authority and private key is generated on the FOG server during first installation in this location:

<pre>/opt/fog/snapins/ssl</pre>

The public certificate is generally located here:
<pre>/var/www/html/fog/management/other/ssl</pre>

The client installs your servers’ certificate and the FOG Project certificate.

The “FOG Project” CA (made by the FOG Project) serves two purposes:

*SYSTEM level services need to be digitally signed otherwise windows will throw security errors. This can also be used to ensure no tampering was done with the client files

*That certificate is used to “verify” upgrades. Lets say we release a patch for the client, the client will download the MSI from your server and check if it was signed by us. If the MSI was somehow tampered, the digital signature would no longer be valid.

Using HTTP over HTTPS has no security benefit to the client. Why? Because all traffic is already encrypted. Here’s a very basic overview of how the new client communicates

*Each client has a security token. This is used to prove to the server that the client is the actual host and not an impersonator. This token gets cycled constantly. When the client first makes contact, it encrypts its token and a proposed AES 256 key using RSA 4096 using your server’s public key. This public key is verified against the pinned server CA certificate by checking the x509 chain and fingerprints.

*If the server accepts the security token and the new AES key, all traffic from that point on is AES 256 encrypted using that securely transmitted key.

The whole point of our security model is to allow for secure communication over insecure medians.
Even then, the client installation has an HTTPS option, but it serves no real security benefit.

References:

[https://forums.fogproject.org/topic/6325/invalid-security-token-without-any-security-tokens-being-set-also-ca-ssl-security-concerns/6 CA SSL security concerns]

[https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning Certificate and Public Key Pinning]

[https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet#Certificate_and_Public_Key_Pinning Transport_Layer_Protection_Cheat_Sheet]

==== Reset encryption data ====
This pertains to the new fog client available in FOG 1.3.0 and above, and does not apply to the legacy fog client that was available in 1.2.0 and below.

The “Reset encryption data” is mainly doing one thing: Clearing the security token for a host.

Each host has a security token used by the client. This token is private; only the client knows it and is protected. It is used to prove the identity of the host, ensuring no one ‘fakes’ being a certain host. So when you 'Reset Encryption Data", you are essentially telling the server that the first host to say that they are the host in question gets ‘locked’ in (pinned is the technical term).

In order to have encrypted traffic, the handshake must occur. During the handshake the server proves its identity to the client, and the client proves its identity to the server (using the security token). If the handshake fails (due to a bad security token), encryption cannot occur.

The most common scenario where the security tokens for a client will be incorrect is if you manually uninstall a client, and then install it.

=== Maintain Control Of Hosts When Building New Server ===

Because of the security model of FOG 1.3.0 and the new client, without the proper CA and ssl certificates present on a new fog server, any currently deployed hosts with the new fog client installed will ignore the new server and not accept commands from it. This is by design.

In order to maintain control of existing hosts with existing new fog client deployments, you must copy this directory from the old server to the new server:

* /opt/fog/snapins/ssl

Copy the directory to a temporary location first. I would suggest /root

<pre>cp -R /opt/fog/snapins/ssl /root</pre>

Then you can use scp to copy the directory (or some other method) to your new fog server. Run the below command from the '''old''' server, Where x.x.x.x is the new fog server's address:

<pre>scp -rp /opt/fog/snapins/ssl root@x.x.x.x:/root</pre>

Or, the reverse. Run the below command from the '''new''' server, where x.x.x.x is the old fog server's address.

<pre>scp -rp root@x.x.x.x:/opt/fog/snapins/ssl /root</pre>

Next, install fog. After the installation is complete, delete the ssl folder the installer made, and place your old ssl (from /root that you copied) in there. The ownership should be fog:apache on Red-Hat variants, should be fog:www-data on Debian variants. Then '''re-run the installer.''' Instructions for the folder manipulation are below, assuming you followed the above instructions. On the '''new''' server:

<pre>
rm -rf /opt/fog/snapins/ssl
cp -R /root/ssl /opt/fog/snapins/ssl
chown -R fog:apache /opt/fog/snapins/ssl #or fog:www-data for ubuntu and debian
</pre>

If you do not care about maintaining control of existing hosts with existing new fog client deployments (because there is only 1 or 2), you can recreate your CA with the -C argument during installation:

<pre>./installfog.sh -C</pre>

Note: Recreating the CA (--recreate-CA) is '''very strongly advised against''' if you have many clients deployed already, because it resets the identity of the FOG Server. This causes all fog clients to distrust the server, and will require total reinstallation of all fog clients in an environment. However, you may recreate the keys (--recreate-keys) safely and be able to still control the fog clients.

=== FOG Client 0.10.0+ Installation Options ===

<pre>msiexec /i FOGService.msi /quiet USETRAY="0" HTTPS="0" WEBADDRESS="192.168.1.X" WEBROOT="/fog" ROOTLOG="0"</pre>

Firstly, all options are optional. Here’s what they all do:

*USETRAY: defaults to "1", if "0" the tray will be hidden

*HTTPS: defaults to "0", if "1" the client will use HTTPS (not recommended)

*WEBADDRESS: defaults to "fog-server", this is the ip/dns name of your server

*WEBROOT: defaults to "/fog"

*ROOTLOG defaults to "0", if "1" the fog.log will be at C:\fog.log, otherwise %PROGRAMFILES%\FOG\fog.log

Reference: [https://forums.fogproject.org/topic/6222/msi-silent-install-without-tray-icon/2 MSI Silent Install without Tray Icon]

=== Manually Reset Encryption On ALL Hosts ===

This applies to FOG 1.3.0 where the New Client is in use and for some reason you need to manually reset the encryption for all hosts.
<pre>
mysql
use fog
UPDATE hosts SET hostPubKey="", hostSecToken="", hostSecTime="0000-00-00 00:00:00";
</pre>

Please note that if your Web interface is functional, you may place all computers into a group, and use the group to reset encryption on all hosts by simply clicking the "Reset encryption" button on the group's basic page.

=== FOG Client with Sysprep ===

If you plan to use Sysprep before image capture and are also planning to use the FOG Client, You '''must''' disable the FOGService service from running at boot before you Sysprep to take your image, and then re-enable it within your SetupComplete.cmd so that it is re-enabled '''after''' the image deployment is complete. Failing to do so will break the Sysprep post-deployment process with an error message that says "Windows Setup could not configure Windows to run on this computer’s hardware.” You must also disable the FOG_CHANGE_HOSTNAME_EARLY feature in the fog web interface, as this too will cause problems.

* To disable the FOG_CHANGE_HOSTNAME_EARLY, navigate through: FOG Web Interface -> FOG Configuration -> FOG Settings -> General Settings -> FOG_CHANGE_HOSTNAME_EARLY and un-check this option, and then click save.

* To disable the FOGService, navigate through Windows Control Pannel -> View by Small Icons -> Administrative Tools -> Services -> Locate the FOGService -> Right click -> Properties -> Startup Type -> Disabled.

* To re-enable it post-deployment and post-sysprep operations, in your SetupComplete.cmd you must have these two lines at the end:

<pre>sc config FOGService start= auto
net start FOGService</pre>

setupcomlete.cmd has to be placed under C:\Windows\Setup\scripts in the master system. As the name indicates, the script is called by windows just after setup has finished.

After setting up these two things, sysprep can successfully complete post-deployment setup and start the FOGService. The FOGService can then rename/join/deploy/setup printers/setup snapins/etc for you as normal.

FOG Client

2016-06-19T22:16:51Z

Jbob.21733:

This article applies to the new FOG Client, version 0.10+

== The Different Installers ==

The different installers are located in your FOG server's web interface. The link is always at the very bottom of every page and are even available to you if you're not logged into the fog server.

[[File:Fog client link.png]]

[[File:New FOGClient download link.png]]

'''FOGService.msi''' - Windows only, and is ideal for network deployment.

'''SmartInstaller.exe''' - This is the new default installer. It will work on all platforms.

'''Debugger.exe''' - This is not listed in the web interface but is available from github [https://github.com/FOGProject/fog-client/releases here]. Only use this when the above two are not working. This build has more detailed logs that you can use for troubleshooting or a bug report.

== Installing - Windows ==

'''Prerequisites'''
* .NET Framework version 4.0+ (Note: .NET 4 client profile will NOT work)
You can download the framework from here:

[https://www.microsoft.com/en-us/download/details.aspx?id=40779 Microsoft .NET Framework 4.5.1 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows Server 2008 SP2 Windows Server 2008 R2 SP1 and Windows Server 2012]

Windows 10 comes with a version of .Net that will work.

'''Installation'''
* May use SmartInstaller or msi. Simply download either one of them and run.
* Reboot to complete installation.

'''Limitations'''
* CUPS printers are not yet supported

== Installing - Linux ==

Installation instructions derived from [http://www.mono-project.com/docs/getting-started/install/linux/ http://www.mono-project.com/docs/getting-started/install/linux/]

'''Prerequisites'''
* Mono (latest stable build)
* xprintidle - This dependency is optional. If not installed AutoLogOut will not run. xprintidle basically just returns the idle time of an x window, therefore on a system without a GUI it is not needed and should not be installed. It should be available in standard package managers. E.G. apt-get, yum, or dnf

'''Installing Mono'''
Many distributions come with an out of date version of mono in their package manager. Therefore, do not attempt to install via your package manager without the below modifications

=== Debian 8+, Ubuntu 13.10+, and derivatives ===

To install:

<pre>
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update
sudo apt-get install mono-complete
sudo apt-get install xprintidle
</pre>

* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log

The service is automatically configured to run on startup. To manually start and stop the service:

<pre>
sudo service FOGService start
</pre>
<pre>
sudo service FOGService stop
</pre>

To uninstall:

<pre>
sudo service FOGService stop
sudo mono SmartInstaller.exe uninstall
</pre>

=== CentOS 7, Fedora 19 (and later), and derivatives ===

To install:

<pre>
yum install yum-utils
rpm --import "http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF"
yum-config-manager --add-repo http://download.mono-project.com/repo/centos/
yum install mono-complete
yum install xprintidle
</pre>

* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log

The service is automatically configured to run on startup. To manually start and stop the service:

<pre>
sudo systemctl start FOGService
</pre>
<pre>
sudo systemctl stop FOGService
</pre>

To uninstall:

<pre>
sudo systemctl stop FOGService
sudo mono SmartInstaller.exe uninstall
</pre>

=== openSUSE and SLES ===

You can install mono using SUSE One-Click files: [http://download.mono-project.com/repo/mono-complete.ymp http://download.mono-project.com/repo/mono-complete.ymp]

=== Other ===

The FOG Client can be installed on any platform that can run the latest stable build of mono.

To install:

* Check your package manager for mono-complete. After installing it run mono --version. Ensure the version is at least 4.2._ . If it not, remove the package.
* If your package manager had an old version of mono, see [http://www.mono-project.com/docs/compiling-mono/linux/ here] for how to compile mono

* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log

If your system either has systemd or initd the client will be automatically configured to run on startup. If your system does not have either, you will need to configure your system to run the manual start command below on startup.

To manually start and stop the service:

<pre>
sudo /opt/fog-service/control.sh start
</pre>
<pre>
sudo /opt/fog-service/control.sh stop
</pre>

===Limitations===
* The FOG Tray is currently incompatible on all non-windows systems. Regardless of what you set during installation, it will not run.
* The follow modules / features are not yet supported
** Active Directory joining
** PrinterManager

== Installing - OSX ==

'''Prerequisites'''
* Mono (latest stable build)

'''Installing Mono'''
* If you are running El Capitan, navigate to [http://www.mono-project.com/download/#download-mac http://www.mono-project.com/download/#download-mac] and download Mono Universal Installer
* Otherwise, navigate to [http://www.mono-project.com/download/#download-mac http://www.mono-project.com/download/#download-mac] and download Mono 32-bit

'''Installation'''
* Download SmartInstaller.exe from your FOG server and run the installer with mono.
** sudo mono SmartInstaller.exe
* The client will install to /opt/fog-service , and fog.log will be located at /opt/fog-service/fog.log
* Reboot the system to complete the installation.

The service is automatically configured to run on startup. To manually start and stop the service:

<pre>
sudo launchctl load -w /Library/LaunchDaemons/org.freeghost.daemon.plist
</pre>
<pre>
sudo launchctl unload -w /Library/LaunchDaemons/org.freeghost.daemon.plist
</pre>

To uninstall:

<pre>
sudo launchctl unload -w /Library/LaunchDaemons/org.freeghost.daemon.plist
sudo mono SmartInstaller.exe uninstall
</pre>

'''Limitations'''
* The follow modules / features are not yet supported
** PrinterManager

'''Logging'''

You can find the client log file in /opt/fog-service/fog.log

== Additional Details ==

=== Features overview ===

The purpose of the FOG Client is multi-fold.

The client allows the host to automatically:
* Auto logout -- Enables auto logout of users if inactive for specified period of time. 5 minute's is the minimum time as all others are way too soon, sometimes people may just be on a phone, or had to step out for a bathroom break.

* Client Updater -- (Only on legacy clients) Allows the client to update it's modules if you had to customize things, or found a more recent build was needed for your environment.

* Directory Cleaner -- (Only on legacy clients -- Only worked with Windows XP) Enables the client to remove directories on the host automatically. It lost operation after Windows XP due to UAC controls and better security mechanisms especially needed. Removed completely from the New client.

* Display Manager -- (Legacy clients and at least through 0.9.12 of the new client, might come back if the need is strong enough though you can achieve the same results using a snap in.) Enables the client to adjust the resolution of the system on a per system basis, or global basis.

* Green FOG -- Allows you to specify a shutdown and/or Restart for hosts. These are scheduled on 24 hour time blocks. You schedule the time and action you want to take at that time. The client will schedule what you need for those times.

* Host Registration -- Registers additional mac addresses to a pre-existing host if registered. The New client will also register the host under a pending status if the host is not already registered.

* Hostname Changer -- Changes the hostname and joins the domain automatically.

* Printer Manager -- Manages Printers for the host. Legacy client only added printer or added/removed printers. The No management for both new and legacy simply does nothing. Will remove all printers under Add/Remove type and only add back the printers as needed (Only Assigned Printers). Under Add Only (now FOG Managed Printers) only manages printers that are listed under the printer's GUI and those that are assigned to that host. In legacy client, it only added printers and never removed. Under the new client, it will ONLY manage printers assigned meaning if you remove a printer from a host, the new client will remove that printer.

* Snapins -- Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy.

* Task Reboot -- This will just check if the client is in a tasking (other than a snapin tasking). If it is in a tasking, and the module is enabled, the host will be told to reboot. There is a third portion though in that if the user is logged in, and enforce is not enabled nothing will happen.

* User Cleanup -- (Legacy clients only and again only on Windows XP). Works similar to Directory Cleanup but the entries you make are "safe" user profiles. If the user is not under this listing, it will be deleted. Will not work with the new client, and even legacy clients will not work on anything beyond Windows XP due to UAC and Interactive Service utilities.

* User Tracker -- Just tracks who logs in/out of a client.

=== Security Design ===

Communications between the FOG Client (0.9.9+) and the FOG Server (1.3.0+) are secured using public key infrastructure.

A Certificate Authority and private key is generated on the FOG server during first installation in this location:

<pre>/opt/fog/snapins/ssl</pre>

The public certificate is generally located here:
<pre>/var/www/html/fog/management/other/ssl</pre>

The client installs your servers’ certificate and the FOG Project certificate.

The “FOG Project” CA (made by the FOG Project) serves two purposes:

*SYSTEM level services need to be digitally signed otherwise windows will throw security errors. This can also be used to ensure no tampering was done with the client files

*That certificate is used to “verify” upgrades. Lets say we release a patch for the client, the client will download the MSI from your server and check if it was signed by us. If the MSI was somehow tampered, the digital signature would no longer be valid.

Using HTTP over HTTPS has no security benefit to the client. Why? Because all traffic is already encrypted. Here’s a very basic overview of how the new client communicates

*Each client has a security token. This is used to prove to the server that the client is the actual host and not an impersonator. This token gets cycled constantly. When the client first makes contact, it encrypts its token and a proposed AES 256 key using RSA 4096 using your server’s public key. This public key is verified against the pinned server CA certificate by checking the x509 chain and fingerprints.

*If the server accepts the security token and the new AES key, all traffic from that point on is AES 256 encrypted using that securely transmitted key.

The whole point of our security model is to allow for secure communication over insecure medians.
Even then, the client installation has an HTTPS option, but it serves no real security benefit.

References:

[https://forums.fogproject.org/topic/6325/invalid-security-token-without-any-security-tokens-being-set-also-ca-ssl-security-concerns/6 CA SSL security concerns]

[https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning Certificate and Public Key Pinning]

[https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet#Certificate_and_Public_Key_Pinning Transport_Layer_Protection_Cheat_Sheet]

==== Reset encryption data ====
This pertains to the new fog client available in FOG 1.3.0 and above, and does not apply to the legacy fog client that was available in 1.2.0 and below.

The “Reset encryption data” is mainly doing one thing: Clearing the security token for a host.

Each host has a security token used by the client. This token is private; only the client knows it and is protected. It is used to prove the identity of the host, ensuring no one ‘fakes’ being a certain host. So when you 'Reset Encryption Data", you are essentially telling the server that the first host to say that they are the host in question gets ‘locked’ in (pinned is the technical term).

In order to have encrypted traffic, the handshake must occur. During the handshake the server proves its identity to the client, and the client proves its identity to the server (using the security token). If the handshake fails (due to a bad security token), encryption cannot occur.

The most common scenario where the security tokens for a client will be incorrect is if you manually uninstall a client, and then install it.

=== Maintain Control Of Hosts When Building New Server ===

Because of the security model of FOG 1.3.0 and the new client, without the proper CA and ssl certificates present on a new fog server, any currently deployed hosts with the new fog client installed will ignore the new server and not accept commands from it. This is by design.

In order to maintain control of existing hosts with existing new fog client deployments, you must copy this directory from the old server to the new server:

* /opt/fog/snapins/ssl

Copy the directory to a temporary location first. I would suggest /root

<pre>cp -R /opt/fog/snapins/ssl /root</pre>

Then you can use scp to copy the directory (or some other method) to your new fog server. Run the below command from the '''old''' server, Where x.x.x.x is the new fog server's address:

<pre>scp -rp /opt/fog/snapins/ssl root@x.x.x.x:/root</pre>

Or, the reverse. Run the below command from the '''new''' server, where x.x.x.x is the old fog server's address.

<pre>scp -rp root@x.x.x.x:/opt/fog/snapins/ssl /root</pre>

Next, install fog. After the installation is complete, delete the ssl folder the installer made, and place your old ssl (from /root that you copied) in there. The ownership should be fog:apache on Red-Hat variants, should be fog:www-data on Debian variants. Then '''re-run the installer.''' Instructions for the folder manipulation are below, assuming you followed the above instructions. On the '''new''' server:

<pre>
rm -rf /opt/fog/snapins/ssl
cp -R /root/ssl /opt/fog/snapins/ssl
chown -R fog:apache /opt/fog/snapins/ssl #or fog:www-data for ubuntu and debian
</pre>

If you do not care about maintaining control of existing hosts with existing new fog client deployments (because there is only 1 or 2), you can recreate your CA with the -C argument during installation:

<pre>./installfog.sh -C</pre>

Note: Recreating the CA (--recreate-CA) is '''very strongly advised against''' if you have many clients deployed already, because it resets the identity of the FOG Server. This causes all fog clients to distrust the server, and will require total reinstallation of all fog clients in an environment. However, you may recreate the keys (--recreate-keys) safely and be able to still control the fog clients.

=== FOG Client 0.10.0+ Installation Options ===

<pre>msiexec /i FOGService.msi /quiet USETRAY="0" HTTPS="0" WEBADDRESS="192.168.1.X" WEBROOT="/fog" ROOTLOG="0"</pre>

Firstly, all options are optional. Here’s what they all do:

*USETRAY: defaults to "1", if "0" the tray will be hidden

*HTTPS: defaults to "0", if "1" the client will use HTTPS (not recommended)

*WEBADDRESS: defaults to "fog-server", this is the ip/dns name of your server

*WEBROOT: defaults to "/fog"

*ROOTLOG defaults to "0", if "1" the fog.log will be at C:\fog.log, otherwise %PROGRAMFILES%\FOG\fog.log

Reference: [https://forums.fogproject.org/topic/6222/msi-silent-install-without-tray-icon/2 MSI Silent Install without Tray Icon]

=== Manually Reset Encryption On ALL Hosts ===

This applies to FOG 1.3.0 where the New Client is in use and for some reason you need to manually reset the encryption for all hosts.
<pre>
mysql
use fog
UPDATE hosts SET hostPubKey="", hostSecToken="", hostSecTime="0000-00-00 00:00:00";</pre>

=== FOG Client with Sysprep ===

If you plan to use Sysprep before image capture and are also planning to use the FOG Client, You '''must''' disable the FOGService service from running at boot before you Sysprep to take your image, and then re-enable it within your SetupComplete.cmd so that it is re-enabled '''after''' the image deployment is complete. Failing to do so will break the Sysprep post-deployment process with an error message that says "Windows Setup could not configure Windows to run on this computer’s hardware.”

* To disable the FOGService, navigate through Windows Control Pannel -> View by Small Icons -> Administrative Tools -> Services -> Locate the FOGService -> Right click -> Properties -> Startup Type -> Disabled.

* To re-enable it post-deployment and post-sysprep operations, in your SetupComplete.cmd you must have these two lines at the end:

<pre>sc config FOGService start= auto
net start FOGService</pre>

setupcomlete.cmd has to be placed under C:\Windows\Setup\scripts in the master system. As the name indicates, the script is called by windows just after setup has finished.

After setting up these two things, sysprep can successfully complete post-deployment setup and start the FOGService. The FOGService can then rename/join/deploy/setup printers/setup snapins/etc for you as normal.

FOG Client

2016-05-03T14:17:47Z

Jbob.21733: /* Installing - Windows */

FOG Client

2016-05-03T14:16:38Z

Jbob.21733: /* Installing - Windows */

FOG Client

2016-05-01T15:42:31Z

Jbob.21733: Update installation sections

FAQ

2015-05-14T09:05:41Z

Jbob.21733: /* HAVE YOU TRIED (AS ROOT ON YOUR FOG SERVER) */

= Kernel Panic or Drivers Not functioning=
==Have you tried(As root on your FOG server)==
===FOG 0.32 or earlier.===
Code:
<pre>cd /tftpboot/fog/kernel
mv bzImage bzImage.orig.<CURRENTDATE>
wget -O bzImage --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32
chown -R fog:root /tftpboot</pre>
===FOG 0.33 (64 Bit) OR Download through the kernel updater under Unofficial Kernels.===
Code:
<pre>cd /var/www/<FOGWEBDIR>/service/ipxe
mv bzImage bzImage.orig.<CURRDATE>
wget -O bzImage --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage
chown -R fog.<APACHEUSER (e.g. apache -- redhat, www-data -- debian)> /var/www/<FOGWEBDIR>/service/ipxe</pre>

===FOG 0.33 (32 Bit) OR Download through the kernel updater under Unofficial Kernels.===
Code:
<pre>cd /var/www/<FOGWEBDIR>/service/ipxe
mv bzImage32 bzImage32.orig.<CURRDATE>
wget -O bzImage32 --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32
chown -R fog.<APACHEUSER (e.g. apache -- redhat, www-data -- debian)> /var/www/<FOGWEBDIR>/service/ipxe</pre>

Credits

2015-05-11T22:16:05Z

Jbob.21733: /* Joe Schmitt */

== FOG Project Leads (Creators and Developers too) ==
=== Chuck Syperski ===
Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer 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 following link:

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

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

His username on the FOG forums is Chuck Syperski

=== Jian Zhang ===

No Content

His username on the FOG forums is Jian Zhang

== Community Managers ==
=== Chad-bsid ===

No Content

=== falko ===

No Content

=== andyroo54 ===

No Content

=== BryceZ ===

No Content

=== Kevin ===

No Content

== FOG Developers ==
=== Andy Abplanalp ===

No Content

His username on the FOG forums is Andy Abplanalp

=== Jaymes Driver ===

*Jaymes "loves dnsmasq" Driver

Jaymes is an aspiring software engineer and Ubuntu nut. He began working on his degree at University of Advancing Technology in Tempe, AZ but currently works as a Technology Support Specialist for Seymour Community School Corporation out of Seymour, IN. Jaymes spends his time breaking what isn't broken, and working on private projects that deal 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 Burlington School District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years active duty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email at tommygunsster@gmail.com, thomas@mastacontrola.com, 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 of Science 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 is specialized in IT administration and virtualization, and provides training and consulting for FOG through a training center in France (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 project are 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 Science. You can contact him directly via email at contact@jbob.io or on the forums.

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 are related 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 to count and if he takes a day off there are mass panics. Most of his contributions are testing new features, mass troubleshooting and confirming bugs, wiki updates, and suggesting more a simpler streamline FOG. It is his hope FOG will expand and compete with other streamline imaging software and systems.

His username on the FOG forums is Wolfbane8653

== Notorious Beta Testers ==
=== 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

=== Bill Rice ===
Mr. Rice is a network engineer for Roxborough Memorial Hospital in Roxborough, PA. Enjoys tinkering with all things PC. Building servers, maintaining Infrastructure, WAN, WIFI, LAN, Microsoft Active Directory, Microsoft Exchange, Microsoft SQL. and is learning Linux, (prefers GUI from Mint)

I have been toying around with FOG since build .30 I kinda got in a little late to the party. joined the forums a year later.
I had used fog personally and then introduce this software to the hospital I work for. I provided my own equipment to demonstrate the benefits to using it in our environment, only 1 drawback. I was a total Linux NOOB. I muddled through, configured the original PXE boot and the menu options. I provided my organization with a free alternative for cloning systems on the go while providing a method of booting systems that were corrupted, and recovering lost data. All this was made possible with the FOG software with special thanks to the hard and dedicated work of the founders, Chuck Syperski & Jian Zhang.
Also want to shout out to the additional members of the team for their hard work and the dedication that has provided you with many new updates and added features.

I had spent many hours of researching commands, investigating Linux distro's and have had many pleasures in troubleshooting Ubuntu changes.. lol now I'm a bit more familiar with FOG and its configs, I hope to offer up my experience and ability to seek out those problems/bugs that plague the everyday user so that the development team can fix them quickly.

My username on the FOG Forums is Bill Rice
Feel Free to contact me, I'll do my best to assist. As stated earlier, I'm still new to Linux but the internet is my friend :)
Good luck.
-Bill

=== Wayne Workman ===

Mr. Workman works at a high school in St. Louis as a Technology Specialist, and oversees roughly 500 PCs with about 900 users (among other systems). Holds an AAS degree in Computer Support from Jefferson College, along with CompTIA A+ & NET+. He's an experienced .NET framework programmer and Active Directory Administrator. He began testing the latest version of FOG in January 2015 due to needs of custom Multicast settings, and has worked closely with the Senior Developer to integrate support for Fedora 21 into FOG, and has donated instructions on this specific installation. Today, he spends time helping on the forums and creating better FOG and Troubleshooting documentation.

His username on the FOG forums is Wayne Workman

Upgrade to trunk

2015-02-21T07:57:26Z

Jbob.21733: /* Methods */

=Methods=
*There are a few methods to update to the most resent revision. Each method has its pros so, you will need to figure out which you will use.
**'''SVN'''
**'''Git'''
**'''BTSync'''
**'''wget'''
*Remember these are mostly betas so there are bound to be bugs, but with bugs also comes fixes of the issues found in the "Stable Release"
*If you have nodes they will also need to be upgraded! (Excluding Beta [[Windows_Storage_Node | Windows Nodes]])

==SVN==
*Install as seen in '''[[SVN]]'''
<pre>svn co https://svn.code.sf.net/p/freeghost/code/trunk /some/local/folder</pre>

*Then navigate to the folder you specified and run:

<pre>sudo /some/local/folder/bin/./installfog.sh</pre>

====Update from prior downloaded SVN====
<pre>cd /some/local/folder/
svn up
cd bin
./installfog.sh</pre>

*''NOTE:'' You must run '''svn up''' in the "/some/local/folder/" and not in ".../fog/bin" nor in ".../fog"

----
==Git==

*Install Git

<pre>
sudo apt-get install git
</pre>

*Initial Setup
<pre>
git clone https://github.com/FOGProject/fogproject.git /some/local/folder
</pre>

*Update to latest
<pre>
cd /some/local/folder
git pull
cd bin
./installfog.sh
</pre>
----

==BTSync==
*If you want the latest, get on the BTsync :) You could have changes within 20-30 seconds of them being made.
**'''NOTE:''' as of 2901 the kernels are no longer synced using BTSync. They auto download when installing the fog script.
<pre>
Fog Read only Secret: BAU3NUY3XTKVMHHEZO6C7OH55AN2PCGJV
</pre>

*Create the location that you want to have synced.

<pre>
sudo mkdir /fog
sudo chrmod 777 /fog
</pre>

*Install BTsync:

<pre>
sudo add-apt-repository ppa:tuxpoldo/btsync
sudo apt-get update
sudo apt-get install btsync
cd Downloads
tar xzpf btsync_i386.tar.gz (I have downloaded 32 bit. So check your version)
./btsync
</pre>

*Open a webpage: <IP Address>:8888

<pre>
Add Folder:
Secret: BAU3NUY3XTKVMHHEZO6C7OH55AN2PCGJV
Path: /fog
</pre>

*Then '''Any time''' you see an update. Open up your terminal:

<pre>
cd /fog/bin/
sudo ./installfog.sh
</pre>
And you are updated quite quickly!

~Sources: [http://askubuntu.com/questions/284683/how-to-run-bittorrent-sync,[AskUbuntu]]
----

==wget==
<pre>
wget --no-check-certificate http://mastacontrola.com/fog_trunk.tar.bz2
</pre>
*Once downloaded you'll need to unpack the bz2 file using the command:
<pre>
tar -xjf fog_trunk.tar.bz2
</pre>
*Then go into the unextracted file. Follow these steps:
<pre>
cd fog_trunk/bin
./installfog.sh
</pre>

= Congratulations =
* Congrats! You have now upgraded to the "bleeding edge" of FOG deployment. It is your responsibility to keep upgraded until the next "Stable Release". Until then you will see in the ''cloud'' of your ''Web Gui'' '''rXXXX'''. This indicates the revision you are now on.
*You can check for updates to the revisions under [[File:Config.png]] '''Fog Configuration'''. This will state the version you are on and what the lastest revision is.

Credits

2015-01-12T18:21:59Z

Jbob.21733: /* Joseph Schmitt */

Credits

2014-12-04T14:54:55Z

Jbob.21733: /* Joseph Schmitt */

Credits

2014-12-04T14:54:26Z

Jbob.21733: /* Joseph Schmitt */

Credits

2014-10-13T18:22:10Z

Jbob.21733: /* Joseph Schmitt */

= FOG Project Leads (Creators and Developers too) =
== Chuck Syperski ==
Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer 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 following link:

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

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

== Jian Zhang ==

No Content

= Community Managers =
== Chad-bsid ==

No Content

== falko ==

No Content

== andyroo54 ==

No Content

== BryceZ ==

No Content

== Kevin ==

No Content

= FOG Developers =
== Jaymes Driver ==

No Content

== Tom Elliott ==

Tom Elliott is a contributing developer for FOG computer imaging solution. He is a technical support specialist for Burlington School District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years active duty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email at tommygunsster@gmail.com, thomas@mastacontrola.com, or on the FOG Forums. Username on the forums is Tom Elliott.

== Fernando Geitz ==

No Content

== Peter Gilchrist ==

No Content

== Greg Grammon ==

No Content

== Curtis Larsen ==

No Content

== Lee Rowlett ==

No Content

== Joseph Schmitt ==

Joseph Schmitt is currently working towards a degree in Computer Engineering. The majority of his work is with the FOG Service. You can contact him directly via email at contact@jbob.io or on the forums, his username is Jbob.

== John Shaw ==

No Content

== Travis Vlaminck ==

No Content

= Notorious Beta Testers =
== Andy Abplanalp ==

No Content

== Ian Allison ==

No Content

== Lane Garland ==

No Content

== Greg Plamondon ==

No Content

== Dan Younkin ==

No Content

Credits

2014-10-08T01:11:22Z

Jbob.21733: /* Joseph Schmitt */

= FOG Project Leads (Creators and Developers too) =
== Chuck Syperski ==
Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer 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 following link:

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

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

== Jian Zhang ==

No Content

= Community Managers =
== Chad-bsid ==

No Content

== falko ==

No Content

== andyroo54 ==

No Content

== BryceZ ==

No Content

== Kevin ==

No Content

= FOG Developers =
== Jaymes Driver ==

No Content

== Tom Elliott ==

Tom Elliott is a contributing developer for FOG computer imaging solution. He is a technical support specialist for Burlington School District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years active duty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email at tommygunsster@gmail.com, thomas@mastacontrola.com, or on the FOG Forums. Username on the forums is Tom Elliott.

== Fernando Geitz ==

No Content

== Peter Gilchrist ==

No Content

== Greg Grammon ==

No Content

== Curtis Larsen ==

No Content

== Lee Rowlett ==

No Content

== Joseph Schmitt ==

Joseph Schmitt is a new member of the FOG development team. He is currently working towards a degree in Computer Engineering. The majority of his work is with the FOG Service. You can contact him directly via email at contact@jbob.io or on the forums, his username is Jbob.

== John Shaw ==

No Content

== Travis Vlaminck ==

No Content

= Notorious Beta Testers =
== Andy Abplanalp ==

No Content

== Ian Allison ==

No Content

== Lane Garland ==

No Content

== Greg Plamondon ==

No Content

== Dan Younkin ==

No Content

Credits

2014-08-31T18:51:43Z

Jbob.21733: /* Joseph Schmitt */

= FOG Project Leads (Creators and Developers too) =
== Chuck Syperski ==
Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer 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 following link:

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

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

== Jian Zhang ==

No Content

= Community Managers =
== Chad-bsid ==

No Content

== falko ==

No Content

== andyroo54 ==

No Content

== BryceZ ==

No Content

== Kevin ==

No Content

= FOG Developers =
== Jaymes Driver ==

No Content

== Tom Elliott ==

Tom Elliott is a contributing developer for FOG computer imaging solution. He is a technical support specialist for Burlington School District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years active duty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email at tommygunsster@gmail.com, thomas@mastacontrola.com, or on the FOG Forums. Username on the forums is Tom Elliott.

== Fernando Geitz ==

No Content

== Peter Gilchrist ==

No Content

== Greg Grammon ==

No Content

== Curtis Larsen ==

No Content

== Lee Rowlett ==

No Content

== Joseph Schmitt ==

Joseph Schmitt is a new member of the FOG development team. He is currently working towards a degree in Computer Engineering. The majority of his work is with the FOG Service. You can contact him directly via email at jbob182@gmail.com or on the forums, his username is Jbob.

== John Shaw ==

No Content

== Travis Vlaminck ==

No Content

= Notorious Beta Testers =
== Andy Abplanalp ==

No Content

== Ian Allison ==

No Content

== Dan Younkin ==

No Content

== Lane Garland ==

No Content

== Greg Plamondon ==

No Content

Credits

2014-08-31T18:50:11Z

Jbob.21733: /* Joseph Schmitt */

= FOG Project Leads (Creators and Developers too) =
== Chuck Syperski ==
Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer 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 following link:

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

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

== Jian Zhang ==

No Content

= Community Managers =
== Chad-bsid ==

No Content

== falko ==

No Content

== andyroo54 ==

No Content

== BryceZ ==

No Content

== Kevin ==

No Content

= FOG Developers =
== Jaymes Driver ==

No Content

== Tom Elliott ==

Tom Elliott is a contributing developer for FOG computer imaging solution. He is a technical support specialist for Burlington School District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years active duty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email at tommygunsster@gmail.com, thomas@mastacontrola.com, or on the FOG Forums. Username on the forums is Tom Elliott.

== Fernando Geitz ==

No Content

== Peter Gilchrist ==

No Content

== Greg Grammon ==

No Content

== Curtis Larsen ==

No Content

== Lee Rowlett ==

No Content

== Joseph Schmitt ==

Joseph Schmitt is a new member of the FOG development team. He is currently working towards a degree in Computer Engineering. The majority of his work is with the FOG Service. You can contact him directly via email at jbob182@gmail.com. Username on the forums is Jbob.

== John Shaw ==

No Content

== Travis Vlaminck ==

No Content

= Notorious Beta Testers =
== Andy Abplanalp ==

No Content

== Ian Allison ==

No Content

== Dan Younkin ==

No Content

== Lane Garland ==

No Content

== Greg Plamondon ==

No Content