Knox Deployment App only able to add device to one Knox cloud service

Environment

• Knox cloud services
• Knox Deployment App

Overview

Using the Knox Deployment App, some admins have reported that they aren’t able to enroll devices in more than one Knox cloud service. When adding a device in a second service, such as enrolling in Knox Mobile Enrollment after enrolling in Knox Configure, the following error message displays:

The device is already enrolled.

Cause

This behavior is by design. After the Knox cloud services server looks for any profiles associated with the device, one of two actions occurs:

• If no profiles are found, the user is prompted to enroll with Bluetooth or NFC.
• If one or more profiles are found, the Knox Deployment App proceeds to the next step without prompting for Bluetooth or NFC enrollment.

If a profile is found, your services check if the device is already enrolled with the profile, then repeats for any additional profiles. For example, if the only profile assigned to the device is in Knox Mobile Enrollment, your services retrieve the Knox Mobile Enrollment profile and marks the device as enrolled. The Knox Deployment App then displays the message “The device is already enrolled”.

If no profile is found, the Knox Deployment App continues with the enrollment process.

Resolution

Currently, the Knox Deployment App is only designed for use with one Knox cloud service at a time. To avoid encountering issues with Bluetooth and NFC enrollment, please ensure you remove your device from any service it’s in before enrolling in another.

If you’d like to use both Knox Mobile Enrollment and Knox Configure, ask your reseller to upload your devices to your Knox Mobile Enrollment console. If you don’t have a reseller, raise a support ticket through the Knox Admin Portal and the Samsung Knox team can assist you.

Additional information

• To learn more about the Knox Deployment App, see the Knox Mobile Enrollment admin guide.
• To find a local reseller, visit Buy from a reseller.