forum.opsi.org

Hi, I have created a package that should run at the user_login event. By manually editing the config file to enable this event type on the client, I do manage to "trigger" OPSI to process events, but there are no events found. There is a package created where in opsi-newprod I have ONLY se...

Hi, I think I know what's happening, just looking for confirmation. Our OPSI server is in our (service provider) domain, let's say FOO.COM We have a Depot server at a customer, say BAR.COM The only config server is at our domain, say the config server is opsi.foo.com opsi.foo.com and opsidepot.bar.c...

OK, thanks. I was confused as sudo apt-get update sudo apt-get upgrade did not upgrade the opsi-depotserver; the package was marked as "held back" by the apt-get I entered sudo apt-get install opsi-depotserver and this installed the right version of the packages. Just wanted to share with ...

Hi, Forgive me the stupid question, but I'm still trying to improve my knowledge of Ubuntu... I have learned on this forum that in order to get rid of the error: "ProductGroup is not defined" and "method getClientsWithFailed_hash is not valid" is to revert to an older version of ...

Thanks!

In that case, we have some work to do, as the FQDN of the depot is not resolvable currently by the config server.

Will post update as soon as we have done this.

Wonderful support community, btw!

Krgds
Koen

Hi Patel, Sorry for the late reply from my side. With regards to the previous post, I have to take back my suggestion. The backend conf file is indeed changed to JSONRPC and that's how it should work. No idea why it didn't with me the first time I tried. I checked now, and the backed conf file is us...

Hi, We are setting up an OPSI server at OPSICONFIG.ACME.COM (our site) and multiple depots at OPSIDEPOT.CLIENT1.COM , OPSIDEPOT.CLIENT2.COM (customer sites) Between the servers are WAN connections, and the OPSI config server is hosted in a data center with good bandwidth - All depot servers can comm...

Hi, Very clear indeed - thank you for your time. Thanks to this thread, I have found the solution to my problem: - I have removed the IP address from the clients in the OPSI database - I have changed the "Update IP" setting in opsiclientd.conf to "no" Now, OPSI uses FQDN lookup (...

Hi, Sorry for the delay, I accidentally unsubscribed following this thread by email. I understand. So, theoretically: - a client CLIENT01 installs opsiclientd while it has IP address 192.168.2.100 - the computer is used elsewhere, DHCP times out, and another PC, CLIENT02, gets address 192.168.2.100....

Hi Bardo,

Thanks for your answer!
However, the file /etc/opsi/opsiconfd.conf has 2 related settings:
verify IP
update IP

but no
resolve IP

Was that a small typo, or should I add the parameter you mentioned?
I'll test by setting both verify & update to "Yes".

Tnx

Koen.