Installing Pulse Client on OS X Endpoints Using a Preconfiguration File

The following procedures apply to OS X installations only.

After you create client connection sets and specify the connections to include within a client component set, you can create a preconfiguration file with all the connections you want to distribute with Pulse Client. After you run the Pulse Client installer on the endpoint, you run a special command that imports the settings from the preconfiguration file into Pulse Client.

To create a preconfigured Pulse Client installer for distribution to OS X endpoints:

1.Select Users > Pulse Secure > Connections and create a connection set with the connections that you want to distribute.

2.Select Users > Pulse Secure > Components.

3.If necessary, create a new component set with the connection sets you want to distribute.

The All components or No components options apply to Web-based installations only. The Pulse Client installation program for OS X always installs all components.

4.Select the check boxes next to the component sets that you want to distribute.

5.Click Download Installer Configuration.

You are prompted to save the preconfiguration. You can also specify the name of the target Pulse Secure server for the connections, which enables you to quickly create multiple configuration files that are the same except for the target server.

The default filename of the ".pulsepreconfig" file is the name of the selected component set. Make note of the filename and location where you put the file. The preconfiguration file must be available to the clients either through a network share or distributed along with the Pulse Client installer file.

6.Select Maintenance > System > Installers.

7.Download the Pulse Client installer, "Pulse Client installer (Macintosh)".

Installing Pulse Client on OS X Endpoints Using Command-Line Options

The Pulse Client installer includes Pulse Client and all of the software components for all of the Pulse Client services. The preconfiguration (.pulsepreconfig) file contains the definitions of the Pulse Client connections that provide client access to specific Pulse Secure servers and services. After you distribute the Pulse Client installation package, you must first run the installer, and then run a separate program called jamCommand, which imports the settings from the .pulsepreconfig file. The jamCommand program is part of the Pulse Client installation.

The Pulse Client file you download from the Pulse Secure server is in compressed (.dmg) format. You must unpack the file before you run the Pulse Client installation program.

The following steps include sample commands to install Pulse Client on an OS X endpoint and then import Pulse Client connections from a .pulsepreconfig file.

1.Run the Pulse Client installation program:

sudo /usr/sbin/installer -pkg <full-path-to-the-pulse-install-package> -target /

2.Import the settings from the .pulsepreconfig file:

/Applications/PulseSecure.app/Contents/Plugins/JamUI/./jamCommand -importfile /Users/<user profile>/<pre-config file location on local disk>/<preconfig file name>

Installing Pulse Client on Linux Using Command-Line Options

The nss3-tools and net-tools are dependency packages required to successfully install the Pulse Client. Use the following commands to install these dependency tools manually.

Fedora: yum install <dependency tool name>

Ubuntu and Debian: apt-get install < dependency tool name >

The Installation Command:

Debian – based installation

dpkg -i <package name>

RPM – based installation

rpm -ivh <package name>

The Uninstallation Command:

Debian – based installation

dpkg -r <package name>

RPM – based installation

rpm -e <package name>

The upgrade from old Pulse client to new Pulse Client is not supported.