forum.opsi.org

Hi,
Thank you all for your answers.
In fact, I solved my problem using a local admin setup and AutoIT, as command-line only MSI installation was not working, even with the local context opened.
I don't have time to explore MSI caveats, but maybe I'll try one day ...
Regards

The software is "LPKF CircuitPro PM". Winst version 4.11.5.20 is used. The command line used is something rather classical : [Winbatch_install] msiexec /i "LPKF CircuitPro PM 2.3.msi" /qb! /l* "$LogDir$\$ProductId$.install_log.txt" TARGETDIR="$InstallDir$" I h...

Thanks for your reply.

I also tried without AutoIT, with "/qf" flags. I can answer all the questions manually, and the installation is successfull if I run it logged in.

But if I let the agent perform it, I can answer the questions but the installation hangs.

Hi, I'm experiencing something rather strange with a new installation I am trying to perform (a simple MSI) : if I run my script logged on Windows (admin) and using winst32, it works perfectly. But if I ask OPSI to install the product running the very same script, on next reboot or by executing it i...

Hi,
Can someone explain the following message :
Exception in CreateAndProcessScript: Handling AktionslisteRange check error

Regards

Thanks for your reply ! It reads to me like you have one client and then only change the mac address to install another client with the same settings. I would advise against this if you ever want to know what exactly is installed on one client! You may also run into problems and unnecessary work whe...

Hi,
No, they aren't. I think it's because another tool is used for inventory management. OSPI is only used for OS and software deployments.

Hi, I'll have to deploy more than 100 clients in a near future, and most of them consist in hardware renewal. Thank to OPSI capabilities, I just have to change a MAC address and I can get the existing products selections. Very nice ! But when I tried to install a dozen of machines concurrently, I ex...

Hi, I finally managed to update the netboot product and use the most recent bootimage. But I have another problem : is there a way to "prune" the hardware records ? I deleted the old machine, but when I recreate it, many parameters still remain (fomrer MAC address, the NIC of the new machi...

Thanks for your reply.

If I use "opsi-backup", I can safely revert back to the currently used version ? I don't have much informations, but my predecessor seems to have tweak a few things and I would like to be able to go back if I can't port them in a newer version.