- Managing device features and behavior
- Managing devices with IT policies
- Restricting or allowing device capabilities
- Setting device password requirements
- Creating and managing IT policies
- How BlackBerry UEM chooses which IT policy to assign
- Allowing BlackBerry 10 users to back up device data
- Importing IT policy and device metadata updates
- Creating device support messages
- Enforcing compliance rules for devices
- Sending commands to users and devices
- Deactivating devices
- Controlling the software updates that are installed on devices
- Create a device SR requirements profile for Android Enterprise devices
- Create a device SR requirements profile for Samsung Knox devices
- View users who are running a revoked software release
- Managing OS updates on devices with MDM controls activations
- View available updates for iOS devices
- Update the OS on supervised iOS devices
- Configuring communication between devices and BlackBerry UEM
- Displaying organization information on devices
- Using location services on devices
- Using Activation Lock on iOS devices
- Managing iOS features using custom payload profiles
- Managing factory reset protection for Android Enterprise devices
- Create a Factory reset protection profile
- Manually obtain a user ID for a Google account
- How factory reset protection responds to device resets
- Considerations for using a specific Managed Google Play account when setting up a factory reset protection profile
- Clear factory reset protection from a device
- Setting up Windows Information Protection for Windows 10 devices
- Allowing BitLocker encryption on Windows 10 devices
- Managing attestation for devices
- BlackBerry Docs
- BlackBerry UEM 12.13
- Administration
- Managing device features
- Controlling the software updates that are installed on devices
- Create a device SR requirements profile for Samsung Knox devices
Create a device SR requirements profile for Samsung Knox devices
Samsung Knox
devicesDepending on the wireless service provider that a device uses, E-FOTA updates may not be available. Some wireless service providers (for example,
T&T
and Verizon
) use their own systems to manage wireless updates. Verify that an E-FOTA license has been added to
BlackBerry UEM
. To use E-FOTA, you must select the Android
global "Allow OTA updates" rule in the associated IT policy in the BlackBerry UEM
management console.- On the menu bar, clickPolicies and Profiles.
- ClickCompliance > Device SR requirements
- Click
.
- Type a name and description for the profile.
- Click theAndroidtab.
- In theSamsung device firmware ruletable, click
.
- In theDevice modelfield, enter the device model or select one from the drop-down list.
- In theLanguagedrop-down list, select a language.
- In theCarrier codefield, enter the CSC code for the wireless service provider for the device.
- ClickGet firmware version.
- Repeat steps 5 to 8 for each firmware rule that you want to add.
- When you are done, clickAdd.
- In theSamsung device firmware rulestable, clickSchedulebeside the firmware version you added.
- In theSchedule forced updatedialog box, do the following (Note: If you select the Schedule forced update option, the Knox device is no longer restricted to the firmware version and you can manually update it if a later version is available.):
- In theSchedule forced update betweenfields, select a date range when the update must be installed. The date range must be between 3 and 7 days. The default value is 7 days.
- In theSchedule forced update during the hours ofdrop-down lists, specify when the forced update must be installed and the time zone for the user. The time range must be between 1 and 12 hours.
- ClickSave.
If necessary, rank profiles.