Monitoring the import process

To check the details of your import processes, examine the log files located in the following directory on your on-premises server where the Hybrid Connector is installed:

C:\Temp\Logs 

Open the most recent log file and search for these entries:

TransferAdOrganizationalUnit.ps1 | 7437 ms
TransferAdUser.ps1 | 24672 ms
TransferAdGroups.ps1 | 26866 ms
TransferAdGroupMembers.ps1 | 146207 ms

These entries represent the four steps the CoreView Hybrid Connector performs during each on-premises import process.

If any of these steps are missing, it indicates that the import process did not complete successfully. Additionally, the log file should contain error details and the time taken to complete each step, which can assist you in troubleshooting issues related to the import of Organizational Units (OUs), User Objects, Groups, and Group Members from your on-premises environment.

Please note the following limitations:

• For an on-premise Active Directory Resource Forest model, the Hybrid Connector will only import Organizational Units.
• In a multi-forest Active Directory topology, group memberships will not be imported.
• When using an on-premise Organizational Forest Model or a Restricted Access Forest Model, the Hybrid Connector will import both users and groups.
• When importing Active Directory group members in a multi-domain single forest environment, the Hybrid Connector optimizes the import process by attempting to use an Active Directory Global Catalog server. A Global Catalog is a special Active Directory server that contains a searchable copy of all objects across all domains in your forest, so this connection is crucial for importing the group members during the final step. The Hybrid Connector will use a Global Catalog when:
  
  • A Global Catalog server can be discovered and reached from the machine running the Hybrid Agent
  • The Global Catalog server passes a connectivity test
  • If the Global Catalog cannot be found or is unreachable, the connector automatically falls back to querying each domain individually.

During the group member import process, the Hybrid Connector first identifies all groups within each Organizational Unit (OU) across your domains without using the Global Catalog and if a domain controller cannot be contacted while retrieving groups from an OU:

• The OU is skipped, and the groups within it are not processed in that import cycle.