Omitting Windows Servers from SCCM import?

jw9
Tera Contributor

Hi,

 

We are in the process of installing the Service Graph Connector for SCCM for the purpose of updating laptop inventory but we want the Windows Servers ONLY to be updated by Discovery. Is this possible using reconciliation rules or any setting in the SCCM integration?

Thanks.

JW

1 ACCEPTED SOLUTION

Rahul Priyadars
Giga Sage
Giga Sage

Service Graph Connector for SCCM uses IRE engine . So you can use data precedence and recon rules to control update/create of Windows Server using Discovery Source.

 

Data source precedence rules are used along with data refresh rules and reconciliation rules to determine reconciliation steps for a CI. These rules determine if, when, and by which data source a CI can be updated.

After an authorized data source updates an attribute, subsequent updates are accepted only from the same data source or from a data source with a higher priority. Updates from a data source with a lower priority are rejected, unless these two conditions are met:
  • The lower propriety source is the first source updating the CI.
  • The CI became stale based on data refresh rules for the CI class.

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/configuration-management/task/t_DefineDataSourcePrecedence.html

Regards

RP

View solution in original post

3 REPLIES 3

knoxkf
Kilo Guru

We had the same issue at our place.  We found that in our environment, they did classify servers using roles.  And all we had to do was tweak the sql (we are still using the legacy transform maps):

v_GS_SYSTEM.SystemRole0 <> 'Server'

This was on the computer identity data source.

jw9
Tera Contributor

I tried to replace the line v_GS_SYSTEM.SystemRole0 as SystemRole with v_GS_SYSTEM.SystemRole0 <> 'Server' but Windows Server data is still getting updated.

Rahul Priyadars
Giga Sage
Giga Sage

Service Graph Connector for SCCM uses IRE engine . So you can use data precedence and recon rules to control update/create of Windows Server using Discovery Source.

 

Data source precedence rules are used along with data refresh rules and reconciliation rules to determine reconciliation steps for a CI. These rules determine if, when, and by which data source a CI can be updated.

After an authorized data source updates an attribute, subsequent updates are accepted only from the same data source or from a data source with a higher priority. Updates from a data source with a lower priority are rejected, unless these two conditions are met:
  • The lower propriety source is the first source updating the CI.
  • The CI became stale based on data refresh rules for the CI class.

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/configuration-management/task/t_DefineDataSourcePrecedence.html

Regards

RP