Jump to content

Recommended Posts

Posted

Hi

 

Has anyone else had issues with their SBB Netsweeper agent not starting? We're just having this randomly happening to us. It's hard to monitor as staff only become aware when they can't use YouTube because it's blocked by the KS3 filtering policy. When you look at the machine there is no NS agent in the taskbar. We can push it out again, or restart the machine to resolve but would like to know why it's happening.

 

We've got a call open with SBB and RM and have installed the latest agent. It looks like the service isn't starting but I don't know why not.

 

Thanks for any help!

Posted
Hi

 

Has anyone else had issues with their SBB Netsweeper agent not starting? We're just having this randomly happening to us. It's hard to monitor as staff only become aware when they can't use YouTube because it's blocked by the KS3 filtering policy. When you look at the machine there is no NS agent in the taskbar. We can push it out again, or restart the machine to resolve but would like to know why it's happening.

 

We've got a call open with SBB and RM and have installed the latest agent. It looks like the service isn't starting but I don't know why not.

 

Thanks for any help!

 

 

Yes, my MSP says it's a windows update born issue - possibly Nov/Dec updates, we haven't got a fix other than creating a scheduled to task to start it every 10 minutes.

Posted

Yes. Very often.

 

I have a start up batch now to force it, but has the WAgent MSI been changed to use WAgent as a service? There is an option in the MSI under the Property table called NS_WAGENT_SERVICE, default is 0, I set this to 1.

 

Its worked on 99% of our machines, however I still use the script in one instance and it just runs the installed EXE with the the WAgent args, works perfectly fine, but its a simple start "" etc.

 

Its been that way for me since like February 2021 :(

Posted

Yes I had this issue with SBB Netsweeper Wagent too for the past year.

Support just passed it off as a O/S issue and assured me the MSI was fine.

Ticket closed and went down the script route in the end

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...