Comments
-
Either put patch manager into debug mode and review the logs in program data folder or look at the exception tab for the job
-
-<sdp:ApplicabilityRule SchemaVersion="1.0"> <bar:FileVersionPrependRegSz Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe"Value="Path"RegType32="false"Path=".\msedge.exe"Comparison="LessThan"Version="110.0.1587.41"/> </sdp:ApplicabilityRule>
-
-<sdp:ApplicabilityRule SchemaVersion="1.0"> <bar:FileVersionPrependRegSz Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe"Value="Path"RegType32="false"Path=".\msedge.exe"Comparison="LessThan"Version="110.0.1587.41"/> </sdp:ApplicabilityRule>
-
SolarWinds repository for OpenJDK should be using https://adoptium.net/temurin/releases/?version=8 as stated in the upstream repository. OpenJDK 8u342 GA Release is last release being provided by Redhat
-
Through WMI I look at if it has a battery installed. "BatteryStatus <> 0"
-
If you download the appx bundle with all the required runtimes, along with the license, then yes you can install it from command prompt.
-
If you download the appx bundle with all the required runtimes, along with the license, then yes you can install it from command prompt.
-
You can create your own custom package that includes the edge msi. I used a registry value to point to the msedge.exe to compare versions.
-
You can create your own custom package that includes the edge msi. I used a registry value to point to the msedge.exe to compare versions.
-
From your vague information I assume msu file. You will have to call it from package boot. pretty sure if you search you will find information on those files on being deployed.