Geoff Cottrell

Just tested the hotfix. It works great. Thank you!

Thank you Andy. You are an ace!

Hi Andy, I don't want to cause you any extra work... If you will be releasing a version 3.0.8 that has this change in it sometime this month (forgive me please, I do not know what the release schedule is...), that would be fine. But if it's not a big deal to roll the hotfix, I would be both grateful and happy to do so. Thank you! Geoff

Hi Andy! Yes, my Windows Server 2016 machine has the USERPROFILE set to C:\Users\<MyUserName>, so I think the porposed fix you mentioned in this thread would be very helpful. Again, thank you very much for getting back to me! Geoff

Thank you so much Andy! I am "new" to the WIndows Server configurations, so I missed the file permission issue until I looked at where the error was printing in the source code. For some odd reason we need to use the -J 3 option on a handful of servers to ensure reliable IPMI communications. So for now I will try to enforce the use of Administrator. I do see the %USERPROFILE% variable in the user Path variable, so I will play with this a little to see how it's set and I will post up here again when...

Good afternoon, I am hoping someone can help shed some light on an issue I am having with running ipmiutil version 2.99 for Windows. The problem I am having appears to be related to Windows Server 2016 (build version 1607). Other versions of Windows 10 (and Windows 7) appear to be working fine. For example, on Windows Server 2016, when I run the following command: ipmputil.exe health -N 192.168.xxx.yyy -U uname -P pword -J 3, I get the following error: ipmiutil ver 2.99 ihealth ver 2.99 Opening lanplus...