Hi Everyone ,
For those of you who are using SCUP to update java need to be careful for one very important scenario which might leave your client ( Servers in my case ) without any version of Java . We faced an issue last week when we had a patching window and since we use SCUP for managing third party updates we were also upgrading Java to latest version Java 8 update 111 . I have done the explanation through flowchart to get a better understanding of the issue .You can go through the flowchart attached here to get a clear view .
So what this flowchart means is when deploying Java you need to fix failures with that change window else when you miss the window , the system will start showing as complaint as the status message will be sent that system does not require Java when the software update compliance cycle runs and it leaves your system without any version of Java .
If you using using SCUP then you can also check your SQL database if any previous Java installation was done in that period to be sure . You can find the query in the script section of my blog or you click on the following link :
Query Name :
SQL Query for checking updates installed on workstations or servers in the last 60 days
If you do not have access to the SQL database you check in the event viewer of the client in the applications tab .Just do a search using Java as the keyword :
So in this way you can find if Java install ever failed or was Java never installed on the client . The SCCM logs will be overwritten by the time you notice the missing Java version .
Hope this helps 🙂
Leave a Reply