Both in the Sync Service and the Portal there may be regular error messages that we just live with. We’ve figured out they’re “low priority” or perhaps they’re false alerts, where FIM thinks there’s an error but the end result is fine.
However, as much as possible, we should aim for a system that runs without errors unless there really is a problem. Habituating people to “normal” errors just increases the chance they’ll miss actual errors.
Got something to add? Disagree? Comments are open!
1 Reply to “FIM Best Practice: Sort out errors”
I completely agree. When people ignore ambiguity errors, extension exceptions, it will mostly end up with user not getting provisioned, where he/she should be. We can avoid a lot of issue tickets/calls by fixing these errors. We will also service the community by teaching the source of truth to deal data entry with caution.