Component Set Options for Ivanti Connect Secure

A Ivanti Secure Access Client component set includes specific software components that provide Ivanti Secure Access Client connectivity and services.

Client component set options affect Web-based installations only.

•All components: Supports all Ivanti Secure Access Client connection types.

•No components: Updates existing Ivanti Secure Access Client configurations, for example, to add a new connection. Do not use this setting for a new installation.

Creating a Client Component Set for Ivanti Connect Secure

A Ivanti Secure Access Client component set includes specific software components that provide Ivanti Secure Access Client connectivity and services.

Client component set options affect Web-based installations only.

To create a Ivanti Secure Access Client component set:

1.From the admin console, select Users > Ivanti Secure Access Client > Components

2.Click New to create a new component set.

3.If you have not yet created a client connection set, select Users > Ivanti Secure Access Client > Connections and create a new connection set. Or you can use the default client configuration, which permits dynamic connections, and allows Ivanti Secure Access Client to automatically connect to Ivanti Policy Secure or Ivanti Connect Secure.

4.Specify a name for the client component set.

5.(Optional) Enter a description for this client component set.

6.Select a connection set that you have created, or use the default connection set.

7.For Ivanti Secure Access Client components, select one of the following options:

•All components: Supports all Ivanti Secure Access Client connection types.

•No components: Updates existing Ivanti Secure Access Client configurations, for example, to add a new connection. Do not use this setting for a new installation.

8.Click Save Changes.

9.After you create a component set, distribute Ivanti Secure Access Client to users through a role. When users access the role, the installer automatically downloads to the endpoint. The installer components and connections are applied to the endpoint client.

If client connections associated with the component set for a role are changed even though the list of components has not, the existing configuration on the endpoint is replaced immediately if the endpoint is currently connected, or the next time the endpoint connects.

If a user is assigned to multiple roles and the roles include different component sets, the first role in an endpoint’s list of roles is the one that determines which client (component set) is deployed.

Manage Ivanti Secure Access Client Versions

This feature is supported for Ivanti Secure Access Client on macOS and Windows. From 9.1R2 release onwards, this feature is supported for iOS Mobile Client and Android Mobile Client also.

From 9.1R2 onwards, this feature will not be applicable for Windows Universal App.

This feature allows admin to configure a minimum client version. If the client has version lower than the configured minimum version, then the Ivanti Connect Secure server will reject the client connection.

If the client is older than the configured minimum client version, then Ivanti Connect Secure gateway will reject the connection. User can upgrade it later through browser or SCCM server.

For example, the gateway can host Ivanti Secure Access Client 5.2r3, but the minimum version could be Ivanti Secure Access Client 5.2r2.

Similarly, if Ivanti Secure Access Client 5.2r2 is connected to the gateway it would prompt for an upgrade, if the active version is greater than the Ivanti Secure Access Client version.

For Ivanti Secure Access Client 5.2r1, the connectivity would be rejected and will display an appropriate error message.

This feature is qualified only for Ivanti Connect Secure.

To enable this feature on Ivanti Connect Secure:

1.From the admin console, select Users > Ivanti Secure Access Client > Components.

2.Select the Enable minimum client version enforcement checkbox. The following options appear:

•Desktop Clients

•Android Mobile Clients

•iOS Mobile Clients

3.Specify the minimum client version to be enforced on Ivanti Secure Access Client. For example, 22.X.

If the minimum client version is not specified for any specific type of client, any version of the client is allowed to connect to Ivanti Connect Secure without any minimum client version enforcement for that specific client.

4.Click Save.

5.Select a Version to Activate or Delete the version details.

6.Click Browse to select a Ivanti Secure Access Client package.

7.Click Upload to add packages.

Ivanti Secure Access Client allows you to add up to three packages on the server at a time. To add new packages, delete an existing package.

Observe the following:
- Minimum Client Version Enforcement is not supported on Linux clients. Enforcement is not applicable when Ivanti Secure Access Client for Linux connects to a Ivanti Connect Secure with minimum client version enforcement enabled.
- Minimum Client Version Enforcement is not supported by Ivanti Policy Secure.
- Minimum Client Version Enforcement is not supported for a client session launched from a user browser session.