Understanding the implications with Active Directory

In installations where the Active Directory Connector has been installed, it has implications for exporting and importing workspace data that includes global group and user accounts. For more information about the Active Directory Connector, see About the Active Directory Connector.

When you export global groups that were obtained from Active Directory by the Active Directory Connector, the global groups are identified by 32-digit hexadecimal numbers. These are the Active Directory group IDs.

When you import workspace data that contains global group IDs to another Meridian Project Portal installation with the Active Directory Connector installed, the following rules apply:

• If Meridian Project Portal can find the same global group IDs in Active Directory, the global groups are added to the workspace.
• If a global group cannot be found in Active Directory, a new access (local) group is created.

User accounts cannot be imported to Active Directory from workspace data. All user accounts in the source workspace should exist in the destination workspace prior to the import. If a user does not exist in the destination workspace, the import will fail.