Why some Application Device Management policies not being pushed to devices on command?

Knox Premium knowledge base

How can I configure the company name displayed in the Samsung SDS IAM & EMM app?
Why are enrolled devices not showing compliance status in the SDS IAM & EMM console?
Why does the location map show somewhere other than where the device is actually located?
Are older versions of the SDS IAM & EMM Connector still supported after it is updated to a new version?
Are there any firewall ports that need to be opened for the SDS IAM & EMM Connector to work properly?
Are there any system or pre-installed apps that can't be blacklisted?
As a Managed Service Provider (MSP) admin for SDS IAM & EMM, how do I access each sub-tenant and view managed devices?
Can devices receive Samsung SDS IAM & EMM app updates without Google Play?
Can end users be prevented from setting up EAS-enabled enterprise email accounts in the personal space?
Can I add the Samsung Push Service app to the home screen in Kiosk Mode?

Article ID: 115013837828
October 23, 2017 16:17

[Environment]
SDS IAM & EMM

[Summary]
Most often, it is caused if you are using unsupported or older devices on which all the options for Knox Premium are not available. Also, you must have a Knox Premium license – please check if it was pushed properly in Samsung SDS IAM & EMM Agent > Settings > Diagnostics

Was this article helpful?

Sorry about that

Why wasn't this helpful? (check all that apply)

Couldn't find what I was looking for

Information confusing or unclear

Instructions didn't work

Comments

Great!

Thanks for taking the time to give us some feedback.

Additional Support

Enroll or sign in to submit support tickets

Looking for other product help?

ARTICLES IN THIS SECTION