# FOGProject/fog-client

A cross platform computer management client
C# Objective-C Shell PowerShell Batchfile
Type Name Latest commit message Commit time
Failed to load latest commit information.
.nuget Aug 10, 2015
BootStrap Oct 13, 2015
BuildTools Sep 27, 2016
Debugger Jul 29, 2019
MSI Jul 8, 2019
Modules Sep 9, 2019
PrinterManagerHelper Apr 15, 2017
Service Jul 29, 2019
SetupHelper Feb 14, 2018
ShutdownGUI Jul 8, 2019
Tray Jul 29, 2019
UniversalInstaller Jul 28, 2019
UpdateHelper Jul 29, 2019
UpdateWaiter Jul 29, 2019
UserService Jul 29, 2019
libs Jul 28, 2019
packages Jul 29, 2019
resources Oct 10, 2015
.gitignore May 2, 2017
.travis.yml Oct 14, 2015
FOGService.sln Oct 3, 2017
FOGService.sln.DotSettings Jun 19, 2016
FOGService.v12.suo Aug 1, 2015
build.ps1 Jul 28, 2019
themes.xml Dec 5, 2016

# FOG Client

## Concept

FOG Client is a cross platform computer management software. With it, Linux, Mac, and Windows machines can easily be managed by a remote server.

## Development

#### Cross Platform Compatibility

Feature Windows Linux OSX
Auto Logout
Auto Updating
PowerManagement
Rename
Join Active Directory
Join Samba Directory
Join Open Directory
Snapins
Snapin Packs
User Tracker
TCP/IP Printers
Network Printers
CUPS Printers

## Building

#### Environment

To checkout and build the entire client (including the Installer) Windows is required. This is due to the MSI for network deployment and the Universal Installer. The following dependencies must be installed and included in PATH

• Git for Windows
• Default install settings are fine.
• WiX Toolset
• Powershell / WMF 4.0+ (Windows 7 ships with 3.0)
• See Install Instructions on that page to find the correct package for your system
• .NET v4.6
• MSBuild Tools 2015
• Included with Visual Studios 2015 if you have that already
• Add to PATH - for instructions see below
• Windows SDK 7, .NET 4
• Before running the installer note down and then adjust some registry keys or the installer will fail (details see here)
• 32 bit: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\Version and HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Version
• 64 bit: HKLM\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Client\Version and HKLM\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full\Version
• Default setup is ok if you have enough disk space left but you can savely go with only selecting '.NET Development' and the two submodules
• After installation change back the registry keys to what they were before

In case you want to build the Universal Installer you need to add ILMerge as well:

• ILMerge
• (Add to PATH - for instructions see below)

• Win+R key -> rundll32.exe sysdm.cpl,EditEnvironmentVariables
• New... -> Variable name: PATH, Variable value: C:\Program Files\MSBuild\14.0\Bin;C:\Program Files\Microsoft\ILMerge

#### Repository and powershell setting

Open Git Bash and clone the repository:

IEUser@WIN7 MINGW32 ~/Desktop
\$ git clone https://github.com/FOGProject/fog-client
Cloning into 'fog-client'...
...


Powershell must be configured to allow scripts to be run on the machine. Open CMD as adminstrator and run

powershell "Set-ExecutionPolicy RemoteSigned"


#### Build Command

powershell "C:\path\to\fog-client\build.ps1"


The binaries will be in C:\path\to\fog-client\bin

## Modules

The client's functionality derives from modules. Each module has 1 specific goal, and is isolated from every other module. Each module is executed in a sandbox-like environment, preventing bad code from crashing the service. Since each module is isolated, the client's server can choose which modules to enable or disable.

#### AutoLogOut

AutoLogOut is responsible for automatically logging out users after a set inactivity period. Once that time period is reached, the user is notified that if they remain inactive they will be logged out.

• On Linux AutoLogOut is only possible if xprintidle is installed.
• On Windows one user must be logged in for other users to log out. This is a security measure put in place by Windows. For example, if 5 users are 'logged in', but all hit the 'Switch User' button, non will be logged out. But once someone logs into the machine they will be. GPO is recommened to handle auto log outs on Windows because of this restriction.

#### PowerManagement

PowerManagement is a cron-style power management module. A computer can be configured to restart / shutdown at specific times / days. On-demand shutdown / restarts can also be issued with this module.

#### HostnameChanger

HostnameChanger is one of the core, and most used, modules of the client. It will:

• Rename a computer
• Join a domain
• Leave a domain
• Activate a windows installation with a product key

This module also handles renaming in a domain-friendly fashion. If a computer is joined to a domain, it will first leave the domain, then rename the host, and then join back. This ensures that there are no remenants in the domain.

#### PrinterManager

PrinterManager is aimed to replace the difficult GPO printer systems. Due to the complexity of printers in general, this module has one of the steepest learning curves.

There are three printer management modes

1. None No printers will be added or removed, this is identical to disabling the module
2. FOG Managed Printers The module will only remove printers from a computer if FOG is set to manage it. For example, if a person has personal printer attached to their computer, this module will not touch it.
3. Only Assigned Printers This mode should be used with caution. If selected, this module will only allow assigned printers to be added to a computer. For example, if a person has a personal printer, this module will prevent the user from adding it, unless a FOG administrator adds the printer to the list of managed.

#### SnapinClient

Snapins are executables push out via the FOG server. A snapin can also be set to reboot after finishing. With this module you can push out MSIs, EXEs, batch scripts, shell scripts, or any other file capable of being executed.