Remote Software Deployment: Open Office (this time 38% more officey)


Remote Deploy Open Office

Back in August I wrote an article describing how to deploy Open Office (OOo) via PDQ Deploy. If you want to deploy OOo with a few more customizations, you can try another method using a .bat or .cmd file as the deployment file. We are planning on adding the ability to “chain” deployments and customized actions together in one deployment, but for now you can achieve the same goal using BAT or CMD files.

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 version 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 “\\quagmire\install\OpenOffice3.2.1”). 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.

In this example we want to REMOVE the automatic registration wizard that pops up when OOo is opened for the first time. In order to do this you will need to download the OOo Extension for disabling the wizard. After you download the correct extension add the directory Extensions to your Open Office source directory.

***Please note, the following was used with PDQ Deploy 1.1 which is, at the time of this writing, in public beta. Download it now!***

Here are the contents of our InstallOpenOffice321.bat deployment file. Feel free to copy it and use it yourself.

msiexec.exe /i openofficeorg32.msi /qn ISCHECKFORPRODUCTUPDATES=0 CREATEDESKTOPLINK=0

IF EXIST “%ProgramFiles%\ 3”   (
     “%ProgramFiles%\ 3\program\unopkg.exe” add –shared Extensions\DisableFirstStartWzd_ooo321.oxt
) ELSE (
     “%ProgramFiles(x86)%\ 3\program\unopkg.exe” add –shared Extensions\DisableFirstStartWzd_ooo321.oxt

Refer to the screen shot below where PDQ Deploy uses the file above for the deployment. Notice we are no longer passing any parameters to the installer. We have included the command line parameters in the BAT file. To view other deployment customizations for I would refer you to the OOo Wiki site.

blog spc 2010 10 07 OOoDeploy