Can we disable failed messages when a synchronized account doesn't exist?

Can we disable failed messages when a synchronized account doesn't exist?

Hi,

We're looking to extend our implementation so that a subset of our users that have a second account in another domain can reset both passwords simultaneously using ADSelfService Plus.  I.e. they'll login to ADSelfService Plus as they currently do, against the primary domain, but when they change their password the password on their matching account in the secondary domain is also updated.

In testing this appears to work as expected however, the majority of our users don't have accounts in the second domain so they get some confusing errors - dispite the password changing in the primary domain as we want:
 
I'd like to disable the "There is no such user in this domain" error. Or, even better, can we stop the second domain being an option in the drop down if a second account doesn't exist?

Cameron
                New to ADManager Plus?

                  New to ADSelfService Plus?