• Use a Ivanti Secure Access Client preconfiguration file (.pulsepreconfig) when you install Ivanti
Secure Access Client on endpoints using the default Ivanti Secure Access Client installer.
• Instruct users to open a browser and login to the Ivanti server Web portal where the Ivanti
Secure Access Client configuration has been defined. After successful login, the user should
start Ivanti Secure Access Client from the Web page. Or you can enable Auto-launch as a role
option to have the Ivanti Secure Access Client installation begin automatically after login.
The first time Ivanti Secure Access Client connects to a server that offers a Ivanti Secure Access Client
configuration, the configuration settings are installed on the client, and the client is bound to that
server, which means that only that server can update the client's configuration. Any Ivanti server can
update the Ivanti Secure Access Client software version if that feature is enabled, and any Ivanti server
can add a connection to an existing Ivanti Secure Access Client configuration if the Dynamic
connections option is enabled as part of the connection set on the binding server. Only the binding
server can update Ivanti Secure Access Client's configuration.
If the Ivanti Secure Access Client configuration has Dynamic connections enabled, then connections
from other Ivanti servers are automatically added to Ivanti Secure Access Client's connections list when
the user connects to the other Ivanti server through that server's Web portal, and the user starts Ivanti
Secure Access Client using the Ivanti server's Web portal interface. For example, a user has a Ivanti
Secure Access Client configuration from IvantiServerA (the binding server) and the Ivanti Secure Access
Client configuration allows dynamic connections. If the user browses to IvantiServerB and successfully
authenticates through that server's Web portal and clicks the Ivanti Secure Access Client button, the
server adds a IvantiServerB connection to the Ivanti Secure Access Client configuration, and it appears
in Ivanti Secure Access Client's connection list. This new connection is set to start manually so that it
does not attempt to connect when the endpoint is restarted or conflict with the connections from the
binding server. A dynamic connection is added to Ivanti Secure Access Client's connections list.
However, the connection's target URL is Ivanti Web server URL; it does not use the URL that is defined
for the connection in the server's Ivanti Secure Access Client connection properties. In most cases, these
URLs will be the same.
You can see a Ivanti Secure Access Client configuration by creating and viewing a pulsepreconfig file.
(To create the file, go to the Ivanti Secure Access Client Component screen, select a component set, and
then click the Download Installer Configuration button.) The .pulsepreconfig file contains a section
that defines the machine settings and separate sections for each Ivanti Secure Access Client connection
deployed to the client, as shown in figure.
Copyright © 2024, Ivanti, Inc. All Rights Reserved. Privacy and Legal.
Page 14 of 151
Deploying Ivanti Secure Access Client