OPSI 4.3 – Clients Added Successfully but Unable to Install Packages or Fetch Inventory (Client Service Failing)

[MNJ]

Hello everyone,

I’ve been struggling with an OPSI setup issue for a few days and would appreciate some guidance from the community.

Environment

• Server OS: Tried both Ubuntu and Debian (same issue on both) as well as pre built official VM

OPSI version: Latest release

• Client OS: Windows (multiple versions tested)

• Network setup: Clients are reachable, added successfully in OPSI Configed, and show up as online

• Packages tested: hwsetup, swsetup, etc.

• OPSI agent / client service: Installed successfully and visible on client machines

Problem

Even though:

• OPSI clients are successfully installed and registered on the server

• opsi-script and client agent installations complete without errors

Still:

• I can’t install any OPSI packages like hwsetup or swsetup on clients

• No hardware/software inventory is being fetched from Windows clients

• Client-side OPSI service keeps failing or not starting properly

What I’ve Tried

• Verified network connectivity between server and clients (ping and RPC access fine)

• Reinstalled OPSI server from scratch (tried both Ubuntu and Debian)

• Reinstalled client agents several times

• Verified file share access (\depot-server\opsi_depot) - gets blocked due to Windows guest access policy

• Tried changing map to guest = bad user and other Samba configs

• Ensured opsiconfd and opsi-webservice are active and running

Despite all this, the clients remain stuck — I can’t trigger or complete any installations, and inventory data never syncs back.

Also one more point to mention is that during client installation in windows at some point there is an error occuring where client trying to access custom packages/files from server but failing and skipping.

Any help, hints, or working configs would be really appreciated. I’ve tried most standard troubleshooting steps but no luck so far also manual has nothing related to such issues.

Thank you in advance!
— Manoj

[n.doerrer]

Hello Manoj and welcome to our forum,

please take a look at C:\opsi.org\log\opsiclientd.log for problems with package installation on client side.
Everything starting with "[3]" is an error and might contain a clue to what the actual problem is.

Are you working with the latest versions of "opsiconfd" on serverside and "opsi-client-agent", "opsi-script", "hwaudit" opsi-package wise?

Best,
Nils