Creating a Silent, Unattended Installation of Office 2010

For Use with K1000 Series Managed Installations

Contents
The Formats................................................................................................................................................... 3 .EXE Files ........................................................................................................................................................ 3 CD/DVD and ISO files..................................................................................................................................... 5 Config.xml...................................................................................................................................................... 6 Custom Inventory Rules ................................................................................................................................ 9 Managed Installations .................................................................................................................................10

The Formats
There are a couple of different varieties that Office 2010 arrives in. It can come on a CD/DVD, an ISO or as an executable or MSI. There are subtle differences in the way that you would handle each of these but the core concept is the same.

.EXE Files
Using the .exe version of the installer: Double-click on the installer and allow it to extract its files Push the installer window to the side Navigate to %TEMP% Find the office folder in the temp directory, currently on my system I see: C:\Users\<Logged in User>\AppData\Local\Temp\OWPCFCC.tmp Within this folder, you will see the files and folders needed for the managed installation

You will need to zip the entire contents of this folder at this level in order for the Managed Install to function properly. Highlight the contents and right click. Select Send To > Compressed Folder.

The resultant zip file will be uploaded into the KBOX as the dependency for the software item we are going to relate to each version of Office 2010.

CD/DVD and ISO files

The ISO and CD/DVD Versions of the install make life a little easier. They already have the files extracted into their own folders. All you have to do is go in and claim what you need. Most of the DVDs and ISOs will come with both versions of Office (x86 and x64). They are separated into their own folders. Simply copy the folders to your system and continue from there as if you were working with the files listed above in the .EXE section.

Config.xml
The config.xml file is one way that Microsoft has provided to allow for silent, unattended installs of the Office 2010 Suite. For full details of how to use the config.xml file, you can reference: http://technet.microsoft.com/enus/library/cc179195.aspx The config.xml file is located in the .WW folder that holds the same name of the product version thats being installed, (i.e. standard, ProPlus, etc.)

Copy the file to either a network share, or, the root folder in which the setup.exe is located. Remove the <!-- and the --> from the top line and adjust the values to meet your criteria. For most customers, it will probably resemble the following: <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

Left alone, this will still prompt for user intervention if a product key is required. Just below this, adding the following product key line will remedy this situation (the 25 xs represent the 25 digit product key). <PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxxxx" />

The resultant config.xml file should look something like the following:

<Configuration Product="ProPlusr"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxxxx" /> <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> --> <!-- <USERNAME Value="Customer" /> --> <!-- <COMPANYNAME Value="MyCompany" /> --> <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

<!-- <LIS CACHEACTION="CacheOnly" /> --> <!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> --> <!-- <DistributionPoint Location="\\server\share\Office" /> --> <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> <!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> --> <!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --> </Configuration>

Custom Inventory Rules

Microsoft Office 2010 has no differentiating characteristics for the KBOX to determine if there is an x86 or x64 version present. In order to achieve this separation, you will need to create two new software inventory items and associate a custom inventory rule that will check the registry for the subtle differences in the application. In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook there is a bitness key that specifies x86 or x64. This will work as a differentiator for most customers, but some strip Outlook from Office and hence render this key unusable for this purpose. From Technet: URL: http://technet.microsoft.com/en-us/library/ee681792.aspx If you have installed Office 2010 including Microsoft Outlook 2010, Outlook sets a registry key named Bitness of type REG_SZ on the computer on which it is installed. The Bitness registry key indicates whether the Outlook 2010 installation is 32-bit or 64-bit. This might be useful to administrators who are interested in auditing computers to determine the installed versions of Office 2010 in their organization.

Registry path: HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook Registry key: Bitness Value: either x86 or x64

Using this, you can create your software inventory to something similar to the following: Display Name: Microsoft Office 2010 <version> x64 Vendor: Microsoft Custom Inventory Rule: RegistryValueEquals(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook, Bitness, x64) Associate the appropriate installer file for 64 bit Office and save. Repeat the steps for the 32 bit version. As the machines check in, if they have Office 2010 installed, they will begin to register an additional installed application called Microsoft Office 2010 <version> x64 (or x86 depending on the system). You can now use these software inventory items to create distributions to systems that need either suite. You could also base labels on the custom inventory rules that youve created.

Managed Installations
Once you have your files uploaded and associated to the appropriate software items, you can begin making Managed Installations through Distribution. The steps are similar to any other Managed Installation but the command line will be different. The command line you will use for this setup is as follows: Setup.exe /config <path to config.xml file>

If you stored the config.xml file on a share you would use, \\sharename\config.xml If you stored it within the zip folder, you will need to give the full path to the extraction point, for example: C:\Program Files\KACE\KBOX\downloads\14 where 14 is the number of the Software ID. You can find the ID in the URL of the software inventory item as highlighted below.

So, for a config file that was stored in the zip folder root, your command line would be: Setup.exe /config C:\Program Files\KACE\KBOX\downloads\XX\config.xml (where XX equals the Software Inventory ID of the package)