It seems that more and more businesses are relying on OpenOffice.org (OOo) for their word processing, spreadsheet and presentation needs. I have no empirical data to back up this observation its just anecdotal. Anyway…
There are a few ways to perform a remote deployment of OOo with PDQ Deploy. First things first. You need to download the installation files. For this example I downloaded OOo 3.2.1. After downloading the file, Run it to “unpack” the Installation files. You will be asked where you want the files unpacked to. Choose a network share (I used “\\Scranton\Deploy\Open Office”. Once the files are unpacked QUIT the installation. Yes, quit it. We just needed the files unpacked. We will get to the installation when we deploy the app.
To use PDQ Deploy to install to your organization you can perform a simple deploy by just passing a few extra parameters into your command line arguments.
As you can see we are just calling the MSI file and selecting the options to Not Reboot and run Quiet. We have passed some additional Windows Installer Properties respective to OpenOffice.org. The additional properties prevent OOo from performing an automatic update and prevents a desktop icon from being created on the target machines.
It is imperative that the “Include entire directory” check box is checked. If it is not checked then the deployment will fail (as the additional OOo deployment files will not be copied down to each target).
Get PDQ Deploy today. It’s free and fully functional.