KACE Product Support

For example I have a test machine with Java 7 update 25. It is in the first schedule "Production Detect and Deploy Patches to All Laptops. When I look at the Inventory entry it shows that the only patch detected is Java 6 update 45, but that hasn't been installed yet. Here is what the schedule looks like:

Patch Action: Detect and Deploy
Machine Selection: Three individual machines listed
Operating System: Windows
Limit Detect To Selected Patch Labels: Java to Deploy
Limit Deploy To Selected Patch Labels: Java to Deploy
Max Deploy Attempts: 3
No Alerts
Patching Progress is set to show
Reboot Options: Force Reboot
Patch Schedule: Every day at 12pm
Schedule according to Server Time
Run on next connection if offline
Delay Schedule by 60 minutes

Here is the SQL for the Java to Deploy Label:
select UID
from KBSYS.PATCHLINK_PATCH
where KBSYS.PATCHLINK_PATCH.TITLE like '%Java%'
AND PLATFORM_ID != 7
AND DATEDIFF(NOW(), KBSYS.PATCHLINK_PATCH.RELEASEDATE) > 30 - lmland 11 years ago

Here's what I have for my Java Older Than 30 Days label:

select UID from KBSYS.PATCHLINK_PATCH where ( KBSYS.PATCHLINK_PATCH.TITLE like '%java%')

AND RELEASEDATE<DATE_SUB(now(),INTERVAL 30 DAY)

What is the PLATFORM_ID!=7 referencing? I'm not familiar with that.

When you view your label, does it show you Patches being in it? My Java+30 day label shows 137 patches - rockhead44 11 years ago

PLATFORM_ID != 7 means it doesn't get Mac patches. We are not patching macs in our environment. I believe Windows is 1. I have the same number of patches in that label. - lmland 11 years ago

Imland,

Ok, so you've verified that the JRE 7 u 40 is in the Patch Label that is pointed at this machine, in either a Deploy OR a Detect & Deploy schedule. Next, either find that patch in the Patch Listing, click on it and look to see what the status of that patch is WRT the specific machine, OR find that machine in Inventory, click on it, and see what the status of that patch is.

Ron Colson
KACE Koach - ronco 11 years ago

I already posted a screenshot of the status of the targeted machine below. It lists Java 6 u 45 to be deployed, but hasn't yet installed it. It does not list Java 7 u 40 and the installed version of Java is 7 u 25. - lmland 11 years ago

I have a support ticket with KACE about this. They said it seems like a weird problem. Test machine detected patch for 6 u 45, but it should be detecting 7 u 40 or 45. They are looking at debug logs. I will share more info when I have it. - lmland 11 years ago

We've been in contact with a KACE rep about this for a couple of months--no solution so far. We were eventually transferred to a higher tier of engineers, but we've been told their pretty busy and can have no definite resolution timing. Interestingly enough (referring to Dell system updates), for us, we can push patches and updates on a computer if it is done individually, however, when we do a group push, the file that is deployed to each machine inside of c:\programdata\dell\KACE\dell, .part files are generated. We don't know if this is the cause or not, or a result of something broken, but it looks like the exe file gets corrupted when the group push is enabled. We hope to find a solution, or at least find out what's wrong soon... - adammitch 11 years ago

Yeah, I was working with support all last week and am now getting bumped up to tier three. I have narrowed my patching schedule down to a single machine and only pushing java updates and it still isn't working. They have unistalled agent, redownloaded patches and had me reimage my test machine without using the k2000. Nothing works yet. This seems like a major problem. I can't believe that this issue is a low priority when it is such an important feature of the software. I might have to start ramping up the pressure, especially if it's not just me. - lmland 11 years ago