Installing LibreOffice 3.6.0.4 and 3.5.6 as an administrative ( aka. Server or Parallel ) installation does not allow setting the installlocation (see the text in a .cmd file for further info. If I use normal installation ( /i instead of /a ) it is working. I am filing this bug as major, because you are not able to install LibreOffice onto a command line server in a custom path... -- install.cmd -- @ECHO off start /wait msiexec /qr /norestart /a "T:\_chrome\LibO_3.5.6_Win_x86_install_multi.msi" INSTALLLOCATON="L:\3.6.0" exit -- END --
NOT reproducible as a real problem for Server Installation of "LibreOffice 3.6.4.0+ English UI/ German Locale [Build-ID: a4b919d],{tinderbox: Win-x86@9 pull time 2012-10-10 19:11:32} on German WIN7 Home Premium (64bit) I never observed a "real life" problem during my hundreds of Server Installations. I simply followed instructions on <http://wiki.documentfoundation.org/Installing_in_parallel#Administrativ_Installation> (more or less): 1. rename the downloaded file to something I can remember and type, for example "3640.msi" and copy it to my "C:\user\Username\" folder 2. In Win programs accessories from WIN Program Start Center I start "Zubehör/Eingabeaufforderung" (no idea how that is called in English), what starts the black DOS command line screen and shows the DOS prompt in my user folder 3. I type "msiexec /a 3640.msi" <Return> Installation starts, and I will be asked for installation folder in the LibO installation dialog So may be there is a problem that WIN command line rules are not respected in all details (I have no skills or knowledge there) by LibO, but I can't see a major QA problem here. András: What has to be done?
(In reply to comment #0) > start /wait msiexec /qr /norestart /a > "T:\_chrome\LibO_3.5.6_Win_x86_install_multi.msi" INSTALLLOCATON="L:\3.6.0" Sorry, I'm away from my Windows box for a while, but would you please try the following? start /wait msiexec /qr /norestart /a "T:\_chrome\LibO_3.5.6_Win_x86_install_multi.msi" TARGETDIR="L:\3.6.0" I read this on stackoverflow, and the answer there seems to be generic, i.e. that works with all msi installers. (see: http://stackoverflow.com/questions/3403733/silent-administrative-install-specifying-an-installation-directory) If it does not work, I'll have a look at this bug next week.
Thanks, working ;) BUT SHOULD BE Documented....