the Samsung Identity Platform resolves the Exchange account name to gmail.com\j.weeks.
Why do I keep receiving account creation notifications after configuring Exchange Settings?
Was this article helpful?
Sorry about that
Why wasn't this helpful? (check all that apply)
Comments
Great!
Thanks for taking the time to give us some feedback.
SDS IAM & EMM Managed Android device
[Summary]
After configuring an Exchange ActiveSync (EAS) profile policy under Samsung Knox Device settings, Samsung Knox Workspace settings or Android Management settings, the enrolled device keeps receiving account creation notifications and cannot complete the email setup.
[Cause]
Users may be have manual settings on the device that prevent them from completing the email configuration. The Exchange configuration may also require some specific format for configuration that has not yet been implemented.
[Resolution]
In order to resolve this issue try the following steps:
- Use User Principal Name (UPN) if no email address is available: If the Active Directory user account has no email address specified, this setting specifies to use the UPN as the email address. If this option is not selected and the Active Directory user account has no email address, the device does not receive the Exchange profile.
- Authentication domain: Enter the authentication domain if it differs from the domain of Active Directory users of enrolled devices. For example, your AD users might be in acme.com, but ActiveSync, users are authenticated through sub-domains such as qa.acme.com and eng.acme.com. or through a hosted domain such as gmail.com or Office 365. If you specify an authentication domain, you must also enter a value in “User name” to specify which user attribute to use to identify the user account for authentication.
- User name: Enter an attribute variable to specify user names. You can specify any Active Directory attribute, but the most useful ones are those that contain the user’s name, such as userPrincipalName %{userPrincipalName} and samAccountName %{samAccountName}. For example, if you use %{samAccountName},when a user enrolls a device, the Samsung Identity Platform contacts Active Directory to resolve the user name attribute value, and also prepends the authentication domain and a backslash to the name.
Example: Given the following settings:
Active Directory user: j.weeks@acme.com
Authentication Domain: gmail.com
Attribute variable: %{samAccountName}