How shall I deploy MS Office 2010?

i am trying to deploy office 2010 for the first time in kace, whats the best way i can get this deployment done.

thanks

Answer Summary: Run your setup.exe /admin and customize it the way you need it. This will create a msp.
From there you can use this command line and create a managed install for it.
setup.exe /adminfile .msp

Answers

5

+1 to dgullet's instructions. I would just add a couple things:

Install the program manually on one machine first (I always use a test machine), run Inventory and then select it from the Inventory > Software list to upload the zipped file (Uploaded & Associate File). From the, it should appear in the Managed Install screen's Software drop-down list (at the top).

Also, make sure you zip the setup files and folders, not the containing folder.

I always put the command line stuff in a batch file and call the batch file. This approach does sometimes pop up a command prompt screen on the client during the install, but I've had more success with this approach.

John,
I stumbled into your batch file today looking for something different, but I think it's going to help me with a separate issue!

I'm wondering, would it be possible to use something similar to your if statements to call the appropriate processor flavor of install? Say I have UltraVNC installers for 32bit and 64bit windows zipped up together and I want it to install the appropriate one based on the %processor_architecture%. I know the option that jknox suggests (comment below) would work by just separating the 64bit and 32bit machines in a label, but it seems simpler to be able to do it in one step.

Yes, I've used that approach in the past and it works well - you just need to make sure you have both installers zipped up together. For example, here's what I used for Adobe Flash when it came in 32-bit and 64-bit versions.

The main thing to be aware of is whether the K1000 will detect the different versions as separate applications or not - if it does, the MI may keep trying to redeploy to the machines that won't get the detected version (i.e. MI tied to 32-bit version of app &gt; mixed-version installers deployed to 32-bit &amp; 64-bit machines &gt; the MI will only detect the 32-bit installs and will show the other machines as still requiring the MI until maximum retries have been reached).

I heard at this past Konference that KACE is going to be working on &quot;rolling up&quot; applications so they aren't broken out so granularly, so hopefully that will prevent this scenario from happening once that system is in place.

Hope that helps!

John
_____________________

:: flash player uninstaller & updater
::
:: kills any programs that might be using flash player
:: checks for bitness (x86 or x64)
:: runs appropriate version of flash player uninstaller
:: cleans up folders
:: checks again for OS bitness (x86 or x64)
:: installs appropriate version of latest flash player
::
:: you can also use this to uninstall newer versions (i.e. 11)
:: and then install earlier versions (i.e. 10)
:: just change the installer used at the bottom

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Kill any programs that might be using flash player
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::

To expand on jverbosk's answer, there will normally be a software inventory entry for the Office suite and for the individual components themselves. For this, you would upload your software package to the suite. The title will vary by version, but mine is "Microsoft Office Professional Plus 2010".

Also, if you are deploying the 32 bit and 64 bit versions, you will need to use a custom inventory rule in separate software inventory items to tell them apart.

Do what Dugullett said, then zip the entire thing together (make sure the MSP gets in their too, and upload it to the Kace box. Then run the command as Dugullett said. Is there any part of that process you aren't sure about?

The following example shows how to use the OCT to set silent installation options, enter a MAK product key, and specify the AUTO_ACTIVATE property value for automatic activation.

To configure silent installation and automatic activation options in the OCT

Run the OCT by typing setup.exe /admin at the command line from the root of the network installation point that contains the Office 2010 source files. For example, use \\server\share\Office14\setup.exe/admin.

To set silent installation options, select Licensing and user interface in the left pane, select None in the Display level drop-down box, select Suppress modal, clear the Completion notice check box, and then select I accept the terms in the License Agreement.

To enter a MAK key, select Licensing and user interface in the left pane, and in the right pane select Enter another product key, add your organization's MAK product key for Office 2010 in the Product key text box.

To set automatic activation options, select Modify Setup properties on the left pane, and then click Add in the right pane.

In the Add Property Value dialog box, in the Name box, type AUTO_ACTIVATE. Note that property names must be uppercase.

In the Value box, type 1, and then click OK.

When you complete your customizations in the OCT, click Save as on the File menu to save the Setup customization .msp file.