Menu

Office 2010 Deployment

September 9, 2010 - Deployment, KMS/MAK, Office 2010

Many company’s choose to deploy Microsoft Office 2010 with the Windows 7 rollout, including mine. I will describe in short our Office 2010 deployment process in this post.

1. Create a network installation point

2. Make a customization file with Office Customization Tool in Office 2010

image

Setup

Features

image

image

Additional content

Outlook

image

image

image image

Save the customization file in de Updates folder: \\servername\sharename\office2010standard\Updates\yourFile.msp

3. Config.xml

Although some settings are already configured with OCT, this is my Config.xml file:

<Configuration Product=”Standard”>

  <Display Level=”basic” CompletionNotice=”no” SuppressModal=”No” AcceptEula=”Yes” />
  <Logging Type=”standard” Path=”C:\YourLogPath” Template=”Microsoft Office 2010 Standard Setup(*).txt” />
  <COMPANYNAME Value=”CompanyName” />
  <Setting Id=”SETUP_REBOOT” Value=”Never” />
  <AddLanguage Id=”match” ShellTransform=”Yes” />
  <AddLanguage Id=”en-us” />
  <AddLanguage Id=”nl-nl” />
  <AddLanguage Id=”fr-fr” />
  <LIS SOURCELIST=”\\servername\sharename\office2010standard” />
</Configuration>

Display

I like to immitate the /qb installation method, this can be done with this line:

<Display Level=”Basic” CompletionNotice=”No” SuppressModal=”No” AcceptEula=”Yes” />

Other options for Display Level are : None / Basic / Full

CompletionNotice set to None. To hide the setup end screen. Users don’t need this screen.

SuppressModal set to None, This way setup doesn’t display error messages and other dialog boxes that might interrupt the installation.

AcceptEula to accept the End User Licensing automatically.

Logging

We like to have some logging to troubleshoot install failures.

<Logging Type=”standard” Path=”C:\YourLogPath” Template=”Microsoft Office 2010 Standard Setup(*).txt” />

Setting – Reboot

To suppress a reboot after setup:

<Setting Id=”SETUP_REBOOT” Value=”Never” />

Setting – Suppress Activation using MAK actication

If you’re using a Multiple Activation Key (MAK) and you want to automatically (silent) activate Office 2010, add the following line to your config.xml. So users don’t get bothered with activation.

<Setting Id=”AUTO_ACTIVATE” Value=”1″ />

AddLanguage

A system engineer in a multilanguage environment needs to enable extra languages. Use the following lines to match the User Interface (Shell UI) language of the user’s Locale, and install some languages used in Belgium.

<AddLanguage Id=”match” />
<AddLanguage Id=”en-us” ShellTransform=”Yes” />
<AddLanguage Id=”nl-nl” />
<AddLanguage Id=”fr-fr” />

LIS Sourcelist

Add extra lines to the LIS Sourcelist if you’re having multiple fileservers holding the Office network installation point.

<LIS SOURCELIST=”\\servername\sharename\office2010standard” />

 

Hotfixes and patches

Hotfixes can be placed in the directory \Updates. These patches will be installed by setup during Office installation.

4. Deployment

Install Office with the /config parameter, pointing to the config.xml file.

\\servername\sharename\office2010standard\setup.exe” /config \\servername\sharename\office2010standard\Standard.WW\Config.xml

 

Happy deploying!

Update: Integrate Service Pack 1 into the network installation point.

One thought on “Office 2010 Deployment

  • Pingback: The D-Spot (The Deployment Spot) » Integrate SP1 into Office 2010 network installation point

  • Comments are closed.