Florian Effenberger
Wed, 30 Apr 2008 06:41:03 -0700
Hi,
The simple solution would be to install the runtime, if required, system wide. A problem seems to be the so called "administrative network installation", right ? In this case OOo will get installed on a network drive and the Office application should be able to start from any Windows client using that installation. This works fine in OOo 2.x but would break for 3.0 if the runtimes don't get installed on the client systems. I'm not that familiar with those deployment, but I would expect that there is either the possibility for the admin to get the runtimes installed on all the clients machines and/or we make it a requirement, that an installation of the needed files need to get run on the client machines ? Any experts around for thoughts about this scenarios ?
well, sounds like my area. ;-)I don't do administrative installs (/a parameter for setup), but unattended ones. It would be good if the required runtimes could be embedded in the setup so in case of an unattended installation (msiexec /qn blabla openofficeorg30.msi) they get installed.
For administrative installs, I hope that the runtimes can be distributed unattended beforehand. Then it shouldn't be a problem.
Maybe Ingo knows more here? Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]