Planehazza Posted June 18, 2024 Posted June 18, 2024 Anyone else? Lightspeed Filter Agent service stopped, so internet access blocked. On some cases it causes Google Drive client to load resulting in the renaming of their local DriveFS folder being required.
TechMonkey Posted June 18, 2024 Posted June 18, 2024 Interestingly IDEX on Smoothwall seems to be having fun on our site. I've swapped domain Auth to higher priority to get us working.
Planehazza Posted June 18, 2024 Author Posted June 18, 2024 We've had intermittent issues with lightspeed filter for a good while now and the latest version promises to fix the issue, but it always returns. The fact that it happens in bulk like today where, we think, a Windows update had stopped the service and it failed to restart. We have a GPO that forces the service to auto restart on failure but it hasn't fixed it. Restarting the PC doesn't help either and the only option is to use services.msc remotely to manually start the lightspeed filter agent service. Lightspeed have been very supportive, but we're struggling to capture useful logs because anecdotally this doesn't seem to repeat on the same device often. So right now, I have no idea what the cause is. Event viewer just shows a typical 101 error to show the service stopping but this is logged when the PC shuts down and so gives us nothing useful other than to say the service stopped... We're running the Windows Agent 2.6.3 as well as chrome extensions, but depending on what article you read on their site this is both recommended and not recommended. Their AI chat helper is very good at understanding my questions and it says I should be running both as we are. So I'm quite frustrated and confused.
finlay Posted September 26, 2024 Posted September 26, 2024 Has anyone else rolled out 2.6.7 and having issues since yesterday?
ibpalle Posted September 26, 2024 Posted September 26, 2024 Interestingly IDEX on Smoothwall seems to be having fun on our site. I've swapped domain Auth to higher priority to get us working. Just an aside, moving AD above iDex allows thew AD group mappings to be used, rather than the iDex group mappings. Before iDex agent 2.3.5 there were cases of group mapping lookup failing. The user activity should show iDex user info still incoming? 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now