Java Pak Updates April 8, 2014

[Lost_In_The_Paradigm]

Can you elaborate on the functionality of the recent updates to the JavaPaks? It seems like our prompts are already going away with the settings we have, but if there is something missing that will really suppress the expiration check on the 15th, I need to know. (Our time is obviously short at this point in time. We have business critical testing starting on Monday, and the Oracle update is to occur on Tuesday.)

[Salman]

"JRE out of date" prompt was handled in the updates. Older version writing the values in Java's deployment.properties file only. And, recently some customers reported that they still see the prompt on client machine once they set it to prevent that popup.

Our tests shows that it requires additional step and that was to add the property "deployment.expiration.check.enabled" as registry key as well.

Now updated Pak will deliver both... in deployment.properties and writing that registry key.

Sal Younis
PolicyPak Software Technical Support

[Lost_In_The_Paradigm]

Thanks for that info. You wouldn't happen to know if this update maintains the lowercase 'F' for the false selection of that setting, would you? In the properties file and the registry?

[Salman]

Yes I know and updates do maintain the lowercase for false.   

Sal Younis
PolicyPak Software Technical Support

[Sponsored content]