Adding the Jamf Trust App in Workspace ONE - Jamf Safe Internet Documentation

Jamf Safe Internet Documentation
Solution
Application
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

Requirements

Before beginning this process, you must obtain the SECRET_KEY and API_KEY values for the Activation Profile in Safe Internet.

  1. Log in to Safe Internet and navigate to Devices > Activation Profiles.

  2. Select the required Activation Profile.

  3. Click Workspace ONE, then the Windows app configuration section.

  4. Click Show App Configuration.

  5. Locate the key values in the displayed code.

Note:

These key values must be kept secure. Rather than copying them into a file for use later, Jamf recommends that you keep Safe Internet open and then copy these values over into the command described below only when you are ready to do so. Saving these values in a note or similar file is not good security practice.

  1. Open the Workspace ONE console.
  2. Navigate to Resources > Apps > Native.
  3. Click the Add drop-down, and select Application File.
  4. Upload the Jamf Trust MSI file.
  5. Select No in the Is this a dependency app? field.
  6. Click Continue.
  7. Navigate to the Files tab in the App Dependencies section on the Select Dependent Applications page.
  8. Select the C++ application created previously.
  9. In the Files tab, modify the following settings:
    1. Set Use Custom Script for MSI to Yes.
    2. Set Custom Script Type to Input.
    3. In the Uninstall Command field, add msiexec /x ((New-Object -ComObject "WindowsInstaller.Installer").RelatedProducts('{56125110-43de-40ce-9aa8-c988ab9fa0af}')) /qn.
  10. In the Deployment Options tab, click Add under the When To Install section.
    1. In the Criteria Type field, select File does not exist.
    2. In the Path field, add C:\Program Files\\JamfTrust\Service\JamfTrust.Client.Windows.Service.exe.
    3. In the Version field, select Greater than or equal to and then enter the version of Jamf Trust you are deploying, with each number of the version using one box. For example, 8.9.0 will use three boxes.
    4. In the Modified On field, select any date and time from prior to the deployment date.
  11. Modify the command on the Deployment Options tab to include the shareable link.

    The command should be in the following format, with all placeholders defined below:

    msiexec /i "{filename.msi}" SHAREABLE_LINK=https://e.wandera.com/{code} UEM=WSONE API_KEY="{api_key}" SECRET_KEY="{secret_key}" NO_PII=true /quiet /qn /norestart
    {filename.msi}
    The name of your Jamf Trust package replaces this string. For example, "jamftrust.winclient.8.2.0.119.signed.msi".
    {code}
    The enrollment link replaces this string. For example, "https://e.wandera.com/abc123".
    {api_key}
    The API key located under Windows on Microsoft Intune in RADAR's Activation profiles replaces this string.
    {secret_key}
    The secret key located under Windows on Microsoft Intune in RADAR's Activation profiles replaces this string.
    {no_pii}
    This setting eliminates the standard level of Personally Identifiable Information (PII) from Jamf Trust when set to true. The setting is not required when using Safe Internet, but is set to true by default when using Jamf Safe Internet.
    Note:

    This command includes an SSL certificate that ensures an HTTPS block page is displayed when a user attempts to access blocked content. If you do not want to install this certificate, add INSTALL_ROOT_CERTIFICATE=false after SECRET_KEY={secret_key} to the end of the parameter list. Additionally, add DESKTOP_SHORTCUT=yes to add Jamf Trust for Windows to the desktop.

  12. Click Save & Assign.
  13. Assign the Jamf Trust app to the required groups on the following pages.
The Jamf Trust app is deployed to your devices.