Knox Deployment Program frequently asked questions

Visit https://partner.samsungknox.com/resellers and click Become a Partner.

No, the customer needs to sign up for Knox Configure or Knox Mobile Enrollment first, and then share their Knox Customer ID with you.

Go to the Support page, and click Submit a ticket. You will be asked to sign in with your Samsung Account before you can submit a support ticket.

You can upload up to 10,000 devices for each customer at a time. To upload more than 10,000 devices, contact support.

Depending on the number of devices you submit, uploading them may take a few seconds to a few minutes. When complete, a status bar shows the results of each device upload:

• Upload devices
• Valid devices
• Invalid devices
• Duplicate devices

If there are any errors associated with these devices, click the Details link to view the Activity log.

Devices should appear on customer consoles shortly after you’ve uploaded them.

Yes, customers receive an email when resellers upload devices for them.

Multiple resellers can submit devices on behalf of the same customer.

Ask your customer to find their Knox Customer ID by clicking their account icon in the Knox Mobile Enrollment or Knox Configure console.

The internal customer reference is an optional field. You can use it to assign an ID to customers for your own organizational purposes.

The Knox Customer ID is automatically assigned.

Yes, you can enroll a device to an EMM using Knox Mobile Enrollment and push settings, apps, and content to the same device with Knox Configure.

No, after you’ve uploaded devices for customers, they determine whether to enroll those devices in Knox Mobile Enrollment, Knox Configure, or both.

Deleting removes devices you select one-by-one on the Reseller Portal. Bulk deleting removes a collection of devices that you’ve listed in a CSV file.

To remove a customer, please submit a support ticket.

No, currently you can only sort device data by Upload ID.

You might need to generate a new API key if your old key is corrupted or compromised.

When a new API key is generated, the previous API key is invalidated. The services configured with the previous API key are unavailable until they are updated with the new API key.

It’s not possible to transfer customers or devices from one reseller to another because of the number of potential database changes and the risk associated with changing thousands of database rows. Customer transfers must be performed manually by a reseller.