/build/static/layout/Breadcrumb_cap_w.png

Kace Patch Waiting to connect

Hello,

I'm new to using Kace, and I didn't have any training, today I was checking my patch updates deployment, and I found many machines weren't able to update and they are either waiting to connect or there was some sort of patch update failure, is there any thing I can do to fix this problem?

yfKhgR.png  

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: h2opolo25 10 years ago
Red Belt
2
Waiting to connect usually happens when the specific PC does is not online.

Canceled would happen if you have it to prompt the user and they canceled it.

Handshake is when the KACE system sees the PC and is trying to open up communications. If it cannot do it for a period of time it will fail.


Most of the time this is caused by DNS. Make sure the DNS name that you are using when provisioning matches with the DNS name of the KACE appliance and also has the same name and valid IP in your DNS server.

Comments:
  • handshake is slightly different:
    It simply checks if all needed files are avaiable locally (signatures and patches)
    If files are missing, it comes to handshake failed.
    It is usually caused by .part files (partially downloaded and failes due to some issues)
    if the still occur, delete the whole c:\programdata\dell\kace\patches\ folder (or at min. the .part inside, bu I like to let redownload ;) ) - Nico_K 10 years ago

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