CMDB Printer Discovery vs 3rd party SG Jamf Import
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 03:42 PM
Hey CMDB experts,
First off, I am not an expert. We are having a printer discovery issue. We use ServiceNow native discovery with SNMPv3 to populate our network printers. This is working well. The problem is that we also use the SG-Jamf integration to import Mac laptops into CMDB. SG-Jamf also brings in printers if present on Macs. If a user has configured one of our network printers on their Mac, it get imported, but with the wrong IP address. Is there a way to block the importing of printers for the SG-Jamf integration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2024 10:11 AM
If your objective is to ensure that existing printers are identified correctly and only the data which you trust from JamF are updated by JamF SG integration, then you must do the following 2 things:
1. Review the identification rules for 'Printer' class. Go to CI class manager, open the Printer class and click on the 'Identification rules' tab to do this. Then check whether you need to update the identifier entries by considering the set of unique attributes for Printers from both discovery and JamF integration. The following URL has details about identification rules:
2. Configure the reconciliation rules for 'Printer' class. Go to CI class manager, open the Printer class and click on the 'Reconciliation rules' tab to do this. For example, you can either set discovery as a higher priority source than JamF for 'IP address' attribute to prevent overwriting or keep only discovery as the source for IP address (this totally preventing JamF from updating the IP address). The following URL has details about reconciliation rules: