Skip to main content
Version: v2.7.0

Reference iOS MDM deployment

Pre-requisites

Requirements – iOS application link and .mobileconfig file

  • Refer to section Deploy iOS Roaming Client to generate .mobileconfig file (sample - .mobileconfig ) specific to your account
  • iOS application link
  • Edit the .mobileconfig file and update the below fields:SecretId[GENERATED_FROM_PREVIOUS_STEP] SecretKey[GENERATED_FROM_PREVIOUS_STEP] DeviceName[MDM Specific device name variable]

For on-prem deployment, ensure the host matches the on-prem DNS Firewall host. For SaaS version, you can use the default value.

ApiBasePathdnsfirewall.oryxlabs.com/api/v2

Deployment through MDM

  • Create a variable to generate a unique device name on installation. DNS Firewall recommends a combination of device serial number and name to uniquely identify and also manually search for a device on the web application. For instance, if you are using Jamf as your MDM, you cans refer to https://learn.jamf.com/bundle/jamf-school-documentation/page/Payload_Variables.html for potential variables you can use for generating device name dynamically. An example name variable could be %Username% -%SerialNumber% which allows to identify the device by a name and also make it unique using the serial number of the device
  • Push the DNS Firewall application and .mobile config to the supervised mobile devices (Android and iOS)
  • On successfully installing the application and consuming the .mobileconfig, DNS Firewall app should be automatically turned on the end device