This article details the different options for creating a Thirtyseven4 Client Package. Each of the Thirtyseven4 Client Packagers have benefits depending on the deployment criteria.
To access the Client Packager Utility, on the machine hosting your Endpoint Security Console 7.6, open your Start Menu and Search for " Client Packager "
Alternatively, the direct path to the Client Packager application is: C:\Program Files (x86)\Thirtyseven4\Endpoint Security 7.60\Admin\Tools\clagnt.exe
Below are examples of the different Client Packagers that can be create for both Mac and Windows installations.
1. Windows Executable for Manual Deployment
When deploying Thirtyseven4 by manually copying the Client Packager file onto the desktop of the machine from a network share or USB, we suggest creating an executable file with the Antivirus Setup included. This will include all of the files to connect the Client back to the Endpoint Security Console and also build the Antivirus portion directly from the package.
Below is a sample configuration for creating the Client Packager 64 bit executable with the Antivirus Setup Included.
2. Windows Executable for 3rd Party Deployment Software
When deploying the Thirtyseven4 Client Packager executable through a 3rd party software, such as PDQ Deploy, using a light-weight Client Packager will be required. The light-weight executable will install the Client Agent to connect the client system back to the Endpoint Security Console. Once connected, the Endpoint Security Console will build the Antivirus portion through compressed files across the network.
This executable package also supports the /silent parameter.
Below is a sample configuration for creating the Client Packager 64 bit executable with the Antivirus Setup NOT Included.
3. Windows Installer for Group Policy Deployment
The Thirtyseven4 Client Packager can also create .msi files to be deployed via Group Policy or other management software.
This is best utilized in an Active Directory environment.
Below is a sample configuration for creating the Client Packager 64 bit Windows Installer.
4. Roaming/Outside of Network Windows Client Packager
Thirtyseven4 Endpoint Security provides the functionality to allow administrators to install to machines that are outside of the network that hosts the Thirtyseven4 EPS Console. Prior to creating the Roaming Client Packager, you must be connected to our Cloud Based Roaming Service.
To connect to our Cloud Based Roaming Service, login to your Thirtyseven4 Endpoint Security Console and navigate to Admin Settings > Clients > Roaming Clients. This page will have a "Connect to Roaming Platform" button. Once connected, this page will display an "Enable Roaming Service" checkbox. Make sure this option is checked and press Apply.
Once connected, you can now create the Roaming Package.
Below is a sample configuration for creating the Roaming Client Packager.
1. Manual Mac Deployment Client Packager
For manual deployment to MacOS devices Thirtyseven4 Endpoint Security can compile .Tar files. When compiling the MacOS installer on the machine hosting the Thirtyseven4 Endpoint Security Console, the first step is to download the MacOS build. ( http://updates.thirtyseven4.com/builds/2017/eps7.6/mclsetp.7z )
Once downloaded, the second "Browse" option will be used to point to the directory that holds the Mclsetp.7z file. By default, this is the Downloads folder.
Once created, the Mac Client Packager will be available at the following path:
Below is a sample of the Mac Client Packager for Manual Installations.
2. Mac Light-weight Client Packager
Similarly to the Windows Client Packagers, the Mac Client Package can be created without the Antivirus portion included directly in the package. This light-weight package is required for the Notify Install method and is used for compiling a .PKG file to allow the Mac build to be deployed remotely through an MDM software.
The Light-weight Mac Client Packager also supports Roaming Installations so administrators can install to machines that are outside of the network that hosts the Endpoint Security Console.
The exact steps for compiling the Mac .pkg can be found within our Administrator Manual.
Below is a sample of the Light-weight Mac Client Packager.