forum.opsi.org

The error "Could not open opsiclientd pipe \\.\pipe\opsiclientd: 2" means that the opsiclientd service has not yet created the named pipe. This is a normal occurrence and not a cause for concern.

The error "Failed to open Service Control Manager (error=5)" means that the opsi-loginblocker does ...

Hello,

you can check the logfile c:\opsi.org\log\opsi_loginblocker.log to see if it contains any clues about the cause.
Please note that opsi 4.2 has reached End-of-Life, so I strongly recommend upgrading the environment to opsi 4.3.

Best regards,
Jan Schneider


Thanks for the reply Jan

It ...

opsiclientd v4.2.0.159
opsi_loginblocker v4.2.0.5

Hello!

We've encountered a strange issue in our environment, where on some clients (we haven't been able to find a common thread yet) opsi_loginblocker never unblocks login, leading to these clients becoming unusable.

It is possible to execute ...

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 ...