Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - Active Directory Users, Groups and Contact Sync Set Up Quick Start Guide

Set up Test Objects

Follow these steps to create test objects in the source environment to validate the Users, Groups, Contacts Sync workflow.

  1. Setup the user object in the source local environment and ensure it is part of the OU filter setup for the Local Environment.
    1. User Object - DisplayName: Lab1User1
  2. Setup the group object in the source local environment and ensure it is part of the OU filter setup for the Local Environment.
    1. Global Group Object - DisplayName: Lab1Grp1
    2. Universal Group Object – DisplayName: Lab1Grp2
    3. Domain Local Group Object - DisplayName: Lab1Grp3
  3. Setup the contact object in the source local environment and ensure it is part of the OU filter setup for the Local Environment.
    1. Contact Object - DisplayName: Lab1Contact1

Validating the Workflow

Follow the below steps to perform Real Time Users, Groups, Contacts Sync workflow and validation.

  1. Select the workflow configured and click RUN.
  2. Allow the workflow execution to complete.
  3. Validate Lab1User1 from source local Active Directory will be created in the correct target OU defined in the workflow. 
  4. Validate Lab1Grp1 from source local Active Directory will be created as Global Group in the correct target OU defined in the workflow. 
  5. Validate Lab1Grp2 from source local Active Directory will be created as Universal Group in the correct target OU defined in the workflow. 
  6. Validate Lab1Grp3 from source local Active Directory will be created as Domain Local Group in the correct target OU defined in the workflow. 
  7. Validate Lab1Contact1 from source local Active Directory will be created in the correct target OU defined in the workflow. 

Best Practices & Tips

This list of best practices and tips has been assembled to further the understanding and assist with implementation questions that may arise during setup and testing.

  1. Mappings have no impact on the matching attributes.
  2. Mappings do not modify the Read Step; all object metadata is read.
  3. If creating an object, such as Unified Groups in the destination the default mappings such as “GroupType” or “ObjectType” are not required because they will be auto generated by Exchange Online during creation.
  4. If only synchronizing Group Membership, then all User attributes can be removed from the default mappings related to your group workflow and template.
  5. Matching by “UserPrincipalName” will only match on the local part value, not the domain part.
  6. Matching by “WindowsEmailAddress” will match on the entire string, not just the local part.
  7. For membership/ownership to sync, within the template option, "If Users are matched" must be set to “Update”, not Skip. Skip will prevent membership from synchronizing.
  8. During testing/piloting you may create a filter under Stage Data step to isolate a subset of test Groups to create and sync membership. This will provide a method to validate a few examples before proceeding onto creating all groups.
  9. The Test Mode option in the workflow prevents the write data step from occurring in a workflow. 
  10. If the RecipientTypeDetails attribute mapping is missing, you will receive this error during the Stage Step. “No mapping found for RecipientTypeDetails.”
  11. If the Name attribute mapping is missing, you will receive this error during the Write Step. “Missing required attribute: Name”.
  12. The default mappings for Proxy Addresses (i.e. EmailAddresses) may prevent the creation of Unified Groups. The following error is received during the Write Step, “There should be at least one MOERA in Email Addresses.”.
  13. When we create a group in the cloud environment, we grant our account Owner access. This can be removed once Sync services are no longer required.
  14. The “ONLY EVALUATE OBJECTS WHICH HAVE CHANGED SINCE THE LAST READ” option only affects the Stage Step. Enable this option after the initial data has been read. Do not set that setting on read and write only workflows.
  15. By default, the “ReplaceDomain” function is used by the “WindowEmailAddress” attribute to set your default email address to the Target Domain selected within the Stage Data step. This can be changed if required.
  16. The default template contains the most commonly used mapping configuration between two environments, depends on the project requirements and scopes, mapping template can be modified to suite your project specific requirements.
  17. Target Group Scope can be configured using these settings if you wish to convert the group scope as new groups created in target Active Directory.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation