You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configuration of these agents is OK since simply restarting the service manually makes everything back on track. So, I've the following hypothesis regarding to what happens to these agents:
User boots his computer;
OCS Inventory Service starts the agent;
Agent fails to contact the OCSI server because the networks isn't up yet (we currently need an active VPN session to contact our OCSI server);
Because the agent failed to contact the server, the OCS Inventory Service stops until next reboot.
Do you think this could possibly happen?
The text was updated successfully, but these errors were encountered:
It's hard to solve a problem when important details are missing, that why we added this template, to help you and us.
General information
Operating system : Windows 10
OCS Inventory information
Windows agent version : 2.9
Problem's description
I regularly have agents which stop contacting the server.
Initial troubleshooting has shown this is often due to the "OCS Inventory Service" being stopped.
Further analysises show that those agents often (always?) have the following error line in their logs:
The configuration of these agents is OK since simply restarting the service manually makes everything back on track. So, I've the following hypothesis regarding to what happens to these agents:
Do you think this could possibly happen?
The text was updated successfully, but these errors were encountered: