Mapped attributes do not update on scheduled or forced LDAP import (4287902)

Mapped attributes do not update for existing users when the scheduled or a forced LDAP import is completed. For example, if the user's mobile number is mapped during import and that number changes in the directory, we would expect the updated number to change in the SMA (KACE Systems Management Appliance) when a new LDAP import is completed where the attribute is mapped.

Note: It may be noted that when a new user is added, these attributes are added as expected, but subsequent imports do not update the attributes that have changed in the directory.

The work-around at this time is to avoid mapping the Manager field during an LDAP import.

As an example, set the Manager field to No Value during the User Import: