/build/static/layout/Breadcrumb_cap_w.png

Kace - Windows updates not working (w/ Screenshots)

*Sorry in advance for so much info (brain overload) at once.  Just wanted all info in 1 spot...

**I failed to mention that for this test below I only have 1 client in the device label.  This client only has Windows 7 64bit ent - fresh out of the box, and will not update with the schedule or by choosing "Run Now".

I can not find where or why Kace is no longer updating Windows on test clients.

Some updates below say Active, but did not download and the file size is 0?  Please check the screenshots and see what I may be missing.  Of course any help is appreciated!



----------------------------------------------------------------------------------------------------------------------------------



------------------------------------------------------------------------------------------------------------------------------------------



 

------------------------------------------------------------------------------------------------------------------------------------------


------------------------------------------------------------------------------------------------------------

Device Label:



-----------------------------------------------------------------------------------------------------------------------

Patch Label:




-----------------------------------------------------------------------------------------------------------------

Smart Label:


-------------------------------------------------------------------------------------------------------------------------------







2 Comments   [ + ] Show comments
  • How is the label "(ADM) !Clients" applied to patches? - JasonEgg 8 years ago
  • Thanks for your curiosity in helping Jason.
    "(ADM) !Clients" is a device Smart label I use for all clients, scripts and such to separate domain machines and servers.
    Criteria for label:
    Name - does not contain - server
    Name - contains - windows
    IP Address - begins with - x.x - davreh99 8 years ago

Answers (2)

Posted by: davreh99 8 years ago
Orange Belt
0

Found the answer to my snag!

Looks like JasonEgg was on the right path from a comment above.

*Also a Thanks goes out to a Dell Tech that mentioned the same thing within a very short amount of time!

How is the label "(ADM) !Clients" applied to patches?

Removing the last line for the Patch Smart Label was what I needed to do!
That line was to filter what clients this should go to, but not needed as the Schedule has a section just for the Devices/Smart labels for devices.

Thanks again to all that have chimed in to help.

Posted by: rockhead44 8 years ago
Red Belt
0
Have you checked your patch download logs?

Comments:
  • I have, but could not find much info, and that is when I decided to post here. We are currently on version: Server Current Version: 6.4.120756
    Client version: 6.4.522 and I believe the posts I found were outdated. Would you be able to explain what logs and what info I should be searching for? Thanks rockhead44. - davreh99 8 years ago
    • Your system logs. My URL is (substitute your k1000 domain where I have "KBOXNAME")

      http://KBOXNAME/systemui/settings_logs.php?logfile=kpatchdownload_log - rockhead44 8 years ago
      • I believe the GUI way is "Setting" tab on the left and the "logs" on the left. Drop down arrow to Patch download log. Is there a way to export these? I did check through log but I am not sure what to look for. Didn't see any failures or errors that's why I would like to export it, so I can search the log. - davreh99 8 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