Skip to main content
Solved

Patch Revision data out of date?

  • January 17, 2018
  • 6 replies
  • 19 views
rstasel
Forum|alt.badge.img+13

Hi All,

I've noticed on our 9.100 install that patch reporting data is out of date.

Casper thinks is current for Chrome is 63.0.3239.84, but 63.0.3239.132 is actually current.

I’m also noticing Flash doesn’t know about latest version. 28.0.0.137 came out on the 9th (of January, 2018).

Anyone else seeing this?

Best answer by rstasel

Restarting Tomcat fixed for us...

6 replies

rstasel
Forum|alt.badge.img+13
  • rstasel
  • Author
  • Valued Contributor
  • January 17, 2018

This seems to show what our install has is indeed current with jamf... seems like jamf hasn't updated updated to reflect these versions.

https://jamf-patch.jamfcloud.com/v1/software

Anyone have any info on what's up?

S
Forum|alt.badge.img+8
  • StoneMagnet
  • Contributor
  • January 17, 2018

@staze Looking at that link I'm seeing that Chrome is version 63.0.3239.132 last modified on 2018-01-04T20:31:32Z, and Flash Player is version 28.0.0.137 last modified on 2018-01-09T07:00:19Z. My JSS (version 9.100) is reporting the same versions under Patch Reporting.

rstasel
Forum|alt.badge.img+13
  • rstasel
  • Author
  • Valued Contributor
  • January 17, 2018

Interesting. Yeah, now I'm seeing the same.

Talking to JSS admin, looks like Tomcat is having issues reading SSL certs from DB. Gonna try cycling tonight.

Thanks!

dstranathan
Forum|alt.badge.img+19
  • dstranathan
  • Valued Contributor
  • January 17, 2018

I see the same thing for Adobe Flash and Oracle Java 8 on my JSS (9.99)

rstasel
Forum|alt.badge.img+13
  • rstasel
  • Author
  • Valued Contributor
  • Answer
  • January 17, 2018

Restarting Tomcat fixed for us...

dstranathan
Forum|alt.badge.img+19
  • dstranathan
  • Valued Contributor
  • January 18, 2018

Restarting Tomcat worked for me as well. Patch Reporting appears to be up-to-date again.

Terms & ConditionsCookie settingsAccessibility statement