This has turned out to be a non-issue that only affected the system I was working on. I have logged into another ARM64 machine and ipmiutil works in-band as expected. Sorry for the false alarm. Thanks Andy and Hozefa for enabling this platform!
Thanks for the quick response as always Andy! C:\Windows\System32\drivers\IPMIDrv.sys does exist. It does load the ipmi driver according to driverquery: IPMIDRV IPMIDRV Kernel But it seems the part that is missing is the Microsoft_IPMI WMI classes. I am surprised these are platform specific. As a sanity check, when I try to instantiate this WMI class on server 2019 x86_64 it works: PS C:\Users\Administrator> $CimSession = New-CimSession PS C:\Users\Administrator> $ipmi = Get-CimInstance -Namespace...
ARM64 Windows Server 2019 does allow the program to run, but when I try to run commands against the local BMC, I am unable to get the driver to load. Any special workarounds needed for the KCS interface? Or, could this be some signing issue? Thanks! Here is the output from ipmiutil config -x: ipmiutil config ver 3.13 ipmi_open: driver type = ipmi_open_ia: error opening \.\Imb to imbdrv.sys ipmi_open_ms: cannot open microsoft_ipmi driver (ipmidrv.sys) ipmi_open rc = -16 type = Driver type , open rc...
Added support for hours in ClockTime class. Enabled all display calculations.
Added Linux build and readme.txt
Set title, added Windows 64-bit icons and build scripts
Removed some debugging statements to prepare for release
Added GPLv3 license