admin
Forum Replies Created
-
Posts
-
This new version of Check WMI Plus will fix all your issues
This new version of Check WMI Plus will fix all your issues
This new version of Check WMI Plus will fix all your issues
We are going to keep having problems with wmic unless it is fixed properly.
Please see this post https://edcint.co.nz/checkwmiplus/long-term-fix-for-wmic-keeping-check-wmi-plus-alive/
This is great. However, we are going to keep having problems with wmic unless it is fixed properly.
wmic needs a rebuild. I have no idea if you are able to do such a thing but let us know.
Please see this post https://edcint.co.nz/checkwmiplus/long-term-fix-for-wmic-keeping-check-wmi-plus-alive/
We are going to keep having problems with wmic unless it is fixed properly.
Please see this post https://edcint.co.nz/checkwmiplus/long-term-fix-for-wmic-keeping-check-wmi-plus-alive/I also noticed the error messages today. It appears that the wmic calls still work though
The error message is
The server-side authentication level policy does not allow the user DOMAIN\USER SID (S-SIDDETAILS) from address a.b.c.d to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.This seems to be related to
https://www.csoonline.com/article/3622168/how-to-test-the-impact-of-new-windows-dcom-server-authentication.html
and https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769cI don’t yet know if something will stop working at some point because of this.
Whilst the error message does say “raise the activation authentication level … in client application” this would need someone to poke around in the wmic source to fix this.
On the Rapsberry Pi that gave me a successful compile I believe this is what I had previously done:
– install Pi OS Buster via Noobs
apt-get update
apt upgrade
apt-get remove sonic-pi minecraft-pi wolfram-engine wolframscript libraspberrypi-dev libraspberrypi-doc libraspberrypi0 pigpio
apt-get install libwww-perl openvpn monitoring-plugins-basic libraspberrypi-bin speedtest-cli snmp libmicrohttpd12 inotify-tools
cpan install Linux::SysInfoI have also just compiled it on a Raspberry Pi. You can see the result on this page: Installation Terminal Session Raspbian Buster
Since Raspbian is Debian-based, I thought I might have issues but, no, it just worked first time.
To answer your question about “who maintains the wmi package” – well, the answer is no one does. When it first broke for Windows 10 v2004, I made contact with the Samba team (which is where it first appeared) but they no longer maintained it and it had just been collecting dust.
Given that it worked on Raspbian, I suspect that it should be possible to make it work (without changing the source). I think you are going to need to find someone who has a really good understanding of how the compiling works to help you out.
Also, given that when I did the Fedora 33 compile, it had so many warnings and even ended in an error BUT still produced a working wmic binary, you may be able to fiddle around with the compile and still make it work.
I have shown how I compile it using Fedora 33 on this page:
Installation Terminal Session Fedora 33This problem is fixed as per Fix for Windows 10 v2004
