Monitoring the import process

  • Last update on March 4th, 2024

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.
  • With a single forest Active Directory topology, ensure that your hybrid agent can connect to your Active Directory Global Catalog. This connection is crucial for importing all group members during the final step. Failure to do so may result in incomplete information imports.