Appendix A - Understand how the CI Sync Agent Authenticates to SQL Server

Overview

This appendix shows several example diagrams to explain how the CI Sync Agent authenticates to SQL Server during the normal/ongoing operation of the agent. 

The CI Sync Agent uses a SQL Server (and therefore needs to authenticate to it) for the following two purposes:

  1. To read and write to the RecVer database.  The RecVer database is the CI Sync Agent’s delta record tracking SQL DB.

  2. To read only from data sources (i.e. synchronization data sources) from products such as Lansweeper and SCCM (i.e. SQL based data sources).

There are two topologies described below:

  1. Where the CI Sync Agent has been deployed on the same server as your Source System SQL Server.

  2. Or, where the CI Sync Agent has been deployed on a separate server to the Source System SQL Server.

The topology you use (e.g. same server or separate servers) affects the options you can use for authentication between the CI Sync Agent and the SQL Server.  This table explains the options:

Deployment Scenario

SQL Native Authentication

Local Windows User Account

AD Domain Windows User Account

CI Sync Agent and SQL are on the same server.

Supported

Supported

Supported

CI Sync Agent and SQL are on separate servers.

Supported

Not supported

Supported

CI Sync Agent and SQL are on the same server

CI Sync (EE) Multi-Source Agent to SN - Implementation Diag - Agent and SQL Auth Options - Combined Agent and SQL.jpeg

CI Sync Agent and SQL are on separate servers

CI Sync (EE) Multi-Source Agent to SN - Implementation Diag - Agent and SQL Auth Options - Separated Agent and SQL.jpeg