Installation - MDM
Overview
This documentation describes the installation of the application via a Mobile Device Management (MDM) system as well as the subsequent configuration using configuration profiles on macOS.
The .pkg installation package provided on the website can be centrally distributed to managed devices via an MDM system. After installation, the complete configuration of the application is performed using .mobileconfig profiles.
The configuration consists of two central areas:
Defaults: Settings that define the behaviour of the application
Permissions: macOS system permissions required for the proper operation of the application
Installation via MDM
Requirements
An existing MDM system (e.g. Intune, Jamf, Kandji, Mosyle)
macOS devices that are managed by the MDM
The application installation package (.pkg)
Distribution of the installation package
The application installation package is uploaded to the MDM and assigned to the desired devices or device groups. The installation is unattended and does not require any user interaction.
Distribution can take place either before or after user login, depending on the respective MDM configuration..
Configuration via configuration profiles
After installation, the application is configured using a .mobileconfig profile. This profile contains both the application settings (Defaults) and the required system permissions.
Basic principle
Configuration is performed centrally via the MDM
Settings are defined by configuration profiles
Local changes on the device are overwritten
Profile changes are automatically applied to the devices
Structure of the configuration profile
A complete .mobileconfig file can contain multiple payloads, including:
Preferences Payload (for setting defaults)
Privacy Preferences Policy Control (for setting permissions)
Login Items (for automatically starting the application)
Detailed information on this:
Encrypted notifications
If certificate-based encryption of notifications has been enabled in the IBI-aws Admin, the following folder must additionally be created on all target devices, and the certificate generated in the Admin must be placed exactly in this folder:
/Library/Application Support/IBITECH/IBI-awsLog Files
The client’s log files are located at:
/Users/user/Library/Logs/IBI.aws.Client
The user Library folder is hidden by default in macOS.
To make it visible, choose View → Show View Options and enable Show Library Folder.
The logs are helpful for support cases or troubleshooting.