Jamf pro macos how to#
Jamf pro macos driver#
Jamf pro macos upgrade#
Jamf pro macos pro#

Jamf pro macos driver#

PKCS#11 Tokens and Smartcards: If your VPN connection uses a PKCS#11 device for authentication, it's highly likely it requires a PKCS#11 driver is installed (for example OpenSC).Please see our Knowledge Base for some server setup examples. We recommend username/password authentication be combined with an additional method such as a One Time Password (OTP), two-factor authentication prompt (for example Google Authenticator, Duo Security, or Authy code), or token device (U2F device, PKCS#11 token, etc.). However from a security standpoint we strongly recommend against relying solely a username and password for authentication. For example, you could instead use a shared certificate/key file for all users, along with a username and password.

Jamf pro macos upgrade#

Your organisation could also upgrade to Jamf Pro, which is capable of per-user file/settings deployment.Īn alternative is to change your OpenVPN setup to no longer rely on unique per-user certificate/key files. Instead, consider using the instructions here to deploy the Viscosity application and settings/license data using Jamf Now, and then have the user download their VPN connection separately (for example from a web portal) or use Viscosity's Import From Server feature. User-Specific Certificate/Key Files: If your OpenVPN setup requires that each user's connection be configured with a unique certificate/key, then it's not recommended to use Jamf Now for VPN connection deployment.Please refer to the below items to see if any apply to your OpenVPN setup: If you don't intend on including any pre-configured VPN connections alongside Viscosity please skip ahead to the next section. Some of these setups may require user-specific authentication files, or require additional software, both of which can complicate deployment using Jamf Now. Viscosity supports a wide range of VPN configuration types and authentication methods.

Jamf pro macos pro#

Alternatively, Jamf Pro does not require that packages be signed.

Jamf pro macos how to#

For information on how to obtain one please see the Signing the Installer section at Bundling Viscosity with VPN Connections & Preferences (Mac). In addition, Jamf Now requires that packages being deployed be code-signed using an Apple issued Developer ID Installer certificate. It's possible to upgrade to the Plus plan from the Account section. To deploy packages, Jamf Now requires that you're on the 'Plus' plan, rather than the 'Standard' plan.

Packages, a free installer editor for macOS.

A copy of our viscosity_managed_installer_1.3.tgz template installer package.

An Apple issued Developer ID Installer certificate.

A working Jamf Now setup on the Plus plan.

A copy of the latest version of Viscosity.

To get started you will need the following requirements:

If this is not the case, or you'd like to create a new setup for testing, please refer to the Jamf Now documentation detailing how to create a new Jamf Now setup before proceeding. This guide assumes that you already have a operational Jamf Now setup. Items covered include creating a Viscosity package suitable for deployment, how to optionally include pre-configured connections and settings, and how to optionally bundle in Viscosity license data. Please note that this differs from Jamf Pro. This article details how to deploy and manage Viscosity installations using Jamf Now. This includes handing mass installation of software. It allows macOS administrators to manage installing and uninstalling software on end-user machines. Jamf is a popular deployment suite of device management software that can be used for managing macOS software deployment in an enterprise environment.