The ePatching Team will remove Oracle Java Runtime Environment from all systems during the June ePatching cycle. The “\Assets and Compliance\Overview\Compliance Settings\Configuration Baselines\_DOI\Uninstall\DOI-Oracle Java Uninstall” baseline is available through SCCM and will be used for this removal process. Sites should notate any dependencies on the Oracle Exception sheet ahead of the June ePatching cycle to assure the application is not removed. Sites should reference the notification sent out on March 28, 2019 titled “[Update] Oracle Java open-source (free) End of Life (EOL) – Action Required” for additional information. For systems that require an installed Java application, the x64 and x86 versions of the Amazon Corretto client named “2-DOI-Amazon Corretto 8.212.04.1 “ have been made available through SCCM.
- Oracle Java will not be removed from Windows Servers through the June ePatching process. Sites are still expected to remove Java from unlicensed servers.
- Oracle Java will not be removed from systems listed on the Oracle Exception sheet during the June ePatching cycle. Since Java removal will be enforced with and SCCM baseline, local IT will not be able to re-install Java on systems unless the ePatching team marks them as exceptions.
Oracle Java will not be removed from USAccess LAS/MSU systems running USAccess Network Test tool version 7.x and 8.x
For more information, see the Oracle Java JRE End of Life page:
https://tst.usgs.gov/misc/end-of-life-software/oracle-java-jre-free-version-end-of-life/
