The import process runs every six hours and it’s performed through the management runspace opened between the Hybrid Connector and your domain controller configured into the on-premises configuration section of your CoreView Portal.
CoreView will import only on-premises objects which are not included in the synchronization process of your AADConnect environment, since those objects will be imported into your CoreView tenant from the O365 cloud tenant.
This means the on-premises import process will target only the objects that are not already targeted by your AADConnect component available in the Organizational Units you selected from the menu available on “Settings” > “My Organization“ > “On-Premises“ > “Import“:
In terms of architecture, once a CoreView management session is opened from within the CoreView portal, we turn on the docker container which oversees opening the following run spaces:
- Azure Active Directory
2. Exchange Online
3. MSOL Service
4. Microsoft Teams
5. Microsoft Graph
6. Exchange On-Premises
7. Active Directory On Premises
Please mind that if you are running an On-Premises MultiForest environment, CoreView Hybrid Connector opens both Exchange On-Premises and Active Directory On Premises run spaces for each forest you configured.
The management actions selected by the operators from CoreView are executed through those runspaces. Please note the run spaces are initialized using the service account associated with your CoreView Tenant:
From 1 to 5
CoreView uses the cloud account
which has been created when you configured your CoreView Management Session.
The remaining channels associated with the additional workspaces, are opened by the service account you configured in the On-Premises section of your CoreView portal:
Please remember those channels won’t be used for the on-premises import: CoreView will turn on every 6 hours an additional docker container which will connect to on-premises environments, such as Active Directory On-Premises and Exchange On-Premises.
CoreView Hybrid Connector imports objects only the not synced by your AADConnect and updates the remaining objects already imported into CoreView tenant by the standard import process run daily.
Please note that the daily import process targets your Cloud environment, so only on-premises objects and their related attributes selected in this process will be synchronized by AADConnect.
For performing an on-premises import process, CoreView Hybrid Connector turns on a docker container, imports objects through the steps described below, and turns off independently on the further docker container already running for executing CoreView native management actions and custom actions.
Active Directory Structure
Let’s now describe in detail the on-premises Active Directory structure and the objects imported by CoreView.
The screenshot below shows the partial structure behind a domain controller.
As you may know, not all these objects are OUs. Some of these are called containers. The symbol is a little bit different compared to the OU icon – the name is the same as the docker container, but those work with different behaviors.
In the above picture, containers are underlined by a red line.
For the sake of simplicity, a container can also contain objects (users, groups, computers, and so on), and they are like OUs. However, please consider that CoreView doesn’t import anything from them.
In other words, if you put some object in a container, you won’t find that object listed in your CoreView reports nor would you be able to target that container for any management action.
CoreView can display the updated information of the object you manipulated as soon as a management action is performed.
However, if you are performing any change from within the on-premises Active Directory Users and Computers snap-in or through CoreView custom actions, please expect some delay in finding the updated info about an object you modify. That change will be displayed once the next cycle of the Hybrid Connector import process is performed.