Set up workflow
Follow these steps to create one (1) new workflow for reading, matching, serving and writing data.
How to create a one-way cloud-to-cloud sync workflow
Navigate to Workflows
Click the New button
Name and describe the template, click Next
Select all four (4) previously created environments (cloud and on-premises per hybrid tenant) and click Next
Select ONE WAY SYNC, click Next
The screen that appears next is a preconfigured set of workflow steps to facilitate the flow of objects and attributes between your directories. (Note that additional steps will be added as part of this guide to facilitate two-way syncing.)
Start with steps above, 1. Read. Click the Select button
Select all four (4) previously created environments and click OK
Move to match objects
In this step, you decide how to match existing objects in your hybrid tenant directories
Matching is performed by pairing sets of attributes to find corresponding objects
Your four (4) 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 an exact match
It is extremely important for GAL synchronization that email addresses do not conflict before attempting to create new objects in either environment
Click the Select button to configure the object matching criteria for your source cloud environment and your target cloud environment
Figure 1: Example of criteria for matching objects
Select your source cloud environment from the dropdown menu
Select your target cloud environment from the dropdown menu
Select your first attribute pairings, we'll use WindowsEmailAddress for our first matching criteria
Select the WindowsEmailAddress attribute for the source and target fields
To add more attribute pairs, click the Add Attribute button
Further pairings are evaluated as "OR" conditions. After the first match has been found, further pairings are not evaluated.
In our case, we add three (3) additional attribute pairings to our criteria
UserPrincipalName - Added UPN to ensure uniqueness of local part of address string. When creating new mail-enabled users in a target directory, it is important to define any UPN conflicts that may exist
ExternalEmailAddress - This attribute was added to ensure that no existing MEUs or email contacts have existing objects with the same external or destination address
WindowsEmailAddress to CustomAttribute1 - This matching pair is needed to create matching records for new objects created by Directory Sync.
In this case, ensure that Match Across All Object Types is checked.
Check this box to ensure that the workflow evaluates conflicts regardless of object type, as with two-way GAL synchronization there can be cases where this condition is true and we want to make sure you have identified these matches before attempting decide to create new objects or keep the matches
In this guide it is not necessary to add another pair, click OK to close this configuration
Drag a Match objects workflow task from the left pane to the right below the Match objects task mentioned above. Click the Select button to configure the object matching criteria for your target cloud environment and your source cloud environment
Figure 2: Example of criteria for matching objects
Select your target cloud environment from the dropdown menu on the left as the target now becomes the source in a two-way setup.
Select your source cloud environment from the dropdown menu on the right as source now becomes destination in a two-way setup.
Select your first attribute pairings, we'll use WindowsEmailAddress for our first matching criteria
Select the WindowsEmailAddress attribute for the source and target fields
To add more attribute pairs, click the Add Attribute button
Further pairings are evaluated as "OR" conditions. After the first match has been found, further pairings are not evaluated.
In our case, we add three (3) additional attribute pairings to our criteria
UserPrincipalName - Added UPN to ensure uniqueness of local part of address string. When creating new mail-enabled users in a target directory, it is important to define any UPN conflicts that may exist
ExternalEmailAddress - This attribute was added to ensure that no existing MEUs or email contacts have existing objects with the same external or destination address
WindowsEmailAddress to CustomAttribute1 - This matching pair is needed to create matching records for new objects created by Directory Sync.
In this case, ensure that Match Across All Object Types is checked.
Check this box to ensure that the workflow evaluates conflicts regardless of object type, as with two-way GAL synchronization there can be cases where this condition is true and we want to make sure you have identified these matches before attempting decide to create new objects or keep the matches
In this guide it is not necessary to add another pair, click OK to close this configuration
Drag a Match objects workflow task from the left pane to the right below the Match objects task mentioned above. Click the Select button to configure the object matching criteria for your source local environment and your target local environment
Figure 3: Example of criteria for matching objects
Select your local source environment from the dropdown menu on the left.
Select your target local environment from the dropdown menu on the right.
Pick your first attribute pairings, we'll use email for our first matching criteria
Select the mail attribute for the source and target fields
To add more attribute pairs, click the Add Attribute button
Further pairings are evaluated as "OR" conditions. After the first match has been found, further pairings are not evaluated.
In our case, we add two (2) additional pairs of attributes to our criteria
Mail to targetAddress - This matching pair created to ensure that the system can match existing mail contacts in the destination, where targetAddress points to the source mail attribute.
Mail to extensionattribute1 - This matching pair is needed to create matching records for new objects created by Directory Sync.
In this case, ensure that Match Across All Object Types is checked.
Check this box to ensure that the workflow evaluates conflicts regardless of object type, as with two-way GAL synchronization there can be cases where this condition is true and we want to make sure you have identified these matches before attempting decide to create new objects or keep the matches
In this guide it is not necessary to add another pair, click OK to close this configuration
Drag a Match objects workflow task from the left pane to the right below the Match objects task mentioned above. Click the Select button to configure the object matching criteria for your target local environment and your source local environment
Figure 4: Example of criteria for matching objects
Select your local target environment from the left side drop down menu as the target now becomes the source in a bi-directional setup.
Select your local source environment from the drop down menu on the right as source now becomes target in a two-way setup.
Pick your first attribute pairings, we'll use email for our first matching criteria
Select the mail attribute for the source and target fields
To add more attribute pairs, click the Add Attribute button
Further pairings are evaluated as "OR" conditions. After the first match has been found, further pairings are not evaluated.
In our case, we add two (2) additional pairs of attributes to our criteria
Mail to targetAddress - This matching pair created to ensure that the system can match existing mail contacts in the destination, where targetAddress points to the source mail attribute.
Mail to extensionattribute1 - This matching pair is needed to create matching records for new objects created by Directory Sync.
In this case, ensure that Match Across All Object Types is checked.
Check this box to ensure that the workflow evaluates conflicts regardless of object type, as with two-way GAL synchronization there can be cases where this condition is true and we want to make sure you have identified these matches before attempting decide to create new objects or keep the matches
In this guide it is not necessary to add another pair, click OK to close this configuration
Click the Select button to configure the first workflow task, STAGE DATA, for your source cloud to target cloud sync rule.
Select the Cloud to Cloud GAL Sync Source to Target template and click Next
Select the source cloud environment as your source and click Next
Select the target cloud environment as the destination and click Next
Select the default target domain name and click Next
Configure any phase data filter, it is highly recommended to set up a filter to limit the scope to test on first sync as part of validation. Click Next (See Pro Tip 8)
Click Finish
Drag a Stage Data workflow task from the left pane to the right under the Stage Data task mentioned above. Click the Select button to configure the second STAGE DATA workflow task for your target cloud-to-source cloud sync rule.
Select the Cloud to Cloud GAL Sync Source to Target template and click Next
Select the source cloud environment and click Next
Select the target cloud environment and click Next
Select the default target domain name and click Next
Configure any phase data filter, it is highly recommended to set up a filter to limit the scope to test on first sync as part of validation. Click Next (See Pro Tip 8)
Click Finish
Drag a Stage Data workflow task from the left pane to the right under the Stage Data task mentioned above. Click the Select button to configure the third STAGE DATA workflow task for your local source to local destination sync rule.
Select the "Local to Local GAL Sync" template and click "Next".
Select the local source environment and click Next
Select the target local environment and click Next
Select the default target domain name and click Next
Select the source OUs that will be part of the project by clicking the ADD button.
(Video) Migration Manager Suite Technical Presales Demonstration - MMAD and MMEX Migration OverviewIn the new OU pop-up window, select the OU to include in the scope, check the INCLUDE ALL SUB-OUS box and click OK to close the pop-up window.
Configure any phase data filter by double-clicking the OU in the OUs list. It is highly recommended to set up a filter to limit the scope to test on first sync as part of validation. Click Next (See Pro Tip 8)
Figure 5: Example of setting up a source OU.
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 since we are only syncing the user as a contact.
Figure 6: Example of setting up a target OU.
Click Finish
Drag a Stage Data workflow task from the left pane 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 sync rule.
Select the "Local to Local GAL Sync" template and click "Next".
Select the target local environment as the source and click Next
Select the local source environment as the destination and click Next
Select the default target domain name and click Next
Select the source OUs that will be part of the project by clicking the ADD button.
In the new OU pop-up window, select the OU to include in the scope, check the INCLUDE ALL SUB-OUS box and click OK to close the pop-up window.
Configure any phase data filter by double-clicking the OU in the OUs list. It is highly recommended to set up a filter to limit the scope to test on first sync as part of validation. Click next
Figure 7: Example of setting up a source OU.
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 since we are only syncing the user as a contact.
Figure 8: Example of setting up a target OU.
Click Finish
Click the Select button to configure the WRITE TO workflow task. Make sure all four (4) environments are selected, click OK
Click next
Configure the workflow sync interval, select Manual for now and we can set up a sync schedule once the test sync is complete. Click next
Set up any workflow alert that you want to configure. For now, click SKIP
Click Finish
Set up test objects
Follow these steps to create a test object in each environment to validate the GAL Sync workflow.
Set up a remote mailbox in the source local environment and ensure it is part of the OU filter setup for the local environment.
Display name: Lab1RMBX1
Primary SMTP address: Lab1RMBX1@Lab1.Leagueteam.us
Set up a remote mailbox in the local target environment. It is part of the OU filter setup for the local environment.
(Video) AWS Supports You: Migrating Active Directory to AWSDisplay name: Lab2RMBX1
Primary SMTP address: Lab2RMBX1@Lab2.Leagueteam.us
Set up a mailbox in the source cloud environment.
Display name: Lab1CLDMBX1
Primary SMTP address: Lab1CLDMBX1@Lab1.Leagueteam.us
Set up a mailbox in the source cloud environment.
Display name: Lab2CLDMBX1
Primary SMTP address: Lab2CLDMBX1@Lab2.Leagueteam.us
Capture the LegacyExchangeDN value for the above test objects for later use.
Add the test cloud objects as a member of the cloud environment filter group if the filter group was configured when the environment was first configured.
Validation of the workflow
Follow the steps below to complete the GAL Sync workflow and validation.
Select the configured workflow and click RUN.
Wait for the workflow to finish running.
Validate that Lab1RMBX1 is created from the source local environment in the target local environment as a mail contact. The target email contact should have the following set:
The PrimarySMTPAddress of the source mailbox is added as the targetAddress
The source mailbox's LegacyExchangeDN is added as an x500 address.
The source mailbox's PrimarySMTPAddress is added as the PrimarySMTPAddress.
The target contact's cn is generated as a random GUID to ensure there are no name collisions.
Validate that Lab1CLDMBX1 is created from the source cloud environment in the target cloud environment as a mail contact. The target email contact should have the following set:
The source mailbox's PrimarySMTPAddress is added as an external email address
The source mailbox's LegacyExchangeDN is added as an x500 address.
The source mailbox's PrimarySMTPAddress is added as the PrimarySMTPAddress. Validate that Lab1CLDMBX1 is created from the source cloud environment in the target cloud environment as a mail user. The email user should have set the following:
The source mailbox's PrimarySMTPAddress is added as an external email address
The source mailbox's LegacyExchangeDN is added as an x500 address.
The source mailbox's PrimarySMTPAddress is added as the PrimarySMTPAddress.
Validate that Lab2CLDMBX1 is created from the source cloud environment in the target cloud environment as a mail contact. The email contact should have specified the following:
The source mailbox's PrimarySMTPAddress is added as an external email address
The source mailbox's LegacyExchangeDN is added as an x500 address.
The PrimarySMTPAddress of the source mailbox is added as the PrimarySMTPAddress.
- previous
- View topics 13-16 of 17
- Next