I hate to revive an old thread, but I’m also getting the error. It happens with a 5 year old client that’s in place plus the 0.4.1 client… But I noticed it seems to happen more so on the clients with lots of other nagios checks going on (but the other checks work as expected). Its not using a power shell script but a check windows update.wsf and works fine if run on the client using nscp test
I’m getting the same .hop error in the logs, and its driving me nuts.
I’ll double check the INI (using nsc.INI since its updated from a way old client on the test clients with the new nsclient++ version)