Step 1: installation
First, please get the last release of the installation package (1.2.5), then run the .exe file using administrative credentials. Select “I accept the agreement” when prompted and click “Next”.
Now you can modify the standard folder where the package will install the binary files. Click on “Next” once you filled in your installation path folder:
If you need, you can also customize the shortcut in your Start Menu folder. Click “Next” once you are done:
You can now let the installation process create a desktop shortcut. Click “Next” to proceed:
Click on Install to complete the installation:
Be sure to tick both checkboxes on the final page and click on the “Finish” button:
Step 2: preparation
After installing the connector, the browser will automatically navigate to:
This is the main configuration page for the connector.
Please keep in mind that only the latest versions of Chrome and Edge are supported, so please install them in your system before proceeding with the next steps.
- If you see “Page not found” page, wait 10/20 seconds and refresh the page
- If the browser is not started automatically, please open it and go to http://localhost:1234
Step 3: configuration review
You are now asked to confirm that all requirements are met. You should select all of them prior to clicking on Configure API Key:
Step 4: connector configurator
The next step is about connecting your CoreView Tenant with the Connector.
That can be done by going into the CoreView Portal, menu “Settings” > “My Organization“ > “On Premises“, then selecting “Configure on Premises”:
Then, select services, fill out the credentials like you did in the connector, and click “Save”. If you are configuring more than one AD forest, please fill in the credentials for each AD forest you would like to configure:
You can now copy the API Key that has been generated and paste it into the connector.
After you paste the API Key on the connector, click “Submit”.
If you have any doubts, you can always click “Learn more”, which will lead you to our knowledge base article On-Premises Import Process.
If you see a Success message, it means the connector is configured!
Step 5: verify and open a session on the CoreView portal
Once the connector is configured, go back to the CoreView portal and click “Verify Session”.
Please remember to close your management session before proceeding to the next step.
Our portal will verify the configuration and try to open the session.
You should get the green message “Verified” to confirm your installation has completed successfully:
If you get any error, please review your logs located under c:\temp\logs to identify the issue and click the “Verify Session” button once you fix it.
Step 6: import data
You should now be able to import your on-premises data into your CoreView tenant. Click on the “Show” button:
Click on the toggle “Enable import”, select what are the components you would like to import into CoreView, and then click on “Save and load tree view”:
This will request the Hybrid Connector to start a docker image to connect to your forest and show the tree view of any AD forest you previously configured. Once done, click on the “Import now” button:
Importing organizational units might take some time, depending on the amount of data to import and how many AD forests you have configured.
Once the system displays the OU of your AD forest(s), you can select which ones you would like to import into CoreView and click “Save”:
If you are running a multi-forest environment, please select the needed OUs for each forest you previously configured.
Step 6: source anchor configuration (optional)
If your M365 environment is configured for the synchronization of your on-premises accounts through AD Connect using a different attribute than Microsoft’s default Source anchor attribute (Object GUID), then you must configure the same setting for CoreView.
Click on “Source anchor”, fill in your custom attribute, and click on “Save”:
Step 7: final steps
You have now completed the CoreView Hybrid Connector setup and configuration. You can enable your Management Session and all the CoreView sessions will be hosted by your server: