I asked something like this earlier but didn't get a working solution:
This is on a peer-to-peer network - so no Server and no global GPOs. All of the settings have to be on individual workstations.
We're using ManageEngine EventLog Analyzer (ELA) for SIEM which uses WMI for workstation monitoring.
All of the workstations, including where ELA is running are Windows 10 Pro.
In the past, I had ALL of the computers being monitored successfully.
Over time, the number of computers which "connect" at the monitor computer has dwindled to around 50% - so something has changed.
The change must be on the computers being monitored because half of them still work fine at the monitor end.
To simplify the question, let's stick with the results from WBEMTEST and forget about ELA for now.
It appears that all of the recently "disconnected" computers will no longer connect using WBEMTEST. I know this is more widely known and documented.
I originally created a checklist and a script to make most of the workstation settings. Using them no longer allows successful connections.
All of the workstations are now at Windows 0 Pro 1709 16299.309.
So why do some work and others not work? I've not found a common thread.
Lately, I've taken to trying various PowerShell inter-computer commands to see if that might shed some light. So far, no joy.
I've tried WMIC commands such as
cpu get systemname
For a computer that still connects, I get a valid response.
For a computer that no longer connects, I get "Access is denied".
I'm looking for a near-term solution for this peer-to-peer network; not a longer-term Server-based approach for now.
Any suggestions would be greatly appreciated!