Jamf SGC creating printer devices that are not in Jamf

[Alan Akins]

Hello forum!

In the last week, our Jamf SGC created several "printers" that 

1. Are not records in Jamf (we only have macOS, iOS, and iPadOS devices in Jamf.)
2. Are probably real printers
3. Look like printer connections installed on a Mac...?

• Here's a few examples of the records created. All have Discovery Source="SG-Jamf" and CI class "Printer."
• Serial Number, MAC Address, and Manufacturer are null.
• 'xxx' in the data are for obfuscation.

Name	IP Address
Officejet Pro 8500 A910	dnssd://Officejet%20Pro%208500%20A910%20%5B2D1C1B%5D._ipp._tcp.local./
xxx-WIN-FNP-P18-CON-VP-CLCsecure	smb://xxx-WIN-FNP-P18.xxxx.com/CON-VP-DSNsecure
FMP-WHQ-P11-VP-DSNsecure	lpd://xxx-win-fnp-p11.xxxx.com/WHQ-VP-DSNsecure
Canon iR1018/1022/1023 (UFRII LT)	usb://Canon/iR1018/1022/1023%20(UFRII%20LT)?serial=1976QFNk0024

Does anyone have any idea on how these could get created by Jamf and what I might need to do about it?

Thanks

-Alan

[Will O · Accepted solution]

I recently installed SG-JAMF and observing the same behavior.  I do not see the value in having JAMF data create and update Printer CIs as it typically lacks basic info like model and serial number.  

I created an IRE data source rule for SG-Jamf and Printers to prevent SG-JAMF from creating new Printer records. 

Then I created a Printer class reconciliation rule for SG-JAMF to prevent the discovery source from updating Printer records.  In the reconciliation rule, I chose a single field that I knew was not in the SG-JAMF data since there is not an option to just ignore a discovery source entirely.