Depot Server

[siil-itman]

We are trialing opsi to hopefully deploy a (non-365) solution to manage our pc's on remote sites and our remote workers devices.
I've setup the controller in our head office on proxmox and have a number of local clients connected ok. On one of our remote sites, I've deployed a Debian Linux system with Opsi and configured as a depot server. This location has an IPSec tunnel into the head office.

My questions are
For the client on the depot site, do we still use the agent available in the "controller/public/opsi-client-agent/" as the depot controller doesn't have a public/opsi-client-agent folder available

When we run the installer, what do we put as the Opsi Service url, the controller or depot url?

[j.schneider]

Clients always require a direct connection to the OPSI configuration server (controller/API).
So you have to use the OPSI Service URL.
The OPSI depot server can be used to provide installation files for clients at a different location more efficiently.

[siil-itman]

Thanks for that clarification.

Once we have added a device on a depot site into opsi, is there anything we need to do to get it to use the local server over the central one?

[j.schneider]

You can select client in opsi-configed and move them to another depot via context menu.
See also the available Options of the opsi-client-agent-installer:

https://docs.opsi.org/opsi-docs-en/4.3/ ... ion-helper

[siil-itman]

Final question for today (hopefully).

Looking in opsi-configed on Client configuration\Depots, my config server has all the localboot and netboot packages available yet the depot server doesn't. How do i push packages out to the depot server?

[j.schneider]

You need to install the products on the depot.
You can run the following command on your configserver:

Code: Alles auswählen

opsi-cli package install --depots all https://opsipackages.43.opsi.org/stable/windows/localboot/hwaudit_4.3.1.0-2.opsi

[siil-itman]

Once again, thanks for your guidance, I've got a PC and some localboot products on my depot server.
The PC now has the agent and opsi-script installed, but when I set either hwaudit or swaudit to setup and then select "save and execute selected products only", nothing happens, it doesn't show as installed and I get no update on the hardware or software information tabs for the device.

Is there anything I need to set on the depot server to allow me to push out the software?

[j.schneider]

Do you see a green checkmark in the "On" column of the client table?
Most likely it's a time synchronization issue between the server and the client.
The clocks on both systems should be synchronized as closely as possible.

[siil-itman]

Time is ok but we I am seeing in the devices logs is as follows

Code: Alles auswählen

Traceback (most recent call last):
  File "opsiclientd\EventProcessing.py", line 1040, in processProductActionRequests
  File "opsiclientd\EventProcessing.py", line 1187, in runActions
  File "opsiclientd\EventProcessing.py", line 552, in mountDepotShare
  File "OPSI\System\Windows.py", line 981, in mount
RuntimeError: Failed to mount '\\opsi-depot.example.com\opsi_depot': (86, 'WNetAddConnection2', 'The specified network password is not correct.')
[4] [2026-01-22 12:44:08.475] [event processing on_demand{user_logged_in}] Failed to get bootmode from registry: [WinError 2] The system cannot find the file specified   (EventProcessing.py:874)
[3] [2026-01-22 12:44:13.032] [event processing on_demand{user_logged_in}] Failed to mount '\\opsi-depot.example.com\opsi_depot': (86, 'WNetAddConnection2', 'The specified network password is not correct.')   (Windows.py:980)
[3] [2026-01-22 12:44:13.037] [event processing on_demand{user_logged_in}] Failed to process product action requests: Failed to mount '\\opsi-depot.example.com\opsi_depot': (86, 'WNetAddConnection2', 'The specified network password is not correct.')   (EventProcessing.py:1075)
Traceback (most recent call last):
  File "OPSI\System\Windows.py", line 969, in mount
pywintypes.error: (86, 'WNetAddConnection2', 'The specified network password is not correct.')

What have I got wrong here, is this a opsi-config server <-> opsi-depot server issue or is this a client agent setup issue?

[j.schneider]

You need to run

Code: Alles auswählen

opsiconfd setup --set-depot-user-password

on the Configserver and Depotserver.
Use the same password on both.