Different networks

[loggenk]

Hi,
At our organisation we work with different networks based on the location. When i install a client in for example dev.xxx.xx (where we mostly install the system), and i move it to ehv.xxx.xx its not possible to "fire software on demand"
Opsi is searching for the client in dev.xxx.xx

Does anyone know a solution for that?

With regards,

Kees....

[adlerweb]

((Sorry for the post-fubar - of course i randomly picked the only pc installed in the new subnet and hit the wrong button while editing...))
Hi,

I just changed a subnet some days ago and do not have any problems related to on-demand. In the configed-overview the IPs are still wrong (=old subnet), but on-demand seems to work on DNS/WINS which resolves to the correct host and the actions are executed as expected. Is there a firewall blocking your traffic or a problems with your DNS-setup by any chance?

[mirkt]

what are the values of:
resolveHostAddress
update ip
?
http://download.uib.de/opsi_stable/doc/ ... resolution

In my case, I am using resolveHostAddress = True and update ip = no.. If I need to change client's hostname, I:
* change DNS record
* rename client in configed
* change host_id in opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf

and everything woks..

[loggenk]

Hi it isn't a problem with the ipdadress. When I change the hostname to nb2222.ehv.xxx.xx I can Fire on Demand.

But since we have a lot of mobile users who are working one in Dev, and the next day in Ehv, and so on, i don't like the idea that i have to change the domain frequently.

On the other hand, when they reboot the system they also get the installation. So its not really a problem, but fire on demand is quicker then restarting the system.

Thanks anyway..