Help with Out of box Microsoft Service Graph Connector for SCCM using IH-ETL

LonLandry1
Giga Guru

Howdy Community
I think I may have scope issues...

I need to confirm I have the correct scopes for:

  • Service Graph Connectors > SCCM > Data Sources
  • Service Graph Connectors > SCCM > Setup

    Also, what is the correct scope for the import set used in IH-ETL?

Here is what I know:

  • I have been using guided setup for ETL, but am having trouble test loading 20 records.
  • When following path in application navigator Service Graph Connectors > SCCM > Data Sources
    I see records that begin with SG-SCCM (Ex. SG-SCCM Computer Identity), all records are in the scope
    Service Graph Connector for Microsoft SCCM.
  • When following path in application navigator Service Graph Connectors > SCCM > Setup
    Then selecting Configure Data Source and Scheduled Data Import and select Configure across from 
    Validate Data Sources. The Data source is shown beginning with SCCM JDB-SG-SCCM in the global scope.
    (I expected SG-SCCM in Service Graph Connector for Microsoft SCCM scope)
  • If I look into the record for the Data source is beginning with SCCM JDB-SG-SCCM. I see a Robust Import Set Transformer named SCCM Computer Identity with Source table SG-SCCM Computer Identity [sn_sccm_integrate_sccm_2019_computer_id] (in scope Service Graph Connector for Microsoft SCCM).

Thanks for your help & time!

 

1 ACCEPTED SOLUTION

Kieran Anson
Kilo Patron

Hey,

So someone created the "JDB" connector in the wrong scope. You'd need to delete the created records and re-follow the setup process but ensure you're already in the "Service Graph Connector for Microsoft SCCM" scope

View solution in original post

3 REPLIES 3

Kieran Anson
Kilo Patron

Hey,

So someone created the "JDB" connector in the wrong scope. You'd need to delete the created records and re-follow the setup process but ensure you're already in the "Service Graph Connector for Microsoft SCCM" scope

Do the connection records need to be in Service Graph Connector for Microsoft SCCM scope?

Yes