Web install: With a Web install (also called a server-based installation), users log in to the Pulse Secure server's Web portal and are assigned to a role that supports a Pulse Client installation. You can deploy Pulse Client to endpoints from Pulse Connect Secure and Pulse Policy Secure in the following ways: ![]() In all deployment scenarios, you must have already configured authentication settings, realms, and roles. The default settings for the client permit dynamic connections, install only the components required for the connection, and permit an automatic connection to Pulse Connect Secure or Pulse Policy Secure to which the endpoint connects. These defaults enable you to deploy Pulse Client to users without creating new connection sets or component sets. Pulse Policy Secure and Pulse Connect Secure include a default connection set and a default component set. ![]() ![]() This section describes how to deploy Pulse Secure Desktop Client ( Pulse Client) for Windows and Pulse Client for macOS client software from Pulse Policy Secure and Pulse Connect Secure platforms. Using jamCommand to Import Pulse Secure Connections Installing Pulse Client on OS X Endpoints Using a Preconfiguration File Installing Pulse Client on Windows Endpoints Using a Preconfiguration File ![]() Launching Pulse Client from the Pulse Secure server Web Portal Pulse Secure Desktop Client Installation OverviewĪdding a Configuration to a New Pulse Client Installation
0 Comments
Leave a Reply. |