DocAve 6 Service Pack 3 Control Panel Reference Guide - AvePoint

User Mapping Discrepancy ResolutionsThere are situations where the Source Username cannot be mapped to the Destination Username. Inthe Add Mapping Rules section, you may choose to use the default resolution, or customize the settingsfor resolving such discrepancies.*Note: The Source default user and Source place holder for the source node are only used in two-wayreplication.To have the non-existent destination user replaced by the DocAve agent account, deselect the checkboxnext to Customize settings if the user does not exist in destination.To have the non-existent destination user replaced by a user of your choice, select the Customizesettings if the user does not exist in the destination checkbox, select Add a default destination user,and specify a default destination user in the Target Default User text box.To have the non-existent destination user replaced by the corresponding source users, add a placeholder account in the destination Active Directory, and then perform the following operations:1. Select the Customize settings if the user does not exist in the destination checkbox.2. Select Add a place holder account to keep metadata even if the user no longer exists (Notsupported for SharePoint Online environments.)3. Specify the place holder account that you added in the Active Directory in the Target placeholder text box.*Note: If the Default User and the Place Holder Account have been added in the Active Directory of thedestination, you can set up the user mapping profile in DocAve directly. If not, before setting up the usermapping profile in DocAve, you must manually add the Target Default User and the Target Place HolderAccount in the Active Directory of the destination. For security reasons, it is recommended that youspecify a user who exists in the destination Active Directory but does not exist as the placeholderaccount in SharePoint to avoid unintentionally giving a SharePoint user access to any data assigned tothe placeholder account.*Note: Receiving notification that The user does not exist in destination means one of the followingscenarios is true:• The destination user’s account is no longer active/valid.• The source user and the destination user are in different domains, and there is nodomain mapping or user mapping for these two domains.• The source user and the destination user are in different domains, and the specifieduser cannot be mapped using any of the configured domain mapping or user mapping.• The source user and the destination user are in different domains, and there is a domainmapping for these two domains, but there is no destination user with the same name asthe source user.152DocAve 6: Control Panel