Automate Install Microsoft Build of OpenJDK with PowerShell #278
|
Due to security requirements, we need to upgrade java 8, 11, and 17, every month on 100s of servers running Windows 2012, 2016, and 2019. We are trying to automate the process using PowerShell.
|
Replies: 2 comments 16 replies
|
Hi MSIH LLC (@MSIH), You can use the following command in PowerShell to download a JDK: Invoke-WebRequest -Uri https://aka.ms/download-jdk/microsoft-jdk-17-windows-x64.zip -OutFile jdk-17.zip -UseBasicParsing
Expand-Archive -Force jdk-17.zip -DestinationPath c:\
Remove-Item jdk-17.zip -ForceAll vanity URLs are published here: https://docs.microsoft.com/en-us/java/openjdk/download-major-urls |
|
Thanks for the example. We are doing something like this already. The problem with the ZIP files is when you expand it you get a folder that includes the Java version number. Which makes setting the Path and JAVA_HOME more difficult. The MSI file takes care of both setting and removing these environment variables. Expand microsoft-jdk-11.0.15-windows-x64.zip and you get \jdk-11.0.15+10 |
|
So, you saying it would be good to have a URL download for the MSI package, without the minor version? The other approach is to simply rename the folder extracted from the ZIP to something you already have set in your Renaming an object without its full name (possibly using regex), is possible with Powershell. We may be able to add vanity URLs for MSI packages in July. |
|
If you plan to roll out sich a thing to hundreds machines you should locally archive and test it anyway, which makes a re-packaging step quite easy. So yes it would be good if Powershell could skip parent folder in archives, but for your process that won’t fly. Not to mention checksums, signatures, pre-config and hardening. Since in place updates are not so atomic, expanding to a new dir and setting environment variables (in Powershell) sounds however like a good approach (second best would be a symlink - much better than replacing files of a running application. |
|
I'd also recommend utilizing winget to manage this. > winget install Microsoft.OpenJDK.17An advantage of using winget is that you can easily update to later version numbers by simply running: > winget upgrade Microsoft.OpenJDK.17Both of these should probably be executed from an elevated PowerShell instance or you will receive UAC prompts, but winget seems like a very reliable way to manage things. |
|
I am not sure I understand the logic of not publishing the msi files and all the LTS versions of java (8,11,17) on the vanity URL page. They already have the files and probably the automation. The URL on that page are only for Windows and windows uses MSI to install programs and tools. |
Windows MSI Major Version Vanity URLs v1.0✅ Windows 11 MSI x64
✅ Windows 11 MSI AArch64
✅ Windows 17 MSI x64
✅ Windows 17 MSI AArch64
...we will allow our hero Bruno Borges (@brunoborges) to publicize these in a more fashionable manner upon his return. |
|
Thank you |
|
When are you going to up this page: https://docs.microsoft.com/en-us/java/openjdk/download-major-urls |
|
Thanks for the reply (and admittedly, the reminder that I need to follow through and add this to the public page!). However, we are in the midst of a re-spin of the 17 and 11 binaries so all release activity will be completed (re-completed?) in the next week or so, and at that time I will update this page. For the interim, please use the links above in this issue. |
|
This is complete now (updated it some time ago, just after our respin release). |
I am not sure I understand the logic of not publishing the msi files and all the LTS versions of java (8,11,17) on the vanity URL page. They already have the files and probably the automation. The URL on that page are only for Windows and windows uses MSI to install programs and tools.