So after a few weeks of back and forth on Windows devices (Windows 10 and 11), where I had installed the n10 MP, I finally made a breakthrough.
So while not documented, there is a pre requisite before installing the n10 MP on these device types. And it is Windows Location services.
It seems that Windows location services manages who/what can get the BSSID information and get the host information to populate the data in the Wireless and Host graphs in the Delivery>Network Paths.
So in short, before deploying n10 MP's ensure that your Windows Location services are Enabled(Turned On).
If you have already deployed the n10, the shortest fix to get it working seems to be:
- Uninstall Appneta Monitoring Point.
- Delete the folder "C:\Program Files\AppNeta"
- Either delete the MP from the AppNeta console ( Or when the agent checks in again it will use a new name) or migrate once checked in
- Enable Location Services in Windows,
- Re-install AppNeta on the device. (Make sure to run as administrator)
- Open the services applet, and stop the AppNeta service.
- And now Start the AppNeta service, and all should be working :D
Now based on if you wanted / needed to preserve the monitored data / paths that the device had already captured, you may want to migrate monitoring to the new device MP name.
The reason for all this seems to be linked to the following information / article:
API behavior for Wi-Fi access and location
Changes to API behavior for Wi-Fi access and location - Win32 apps
I Hope this helps everyone else who may have run into this issue.
------------------------------
KR,
Chris
------------------------------