Provisioning Reference Guide › Advanced Configuration Options › Domain Configuration › Explore and Correlate Parameters › Create Users Verify Not Correlated

Create Users Verify Not Correlated

Values: Yes (default) or No

Description: Temporarily set this parameter to No to enable the alternate behavior whereby the Create Global Users phase of explore/correlate will skip the check that the account is not already correlated to a global user.

This capability is deprecated since exploring primary endpoints no longer applies.

The Create Global Users function works as follows for each account present in the container being correlated.

• Check to see if the account is already correlated to an existing global user. If so, leave this account that is still correlated to that global user. On an initial acquisition, no accounts will be correlated. However, on a later re-explore/recorrelate this step is important so that the accounts remain correlated to the global user to which they were previously correlated.

  Note: In a primary endpoint, you would not expect accounts to be correlated to any global user other than the one named the same as the account. There are various scenarios where this could occur. For instance, you may have renamed the account or the global user at some point after they were correlated to one another. Or you might have some system accounts on your primary endpoint that you do not want to correlate to separate global users - opting instead to correlate them to a single restricted global user.

• Attempt to create a global user named the same as the account. If this global user already exists, go on to the next step. This can happen if the global user was also present in another primary endpoint or you deleted your primary endpoint and re-acquired, correlating to global users created during the prior acquisition.
• Create an inclusion between the account and the global user, correlating the account with the global user.

If this configuration parameter is set to No, the first step is skipped. This can greatly improve the performance since that test is time-consuming and slows down as the Provisioning Directory becomes untuned. If you are acquiring an endpoint with more than thousands of accounts, the Provisioning Directory needs to be tuned, but you do not have the chance to do that tuning in the middle of the long-running Correlate operation.

Important! Set this parameter to No only during the initial acquisition of your primary endpoints. Subsequent use can result in accounts that are incorrectly correlated to multiple global users. Once the acquisition is completed, set the parameter to Yes.