Pros and Cons of SAM Pro with SCCM and no Discovery for End User Computing

[ayman_h]

Hi,

I understand it is best to use SN Discovery for Infrastructure SAM. Is anyone able to elaborate a bit more on any Pros and Cons of not performing SN Discovery on the End User Computing and using only SCCM raw data instead?

Do Software Discovery Models still get created from the SCCM software raw data? 

Thanks,
Ayman

[akash_mehta · Accepted solution]

Not sure of the Pros/Cons...

1) Software Discovery Models do get created from SCCM and normalized via the SAM Pro capabilities

2) EUC Equipment tends to already have the SCCM agent on the device and is able to also gather metering information for certain software so you can get that Usage data into ServiceNow which you wouldn't with SN Discovery

3) I don't think it is a bad idea to use both - however, you will want to set a system property to not bring in software for SCCM Managed devices - if you deploy an EUC device without the agent...discovery could pick it up and at least give you something to chase after

4) If you are on Paris you should use the Service Graph Connector for SCCM which has the same functionality as the older Plugins - the Service Graph Connectors are the way to go moving forward.

Hope some of this helps.

-Akash

[ayman_h]

Thanks Akash, those are helpful pointers!

[mikewhalley1]

Hey Akash - does Service Graph Connector for SCCM require an ITOM Visibility subscription?

[ayman_h]

Mike, 

Looks like you will need ITOM and Discovery licensing or ITOM Standard

Thanks,

Ayman