/build/static/layout/Breadcrumb_cap_w.png

Discovery of Kace MDM Devices in Kace SMA doesn´t work

I am currently in the process of implementing the Kace MDM in our Kace SMA. I have correctly filled in the discovery schedule with the tenant and the secret key, but I don't get any results when I run the discovery. On our firewall, the tenant's URL is enabled for communication in both directions via port 443. In the log, however, I find the following entry:

[2021-04-09 08:00:07 +0200] Discovery - MDM [notice] KBScanTask->scanNode() - Scan started.
[2021-04-09 08:00:07 +0200] Discovery - MDM [info] KmmDiscovery->DiscoverKmmDevices() - Performing KACE Cloud | MDM discovery.
[2021-04-09 08:00:08 +0200] Discovery - MDM [error] KBScanTask->scanNode() - Error occurred while discovering KACE MDM devices: Curl returned an error: SSL certificate problem: unable to get local issuer certificate
[2021-04-09 08:00:09 +0200] Discovery - MDM [notice] KBScanTask->scanNode() - Scan complete.


Does anyone have any idea why the detection may fail?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 2 years ago
Red Belt
0

the main issue is this:
Curl returned an error: SSL certificate problem: unable to get local issuer certificate


Check if it works now and if not, open a SR with support since the SSL cert of your tenant seems to be expired.

Posted by: CarstenBuscher 2 years ago
Purple Belt
0

Finally it was a problem with the whitelisting on our firewall. There are two more exceptions that has to be made for the european tenant.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ