Follow these steps to create two (2) new workflow for reading, matching, staging and writing data.
Navigate to Workflows
Click the New button
Name and Describe the template, Click Next
Select the all two (2) local Active Directory environments created previously, Click Next
Select ONE-WAY SYNC, Click Next
The screen presented next will be a pre-configured set of workflow steps to facilitate the flow of object and attributes between your directories.
Start at the top of the steps, 1. Read From. Click the Select button
Select all two (2) environments created previously the click OK
Move to Match Objects
This is the step where you will decide on how to match existing objects across your local Active Directories
Matching is conducted by pairing sets of attributes to find corresponding objects
Your two (2) environments may already have some attributes that can be used to find similar objects between the different directories, or you may need to set some to ensure accurate matching
For the purpose of sIDHistory Synchronization, it is most important that existing objects are correctly matched before attempting to create new objects with the source object’s sIDHistory.
Click the Select button to configure the Match Objects criteria for your source Cloud environment and target Cloud environment
Figure 1: Example Match Objects Criteria
Select your source local environment from the drop-down menu
Select your target local environment from the drop-down menu
Choose your first attribute pairings, we will use WindowsEmailAddress for our first match criteria
Choose the sAMAccountName attribute for the source and target fields
To add more attribute pairs, click the Add Attribute button
Additional pairings are evaluated as “OR” conditions. After the first match is found, the additional pairings are not assessed.
In our case we are adding three (3) additional attribute pairings to our criteria
cn – This attribute was added to ensure we can match existing objects based on CN.
UserPrincipalName – UPN was added to ensure uniqueness of the local part of the address string.
Mail – This attribute was added to ensure we can match existing objects based on Mail.
Note: Matching attributes should be reviewed and adjusted based on actual project scope, there isn’t a set matching rule that will fit all scenarios.
Ensure Match Across all object types is not checked in this case.
There is no need in this guide to Add Another Pair, click OK to close this configuration
Drag a Stage Data workflow task from the left panel to the right under the Stage Data task mentioned above. Click the Select button to configure the fourth STAGE DATA workflow task for your target local to source local synchronization rule.
Select the “Local to Local sIDHistory Sync” template, Click Next
Select the source local environment as your source, Click Next
Select the target local environment as your target, Click Next
Select the default target domain name, Click Next
Select the source Organizational Units that will be in scope of the project by click on the ADD OUS button,
In the new OU pop-up window, select the OU that will be in-scope, check the INCLUDE ALL SUB OUS checkbox, click OK to close the pop-up.
Configure any Stage Data filter you like by double click on the OU in the OUs list, it is highly recommended to setup filter to limit the scope to perform a test on the first sync as part of the validation. Click Next
Figure 2: Example Source OU setup.
Select the default OU for newly created objects for Users, Groups, Contacts, and Devices. In our case, we can select the same OU for all object types as we are only syncing user as contact.
Figure 3: Example Target OU setup.
Click Finish
Click the Select button to configure the WRITE TO workflow task. Ensure the target environment is selected, Click OK
Click Next
Configure the workflow sync interval, select Manual for now and we can setup a sync schedule once the test sync has completed. Click Next
Setup any workflow alert you may wish to configure, for now, Click SKIP
Click Finish
Follow these steps to create test objects in the source environment to validate the sIDHistory Sync workflow.
Setup a User in the source local environment and ensure it is part of the OU filter setup for the Local Environment.
DisplayName: Lab1SIDTest1
Setup a group in the source local environment it is part of the OU filter setup for the Local Environment.
DisplayName: Lab1SIDGrp1
Capture the objectSid value for the above test objects for later use.
Follow the below steps to perform the sIDHistory Sync workflow and validation.
Select the workflow configured and click on RUN.
Allow the workflow execution to complete.
Validate Lab1SIDTest1 from source local Active Directory will be created in target. Source user’s objectSid will be copied to the target user’s sIDHistory attribute.
Validate Lab1SIDGrp1 from source local Active Directory will be created in target. Source group’s objectSid will be copied to the target group’s sIDHistory attribute.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center