Testing changes against a single object

Our Technical Support team may occasionally ask you to test a proposed solution against a single object before applying to all of the objects in the scope of your connection. To do so in Active Directory or AD LDS:

1. Copy the connection in question by clicking the Copy button on the General tab.

   1. A pop-up window will appear.
   2. Give this test connection a name that clearly defines it as a test connection.
   3. By default, only config.txt is selected in the box. Do NOT select any other options. Click Copy.

2. On this test connection, make the changes suggested by the Support team.

3. Check Ignore Deletes on the Destination tab.
   Note: If the proposed changes involve any existing custom maps, please confer with Directory Wizards Support team so that we can guide you through the best way to test changes without affecting your current production connections.

4. On the Source tab, use the Optional - LDAP Query Filter to filter Discovery down to a single object. We recommend using (mail=name@domain.com) to select just one object to test against. If your connection is configured to pull Users, Contacts, and Groups, you’ll need to add the filter string in each of these selected fields to successfully narrow the Discovery down to a single object.

5. Run Discovery on this connection first to ensure that the filter is only processing the single user.

   1. Take a look at the Discovery log generated and verify that only a single object is being discovered before proceeding.
   2. If your results contain more than a single object, adjust your LDAP Query Filter until Discovery finds just one object.

6. Run Simulation only.

   1. Confirm only one object is processed.
   2. Be on the lookout for potential deletes, which are not desirable.
   3. Make adjustments as needed until you are satisfied that your configuration will only alter the single, intended object.

7. If you are satisfied with Simulation, run Sync twice.

   1. At this point, you now either have results of the proposed solution, or…
   2. you have an object on the source/dest to test with (confirm by looking at the dest object).

8. Now can now make the config changes you wish to test, if applicable, or share your test results if this Sync provided results of the solution.

9. Run Discovery on the newly modified test connection ensure that the filter is only processing the single user.

   1. Take a look at the Discovery log generated and verify that only a single object is being discovered before proceeding.
   2. If your results contain more than a single object, adjust your LDAP Query Filter until Discovery finds just one object.

10. Run Simulation only.

    1. Confirm only one object is processed.
    2. Be on the lookout for potential deletes, which are not desirable.
    3. Make adjustments as needed until you are satisfied that your configuration will only alter the single, intended object. Consult the Technical Support team for suggestions if you are not happy with your results.

11. Run SYNC.

    1. Confirm one object was processed.
    2. Review the destination object to see if the changes had the desired effect.

12. Repeat from step 8 to test further changes until you are satisfied with the Sync results. If you need assistance before running your SYNC, Contact Support to review your test logs/results.

13. Once ready, you will be applying the above tested changes to your production connection. When you are ready to do so, remember to always run Discovery/SIMULATION before running a sync. Be on the lookout for unexpected ADDs/Mods/Deletes.

14. Finally, when finished, you can delete your test connection to avoid future confusion.

For O365 (or any other directory type), the recommended steps are the same, but the query in step 4 is slightly different. You need to use the attribute name for the primary email address in your query. So, for O365 that would be primarysmtpaddress resulting in a query of (primarysmtpaddress=name@domain.com).