Any way to test for Java availability before pushing update?
We're trying to update our multiple Java 7 versions in a single job but the pre-deployment task doesn't seems to be able to handle wildcard or partial software name match like "Java 7 update".
Our goal is to update all of our current Java 7 installation (v10 to V72) to the latest version (v75) but we also want to avoid deploying Java 7 on computers that don't already have it.
Is there a way to achieve that?
We have to do this on both XP and Windows 7 x64 computers.
Topic Participants
Stephane Savoie
J leonard
New to M365 Manager Plus?
New to M365 Manager Plus?
New to RecoveryManager Plus?
New to RecoveryManager Plus?
New to Exchange Reporter Plus?
New to Exchange Reporter Plus?
New to SharePoint Manager Plus?
New to SharePoint Manager Plus?
New to ADManager Plus?