- December 22, 2020
-
Renuka Shahane
In large organizations, the configuration of large device inventory is a pain point for IT teams. Especially when the devices are to be configured over-the-air, streamlining the process of setting up a large number of devices can be complex and cumbersome.
Scalefusion enables customization and configuration of profile settings via a Custom Payload. IT teams can configure a custom calendar and email settings, Wi-Fi and VPN settings, digital certificates for authentication as well as device restrictions using Scalefusion custom payload.
This is achieved by using the custom settings feature available under the iOS and macOS device profile on the Scalefusion dashboard. IT teams can make use of a top-notch XML editor and push the custom payload directly onto the devices. This helps IT admins to fine-tune configuration settings to the T, helping to leverage settings that are not available on the Scalefusion dashboard. Using Scalefusion, IT admins can push more than one payload in the same XML file For example, Custom Payload for Wi-Fi and email can be pushed via the same XML file.
In this article, let us discuss how the profile configuration can be achieved for device profiles on macOS and iOS devices. The payloads are to be created in the XML format based on the developer guidelines by Apple.
Custom Payload settings for iOS
Step 1
Navigate to the Device Profile section of the dashboard. Select the iOS device profile to which you want to push custom settings. Choose the restrictions in the custom settings of the profile section.
If the custom payload settings that you upload conflict with the Device Profile settings created in the Device Profile section, you can resolve these conflicts by selecting either of the two options- you can choose:
- Custom Payload Wins over Device Profile Settings: With this configuration, the settings in the Custom Payload are given precedence over the Device Profile settings.
- Device Profiles Wins over Custom Payload: Under this configuration, settings in the Device Profile are given precedence over Custom Payload.
Step 2
Upload the custom payload by importing the custom payload file or by typing in the custom payload in the existing XML editor.
Step 3
Once you enter the payload, you can click on the validate option to validate the payload. If the payload is successfully uploaded without any syntactic/validation issues, a green tick appears on the top right corner of the editor. If there are any errors within your custom payload, a red cross appears.
Now, click on the update profile button to save your custom payload configuration and the settings will be automatically pushed onto the iOS devices configured with the said Device Profile.
Now, click on the update profile button to save your custom payload configuration and the settings will be automatically pushed onto the iOS devices configured with the said Device Profile.
Custom Payload settings for macOS
The process to configure custom payload settings for macOS is similar to that of iOS.
Step 1
Navigate to the Device Profile section of the chosen macOS profile on the Scalefusion dashboard. Select the custom settings options available in the right column.
On macOS devices, specific payloads can be applied only at the user level. Use the toggle button to enable payload application on the user end. If this option is not chosen, the payload is sent on the device channel and is applied to all the users on the device.
Step 2:
The process for conflict resolution, importing the custom payload file or editing it within the XML editor is similar to that of iOS. After you validate the custom payload file, a green tick appears if there are no errors.
Once validated, click on the save button to save the Device Profile settings. These will be then applied to the devices enrolled with the said Device Profile.
Closing lines…
Custom Payload configuration via Scalefusion MDM helps IT admins in quickly pushing settings across multiple devices. This adds to Scalefusion’s prime offering of demystifying IT tasks and reducing the complexity of managing a large device inventory.
