Please provide your feedback in this short Flings' survey.
fling logo of Workspace ONE App Analyzer for macOS

Workspace ONE App Analyzer for macOS

version 1.2.1 — March 22, 2021

Contributors 1

View All

Comments 21

  • profile picture of Diego Izquierdo
  • profile picture of Diego Izquierdo
  • profile picture of Paul Evans
  • profile picture of Paul Evans
  • profile picture of Paul Evans
  • profile picture of Paul Evans
  • profile picture of Paul Evans
  • profile picture of Sixto Suazo
View All

Summary

The Workspace ONE macOS App Analyzer will determine any Privacy Permissions, Kernel Extensions, or System Extensions needed by an installed macOS application, and can be used to automatically create profiles in Workspace ONE UEM to approve list those same settings when deploying apps to managed devices.

Requirements

  • macOS 10.15+
  • Tested on Workspace ONE UEM 2008

Instructions

To connect to your Workspace ONE UEM environment:

  1. From the menubar, select WS1 App Analyzer > Preferences.
  2. Enter in the API information needed to connect to your Workspace ONE UEM environment:
    1. URL: Your Workspace ONE UEM API URL (typically https://asxx.awmdm.com)
    2. Key: Your API Key (created in the WS1 UEM Console under Settings > System > Advanced > API > REST API)
    3. Username: The username for a WS1 UEM administrator account
    4. Password: The password for a WS1 UEM administrator account
  3. Select Test Connection to validate the connection is successful.
  4. Select the appropriate Organization Group. This is where uploaded profiles will be managed.
  5. Select Save. Note that the URL, Key, and Username, and Password will be saved in the device keychain.

How to use the WS1 App Analyzer:

  1. Before installing the target macOS application, launch the WS1 App Analyzer and select the Initial Analysis button. This will determine the configured Privacy Preferences, Kernel Extensions, and System Extensions already installed on the machine.
    1. Note: The first time you perform an analysis, you will be prompted to allow the WS1 App Analyzer to send events to Terminal. Select OK. If you do not, you may need to open System Preferences > Security & Privacy > Privacy > Automation and enable "Terminal" under the WS1 App Analyzer line.
    2. Likewise, Terminal needs full disk access in order to gather the appropriate information. If you receive a prompt stating Terminal needs Full Disk Access, select Open System Preferences and enable "Terminal" under the "Full Disk Access" section.
    3. If you need to enable either of the above settings, simply run the analysis again. You should see a list of configured Privacy Preferences, Kernel Extensions, and System Extensions.
  2. After performing the initial analysis, install the target macOS application on the same machine. You can install the application through any method you prefer, such as manually performing the installation process or deploying the application through Workspace ONE UEM.
  3. When the app is initially installed, manually proceed through any additional prompts to enable Privacy Preferences or approve Kernel or System Extensions. Typical these prompts will appear automatically, but for some applications, they may not appear until certain actions are taken within the application. If needed, feel free to reboot the machine to complete the installation.
  4. Once the target macOS application has been fully installed and all system settings have been enabled/approved, select the Final Analysis button. This will determine the new Privacy Permissions, Kernel Extensions, and System Extensions installed since the initial Analysis was performed. By selecting the New Permissions Needed radio button, you will see a list of only the new settings.
  5. In the table views, you can check or uncheck the permissions that you choose to add to a WS1 UEM profile. Note that certain permissions cannot be enabled through MDM, and may be grayed out. When you are ready, select Upload Profile to upload the profile to your WS1 environment. Make sure you've given your profile a name, and configured the API settings in the above section.
    1. Note: You can double-click any of the rows in the table view to get more information about the particular setting, such as the Code Requirement for Privacy Preferences or the path or Team ID for a Kernel or System Extension.

Changelog

Version 1.2.1

  • Fixed bug that caused crash with certain System Extension configurations

Version 1.2 

  • Added support for Big Sur
  • Updated icon

Version 1.1 Update

  • Fixed bug that prevented Privacy Preferences from loading when default shell was set to zsh.

Contributors

Similar Flings

Mar 03, 2021
fling logo of Workspace ONE Mobileconfig Importer

Workspace ONE Mobileconfig Importer

version 1.1

The Workspace ONE mobileconfig Importer gives you the ability to import existing mobileconfig files directly into a Workspace ONE UEM environment as a Custom Settings profile, import app preference plist files in order to created managed preference profiles, and to create new Custom Settings profiles from scratch.

Oct 08, 2021
fling logo of Workspace ONE Policy Analyzer for Windows

Workspace ONE Policy Analyzer for Windows

version 1.0

Workspace ONE Policy Analyzer for Windows aids in the management of profiles and baselines for Windows 10 devices. Policy Analyzer uses the Workspace ONE UEM API to review the status of profiles and baselines assigned to a specified Windows 10 device.

Jun 28, 2022
UPDATED
fling logo of Workspace ONE ConQuest

Workspace ONE ConQuest

version 1.2

ConQuest configures Meta Quest 2 VR consumer devices for enrollment into Workspace ONE UEM. ConQuest is a Microsoft Windows application that can be run once a Meta Quest 2 device is set to developer mode and connected to the Windows device via USB.