1. Navigate to Workflows.
2. Click New.
3. Name and describe the template. Click Next
4. Select the two (2) local Active Directory environments created previously. Click Next.
5. Select ONE-WAY SYNC. Click Next.
6. The screen presented next will be a pre-configured set of workflow steps to facilitate the flow of objects and attributes between your directories. 
7. Start at the top of the steps, 1. Read From. Click Select.
8. Select the two (2) environments created previously the click OK.
9. Move to Match Objects
   1. This is the step where you will decide on how to match existing objects across your local Active Directories
   2. Matching is conducted by pairing sets of attributes to find corresponding objects.
   3. 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.
   4. For the purpose of Password Synchronization, it is most important that existing objects are correctly matched to perform Password Synchronization.
10. Click Select to configure the Match Objects criteria for your source Local environment and target Local environment.

    

    1. Select your source local environment from the drop-down menu.
    2. Select your target local environment from the drop-down menu.
    3. Choose your first attribute pairings, we will use WindowsEmailAddress for our first match criteria.
    4. Choose the sAMAccountName attribute for the source and target fields.
    5. To add more attribute pairs, click Add Attribute.
    6. Additional pairings are evaluated as “OR” conditions. After the first match is found, the additional pairings are not assessed.
    7. In our case we are adding three (3) additional attribute pairings to our criteria. Matching attributes should be reviewed and adjusted based on actual project scope; there isn’t a set matching rule that will fit all scenarios.
       • 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.
    8. Ensure Match Across all object types is unchecked in this case.
    9. There is no need in this guide to Add Another Pair, click OK to close this configuration.

11. Drag a Stage Data workflow task from the left panel to the right under the Stage Data task mentioned above. Click Select to configure the fourth STAGE DATA workflow task for your target local to source local synchronization rule.
    1. Select the “Local to Local Password Sync” template. Click Next.
    2. Select the source local environment as your source. Click Next.
    3. Select the target local environment as your target. Click Next
    4. Select the default target domain name. Click Next
    5. Select the source Organizational Units that will be in scope of the project by click on the ADD OUS button.
    6. 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.
    7. Configure any Stage Data filter you like by double-clicking on the OU in the OUs list, it is highly recommended to set up a filter to limit the scope to perform a test on the first sync as part of the validation. Click Next.

       

    8. Select the default OU for newly created objects for Users, Groups, Contacts, and Devices. 

       

    9. Click Finish.
12. Click the Select button to configure the WRITE TO workflow task. Ensure the target environment is selected, click OK.
13. Click Next.
14. Configure the workflow sync interval, select Manual for now and we can set up a sync schedule once the test sync has completed. Click Next.
15. Setup any workflow alert you may wish to configure, for now, click SKIP.
16. Click Finish.