Breadcrumbs

Setup Overview (SaaS Agent for Existing On-Prem Customers)

Contents of this Page

  1. Intended Audience

  2. Topology Diagram

  3. Step-by-Step Guide and Required SMEs

  4. Explanation of Solution Components (including links to detailed setup instructions)

Intended Audience

  • These steps are for existing Syncfish customers, who already use a CI Sync Instance with the CI Sync Multi-Source On-Prem Agent, and are now adopting the CI Sync SaaS Agent (i.e. are running both CI Sync Agents at the same time).

  • For customers in the above situation, many of the components are already in place (e.g. their CI Sync SaaS is already registered in their Entra ID, and their ServiceNow instance is already configured for CI Sync). As such, there are fewer instructions for adding the CI Sync SaaS Agent (and the relevant source systems to the SaaS Agent).

Topology Diagram

The numbered bubbles in the diagram refer to the solution components overview table further down this page (See Overview of Solution Components further below)

CI Sync On-Prem and SaaS Agent to SN - High Level Topology (inc Step Bubbles).svg

Step-by-Step Guide and Required SMEs

Phase

Step #

Additional Details

Link

Required SMEs

Estimated Time to Complete

Initial Setup

Step 1

Review the Pre-Installation Checklist

Here

All SMEs

10 minutes

Step 2

Add one/more source system connections using the CI Sync Web UI

Use the instructions below to create access credentials in the relevant source system and then add a source system connection within your CI Sync SaaS Instance using the CI Sync Web UI

See links per system

CI Sync Admin

Plus one/more of the following depending on the scope of source systems being integrated with CI Sync

  • Azure Admin

  • AWS Admin

  • GCP Admin

  • Lansweeper Cloud Admin

  • Cisco Meraki Admin

  • Intune/Azure Admin

  • Jamf Admin

  • SentinelOne Admin

  • And so on….

10 minutes per source system


Synchronization Testing Phase

Step 3

Run your first synchronization test into your Non-Prod ServiceNow using a small set of asset types (e.g. printers, or servers or switches to start with).

In addition to reading the instructions link, Syncfish highly recommend reading the following page before your first sync.

FAQ - What are the Top Tips when first synchronizing data to my non-PROD CMDB?

Run additional synchronization tests into your Non-Prod ServiceNow and include more asset types in the scope of the sync jobs.

Here

Project Manager

CI Sync Admin

Source System admin/s - One or more of the following:

  • ServiceNow Admin

  • ServiceNow platform owner

  • CMDB Manager

  • IT Asset manager

60 - 90 minutes


CMDB Automation Maturity Phase


Start synchronizing into your Production ServiceNow with a small set of asset types.

Progressively sync additional asset types based on your organisational change management approach.

This phase is best thought of as a maturity journey where your newly automated CMDB underpins improvements to key business processes.

N/A

Project Manager

CI Sync Admin

ServiceNow Admin

ServiceNow platform owner

CMDB Manager

IT Asset manager

This timeframe depends on each customer’s own CMDB Automation adoption plan

Overview of Solution Components

Each of the high level steps reference the CI Sync Detailed Setup Instructions. After reading the High Level Steps below we recommend visiting the Detailed Setup Instructions (for customers with an existing On-Prem Agent) Context and FAQs page here Context and FAQs.

#

Component

High Level Supporting Notes

1

DEV/TEST ServiceNow

Nothing to do (ServiceNow will already have been setup for CI Sync when originally implemented with the CI Sync On-Prem Agent).

2

Enterprise Application object in Entra ID

Nothing to do (your CI Sync SaaS instance will already be registered as an Enterprise Application in Entra ID when CI Sync was first implemented with the CI Sync On-Prem Agent).

3

Cloud Source Systems
(data sources for the CI Sync SaaS Agent)

Each source system has it’s own unique requirements for authentication and API/data access.

Your SME/Admin of each source system needs to create a credential for the CI Sync SaaS Agent and perform any other configuration in the source system itself.

Syncfish provide setup instructions for each source system within Steps to Add Cloud Connectors (Existing Customers). For example:

  1. For AWS: Add AWS to SaaS Agent

  2. For Azure: Add Azure to SaaS Agent

  3. For GCP: Add GCP to SaaS Agent

  4. For Lansweeper Cloud:Add Lansweeper Cloud to SaaS Agent

  5. For Cisco Meraki as a data source: Add Cisco Meraki to SaaS Agent

  6. For InTune as a data source: Add InTune to SaaS Agent

  7. For Jamf as a data source: Add Jamf to SaaS Agent

  8. For SentinelOne as a data source: Add SentinelOne to SaaS Agent

  9. For Microsoft 365 as a data source: Add Microsoft 365 to SaaS Agent

  10. and so on.

4

CI Sync Web UI
(to add ServiceNow as a destination, and add cloud data sources for the CI Sync SaaS Agent)

  1. You will add each cloud source (e.g. AWS, Azure, etc) as a source connection using the CI Sync Web UI. Visit Steps to Add Cloud Connectors (Existing Customers). That page contains an index of each supported source system. For example:

    1. For AWS: Add AWS to SaaS Agent

    2. For Azure: Add Azure to SaaS Agent

    3. For GCP: Add GCP to SaaS Agent

    4. For Lansweeper Cloud:Add Lansweeper Cloud to SaaS Agent

    5. For Cisco Meraki as a data source: Add Cisco Meraki to SaaS Agent

    6. For InTune as a data source: Add InTune to SaaS Agent

    7. For Jamf as a data source: Add Jamf to SaaS Agent

    8. For SentinelOne as a data source: Add SentinelOne to SaaS Agent

    9. For Microsoft 365 as a data source: Add Microsoft 365 to SaaS Agent

    10. and so on.

5

CI Sync SaaS

You then do the following using your Non-Production ServiceNow Instance (e.g. ServiceNow DEV or TEST)

  1. See Run a Small Initial Sync Job (then run more) of the Detailed Setup Instructions.

  2. You will assess the resulting data in your non-Production ServiceNow instance.

  3. Once you are satisfied your non-production results/data is satisfactory you will progress to Production (see #6 below).

6

PROD ServiceNow

Nothing to do (except of course to perform testing in Non-Production ServiceNow before doing any sync’s into Production)