Clone machine do not connect to the HOST (4283658)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Clone machine do not connect to the HOST
Description
Cloned machines or newly imaged machines do not connect to the KACE SMA, even after reinstalling the agent.

The following error might be present in the konea.log found in C:\ProgramData\Quest\KACE
```
CryptAcquireCertificatePrivateKey returned 0: Keyset does not exist present
```
Cause

The issue is caused by the cloning process followed, and when a sysprep is not run on the clone machine, Therefore the SSL certificates, KUID, and registry get a cloned over to the new system and does not allow the install agent to provide its own Identifying signature to register or reach the appliance correctly, even after completing an uninstall and reinstall process of the agent.
Resolution
To avoid this issue, make sure the image used to provision new devices does not have a previous KACE agent installation and/or left overs of it.

To correct this issue, follow the process down below:
1. Go to the affected machine, and open CMD as admin:
2. Type certlm.msc | hit enter.
3. Go to Action | Find Certificates...
4. Search for certificates which: Contains: konea | Look in field: Issued by
5. Delete the results found
6. Once all certificates have been removed, do a clean installation of the agent once again
For agent uninstallation instructions see the following kb: How to manually remove KACE Agent on all Operating Systems

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title