10/23/2018 342 views
Has anyone had any luck discovering and provisioning printers using SNMPv3? We are able to discover and provision successfully with v1/v2. We are also able to discover the same devices using SNMPv3 in other applications like HP Web Jetadmin and Ricoh Device Manager. But when we try the same devices and setting in KACE the SNMP Test fails on the discovery.
Answer Summary:
1 Comment   [ + ] Show comment


  • I'm having the same issue, I have 2 HP Copiers in two locations, SNMP 1/2 disabled, SNMP 3 configured identically. Neither can be contacted via SNMPv3.

    I've got ESXi hosts working via SNMPv3, but not HP Copier/Printers...
    • the best way would to contact the HP support, if SNMPv3 works well with other products it seems the SNMPv3 implementation is problematic

Answer Chosen by the Author


I ended up opening a Service Request with Quest Support. If the device requires a Context Name like all of our HP printers KACE is not able to discover it using SNMPv3 since there is no field for the Context Name when setting up the Credential in KACE.

Answered 11/23/2018 by: abeckloff
White Belt

All Answers

this is not a problem, the printer who speak v3 work well. Unfortunately most of my printers don't speak v3.
Answered 10/24/2018 by: Nico_K
Red Belt