Pulse Secure Setup Client

Installing Pulse Secure Client from the Web

For a Web install, you direct users to the Web interface of the Pulse server. After a successful login, a user is assigned to a role that includes an automatic download and installation of the Pulse client software.

Note: In order to install the Pulse Secure desktop client from a web browser, you may need to enable certain browser plugins or other technologies on the endpoint device. For example, Java must be enabled on the endpoint device to install the Pulse client from Firefox, and either ActiveX or Java must be enabled to install the Pulse client from Internet Explorer.

Pulse Policy Secure and Pulse Connect Secure include a default connection set and a default component set. These defaults enable you to deploy Pulse Client to users without creating new connection sets or component sets. Installing Pulse Secure Client from the Web. For a Web install, you direct users to the Web interface of the Pulse server. After a successful login, a user is assigned to a role that includes an automatic download and installation of the Pulse client software. Note: In order to install the Pulse Secure desktop client from a web browser, you may.

Pulse Connect Secure 8.2r1 and Pulse Policy Secure 5.3r1 introduced a new web-installation option called “Pulse Secure Application Launcher” (PSAL). PSAL leverages “URL handler” functionality by invoking a custom URL in a manner that instructs the web browser to execute a program that launches/installs the appropriate Pulse Secure client. PSAL was created to address both the restrictions placed on Java on Mac OS X and the deprecation of Java (and ActiveX) plugins in Google Chrome version 45 and the Microsoft Edge browser. You can read more about the PSAL in Pulse Secure’s KB (Knowledge Base) article KB40102.

For a full discussion of this subject, see the “Adaptive Delivery” section of the Pulse Secure Desktop Client Supported Platforms Guide.

The default Pulse Secure client installation settings includes minimal components, which includes the Host Checker component, and a connection to the Pulse server. If you want a Web install that has customized settings, you can do any of the following:

Edit the default connection set and add new connections. The default installer uses the default component set which includes the default connection set.
Create a new connection set and edit the default component set to include the new connection set.
Edit the role to specify a component set that includes the connections you want for the default installation.

Note: A Pulse installation causes a restart of active network connections on a Windows endpoint. When a user initiates a Pulse installation through a WAN connection to the Web interface of a Pulse server, the user might need to log in to their service provider again to reestablish network connectivity. Users need to be aware of this issue before they begin the installation.

Related Documentation

Enabling or Disabling Automatic Upgrades of the Pulse Secure Client

After you deploy Pulse Secure client software to endpoints, software updates occur automatically. If you upgrade the Pulse client configuration on your Pulse server, updated software components are pushed to a client the next time it connects.

Note: If you configure Pulse Secure client to make 802.1X based connections, a reboot might be required on Windows endpoints when Pulse is upgraded.

Note: A bound endpoint receives connection set options and connections from its binding server, but it can have its Pulse client software upgraded from any Pulse server that has the automatic upgrade option enabled. During a client software upgrade the client loses connectivity temporarily.

Pulse client software upgrades are enabled by default. To change the behavior of Pulse client upgrades: