There are many things that could have gone many different ways, nice approach would be the following:
did the state change occur in the past, or it's constantly critical;
clarify solution version;
VEM OS where agent is installed;
clarify the agent was turned to allowed proxy mode;
calrify any non-nworks test (i.e. via simple event monitor and eventcreate.exe to eventlog) works;
As you could've seen in "nworks Collector: VIC Service Monitor" properties, it relies on a simple Windows service monitor, no rocket science. If it can't do service monitoring, this may be i.e. RunAs profile-related problem on agent. For your convenience, and decrease of response time, I suggest to transfer the conversation from forum to a support queue ticket by e-mailing the copy-paste from this forum page (with answers to questions I put above) to firstname.lastname@example.org
, if you haven't already done so.
For your convenience, you can put myself in cc: of the message so I'll track it, my alias is achernov and you know the domain name. Please feel free to include any additional information (i.e. screenshots) and your contact phone in the e-mail to support.