According to the Servicedesk51_Install_Guide, chapter 4 there are 2 ways to install the SD client:
• Install a GUI Client from the installation DVD or from a network location. • Install a GUI Client using Java Web Start.
We are about to install the SD-client to multiple WS and need a way to install with standard application deployment such as MSI with MST (as it was with 4.5) or an EXE with parameters or INI-file. (the Java Web start is therefore not an option)
Servicedesk51_Install_Guide, page 57: "Once an installation has successfully completed, the file is moved to the following location: %TEMP%\HPOvInstaller\_\ovinstallparams_.ini (Windows operating systems)"
As stated above, the installation of the client produces an INI-file, but I can't find any mention of how to start a new client installation on another WS using this INI-file.
Needless to say I must have missed the information I need totally, can you point me in the right direction please?
Interesting! Which MSI-file did you use that calls on the other 23 msi-packages automatically?
(The client_5.10.066_setup.exe does this but I cannot figure out how to control the installation to make it silent and accept custom directories and so on....is it possible to extract a MSI from the setup.exe perhaps?)
That is precisely what we have done...a snapshot.. and for SP1 another snapshot and when the next patch is released I probably need to redo the entire snapshot since 3 linked install objects to install 1 SD client gets hairy pretty fast.
So I repeat my plea to the SD gods, please point me to a decent silent install, either Setup.exe with parameters och a MSI.
Does all this means that the setup.exe cannot handle silent install for the moment? Does it also means that the only way available for the moment is to install each of the 23 MSI files by itself with a batch file, or something?
I really would like to hear the "tricks" some used to achieve this.