[resolved] Problem to access share "opsi_depot" after migration 4.1 to 4.2

Antworten
bourhis
Beiträge: 97
Registriert: 07 Nov 2012, 15:57

[resolved] Problem to access share "opsi_depot" after migration 4.1 to 4.2

Beitrag von bourhis »

Hi,

I have migrated my Opsi server on version 4.2 and now I have a problem with the "opsi_client_agent" which can't access to "opsi_depot" : the message who appears very fleatingly seems to be "wrong password".

N.B. : if I try to mount manually this share with the "pcpatch" user it's working.

What I have missed in this migration process ?

Best regards.
Zuletzt geändert von bourhis am 14 Dez 2021, 14:26, insgesamt 1-mal geändert.
Benutzeravatar
SisterOfMercy
Beiträge: 1384
Registriert: 22 Jun 2012, 19:18

Re: Problem to access share "opsi_depot" after migration 4.1 to 4.2

Beitrag von SisterOfMercy »

Did you run the opsi-package-updater after the migration? And if so, was the opsi-client-agent updated? If not, you might want to reinstall that package.
Also check clientconfig.depot.user in configed.
Bitte schreiben Sie Deutsch, when I'm responding in the German-speaking part of the forum!
bourhis
Beiträge: 97
Registriert: 07 Nov 2012, 15:57

Re: Problem to access share "opsi_depot" after migration 4.1 to 4.2

Beitrag von bourhis »

I have found the problem : the version 4.1 use the local "pcpatch" user to mount the share "opsi_depot" but, for other purposes, my server is on a samba 4 domain and now (on version 4.2) it try to use the domain user "pcpatch" who don't exist in my AD !

So I have created a user "pcpatch" on my AD (and addes it on the local group) and it seems working :-)
Antworten