forum.opsi.org

Hello All:

I'm still trying to track down a gremlin in our opsi configuration. Namely it has to do with our wireless laptops. I'm the only IT person at a small school district in rural Alaska and opsi has been a lifesaver when it comes to re-imaging computers (for whatever reason). However, I have not been able to successfully use it to push out updates to software. I think I've finally tracked down the problem but could use some advice on how to resolve it.

All of our Windows-based laptops use Radius to authenticate on the wireless network. It appears that the opsi-client launches before Radius can authenticate and thus it does not see the opsi server. In fact, it looks like the networking waits until the opsi-client is finished before authenticating.

Is there a way to confirm that this is what is indeed happening -- and if so -- how would I either change the priority (loading order) of the opsi-client or change the timeout it waits to communicate? Anyone else experience anything like this?

Thanks,
Brent Bain

Hello Brent,

what OS are your clients running?
If you are running Windows XP I am not sure that altering the timeout will solve the problem because then it could be a problem with the order of the chained GINAs.

But of course you can try. Please look at the manual section 7.3, especially the part where the opsiclientd.conf is explained. The best practice on changing these values is to create an config object on the server and then alter it's value. If you search for "config_create" in the manual you will find some examples.

I would take a look into the events. Maybe it is a better approach for your wireless clients to make use of the event that will be triggered when a network connection is available (event_net_connection).


With kind regards

Niko