Service Graph connector - handling the inactive/legacy machines

[kalyani8]

Hello all,

We recently switched over to the SGC from the old SCCM v2. Even though we completed the entire SCCM import, there is a possibility that some computers are not listed as operational. What is the optimal method for managing these records in the CMDB? They will continue to list SCCM as the discovery source.

Should the sys_object_source table be cleaned since a small number of the entries haven't been changed with the SG-SCCM discovery source?

Please suggest!

Thanks 

Kalyani

[Rahul Priyadars]

If i understood correctly your problem Statement- How to handle Old records which are not coming using SG-SCCM?

Old inactive/Decomm records must be kept as it is.

Regards

RP

[kalyani8]

Hi Rahul,

Thanks for the response.

you mean to say that we can leave the discovery source as SCCM for entries which are not updated by SGC?

We identified some of the records are not getting updated even though they are fetched by SGC? is there any necessity to clean up sys_object_source table?

Thanks

kalyani

[ersureshbe]

Hi, No need to clean the source table entries. In OOB, scheduled job is present to clean the import set tables.  Pls refer below link to understand.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0755790

https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/import-sets/t...

[Prabu Velayutha]

@kalyani8  these CIs life cycle status is non operational? This could be due to identification inclusion rule avoiding the updates for non operational CIs.CI Life Cycle status could be a cause. Test by moving it to Install status.

Reference KB below for Discovery to prevent updating the non operational CIs.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0751272