JDK policy keeps running

jonlju
Contributor

Hi,

We have a policy set up to automatically upgrade to the latest version of the Java Developer Toolkit.
We get the new package from AutoPkg and then run it through a scoped policy.
The policy should exclude all members of a Smart Group that contains computers running JDK 111 or 112.

One machine however keeps getting the package installed through the policy on the recurring check-in trigger (every 15 minutes). For some reason it never moves to the Smart Group so the policy keeps installing the application, despite the policy also running a forced recon afterwards to update the inventory.

Have you ever experienced something similar?

1 ACCEPTED SOLUTION

jonlju
Contributor

Hm this is weird though. Patch reporting in the JSS says the client has JDK 8.101 installed, and the package we're distributing is 8.111.
Running "$ /System/Library/Frameworks/JavaVM.framework/Versions/A/Commands/javac -version" returns "javac 1.8.0_111".

Do you know from where the Patch Report fetches the information on the client? While user had three other versions as well, when we moved those and ran a "sudo jamf recon" on the machine it still reported the version as 1.8.101 in the JSS.

View solution in original post

2 REPLIES 2

thoule
Valued Contributor II

This shouldn't be too hard to track down. Start by looking at your smart group criteria, then compare that to the computer's status. I think it is likely that Recon is not running properly, so the JSS doesn't know JDK is installed, and thus the policy is still scoped to that computer. Does the policy run successfully? Is it installed as it should be?

jonlju
Contributor

Hm this is weird though. Patch reporting in the JSS says the client has JDK 8.101 installed, and the package we're distributing is 8.111.
Running "$ /System/Library/Frameworks/JavaVM.framework/Versions/A/Commands/javac -version" returns "javac 1.8.0_111".

Do you know from where the Patch Report fetches the information on the client? While user had three other versions as well, when we moved those and ran a "sudo jamf recon" on the machine it still reported the version as 1.8.101 in the JSS.

View solution in original post