SCCM 2016 - Integration spoke vs Service Graph Connectors

[James_Burson]

Currently we use the existing SCCM 2016 Integration spoke for a daily import of certain workstation records to the CMDB.

With Paris, our good friends have released the Service Graph connector series, which clearly includes a new module for SCCM.

I am struggling to find specifics as to if the existing integration spoke will be EOL in the next release or two and when it might be best to consider converting from the integration to the Service Graph Connector, along with any relevant best practices to accompany the switchover.

Can anyone point me to anything they've found that helps?  My searches have not turned up many relevant threads so far. 

Thanks!

James

[Community Alums]

Hello

Just a comment: it seems the Service Graph connector requires an ITOM license as per Store details.

Cheers

[Jay Naumann]

All,

I have the same question.  Should we implement the SCCM Spoke that comes with Integration Hub or should we implement the SCCM Service Graph Connector that comes with ITOM Visibility?  

Thank you, 
Jay

[Harps]

The Service Graph connector will pass the payload through the IRE rather than using coalescing rules. This leads to greater data integrity in your CMDB. If a connector exists and you are entitled to them then I would recommend to use them. 

[Patrick DeCarl1 · Accepted solution]

SCCM SG should be used for imports from SCCM DB, the SCCM spokes are used integration needs like client software distribution.