asked on June 3, 2018
We've had several customers who when we try to setup AD to LFDS syncing for licenses, it fails because of invalid characters in an AD user/group name.
- As AD allows an account to have characters that LFDS can't handle, what are the characters that are/aren't allowed in an AD user/group name when syncing with LFDS so we can track down the culprit?
- Can the error be updated to say the name of the user/group that is causing this to happen instead of a generic error?
1
0