OPSI clients spontaneously disconnect from server

[mart660d]

We manage around 450 Windows 10 clients using the locally hosted ready-made opsi-server (version 4.2.0.72-1) running on a VMWare virtual machine.

Every now and then, some of the clients will stop communicating with the server. When diagnosing the client, we can see that opsiclientd.exe does start automatically without errors, and the client has connection to the server when the software kiosk is launched. Then as soon as an update/installation is begun via the kiosk, the client will also start configuring whatever was queued before the kiosk software.

There are seemingly no glaring issues to be seen, and when this one problem isn't happening, everything else runs just fine. Could it be an issue with this specific version of opsi-server/opsi-client-agent?

[n.doerrer]

Without more information this is hard to pinpoint. We always recommend to keep the system-packages on the server up to date and the same goes for opsi-packages on the clients.
Does this problem occur with the stable 4.2 opsi-client-agent+opsi-script and stable 4.2 opsiconfd+opsi-server?

If so, the error text (or whole log for context) in c:\opsi.org\log\opsiclientd.log would be the place to look for the cause.