Export (0) Print
Expand All

Deploy Office 2010 by using Microsoft Deployment Toolkit 2010

Office 2010
 

Applies to: Office 2010

Topic Last Modified: 2011-11-11

You can use Microsoft Deployment Toolkit (MDT) 2010 Update 1 to deploy Microsoft Office 2010 to multiple computers on a network, by following the instructions in this article. You can also use the MDT for installing Windows, applications, updates, and drivers.

noteNote
This article describes the deployment of Office 2010 and related applications, if you require them. It is assumed that you have a computer that has MDT 2010 installed on the same network as the target computers to which you want to deploy Office 2010.

In this article:

If you installed Windows by using MDT, you can skip this section. If you did not install Windows by using MDT, follow these steps before you attempt to deploy Office 2010 by using MDT 2010 Update 1:

  1. Install MDT 2010 Update 1.

    Download MDT 2010 Update 1 (32-bit or 64-bit) and the print-ready documentation that is available at Microsoft Deployment Toolkit (MDT) 2010 Update 1 (http://go.microsoft.com/fwlink/p/?LinkId=159061). Instructions about how to run the .msi file are included on the page.

  2. Install Windows Automated Installation Kit (Windows AIK) version 2.0.

    Download the Windows AIK at The Windows Automated Installation Kit (AIK) for Windows 7 (http://go.microsoft.com/fwlink/p/?LinkId=224463).

    For information about Windows AIK and how to install it, see Windows Automated Installation Kit (Windows AIK) User's Guide (http://go.microsoft.com/fwlink/p/?LinkId=232502).

  3. Install networking services, such as Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP).

    For more information, see Domain Name System (http://go.microsoft.com/fwlink/p/?LinkId=232882) and Dynamic Host Configuration Protocol (http://go.microsoft.com/fwlink/p/?LinkId=232881).

Before you begin your Office 2010 deployment, you must create an MDT 2010 deployment share on the computer on which MDT 2010 is installed. The deployment share, which is created in the MDT Deployment Workbench, is the repository for applications, operating system images, language packs, device drivers, and other software deployed to target computers.

To create a deployment share:

  1. On the MDT 2010 computer, create a folder to use as a deployment share. For this article, the deployment share is C:\MDT_Office_Share.

  2. Click Start, click All Programs, click Microsoft Deployment Toolkit, and then click Deployment Workbench.

  3. In the Deployment Workbench console tree, under Deployment Workbench, right-click Deployment Shares, and then click New Deployment Share. The New Deployment Share Wizard opens to the Path page

  4. On the Path page, click Browse, In the Browse for folder dialog box, locate the folder C:\MDT_Office_Share, and then click OK. Click Next.

  5. On the Share page, type the share name MDT_Office_Share$, and then click Next.

  6. On the Descriptive Name page, click Next.

  7. On the Allow Image Capture page, click Next.

  8. On the Allow Admin Password page, click Next.

  9. On the Allow Product Key page, click Next.

  10. On the Summary page, click Next.

  11. The Progress page indicates that the share is being created. On the Confirmation page, click Finish. The New Deployment Share Wizard finishes, and the new deployment share, MDT Deployment Share (C:\MDT_Office_Share), appears under Deployment Shares in the Deployment Workbench console tree.

To add the Office 2010 Professional Plus setup files to the deployment share:

  1. Under MDT Deployment Share (C:\MDT_Office_Share), right-click Applications and then click New Application. The New Application Wizard opens to the Application Type page.

  2. On the Application Type page, make sure that Application with source files is selected, and then click Next.

  3. On the Details page:

    1. Under Publisher, type the name of the application publisher (optional).

    2. Under Application Name, type a descriptive name for Office 2010 (required).

    3. Under Version, type the application version (optional).

    4. Under Language, type the application language (optional).

    5. Click Next.

  4. On the Source page:

    1. Click Browse. In the Browse for Folder dialog box, locate and select the folder that contains the Office 2010 setup files, and then click OK.

      noteNote
      If you want to move the Office 2010 setup files instead of copying them, select the check box that is next to Move the files to the deployment share instead of copying them.
    2. Click Next.

  5. On the Destination page, accept or change the default destination folder (the deployment share folder that will contain the application source files) that was assigned by the wizard, and then click Next.

  6. On the Command Details page:

    1. Under Command line, type the command that you want to be run at the start of the application installation. For Office 2010, this would be setup.exe.

      noteNote
      With setup.exe, you do not have to add the /admin parameter to invoke the Office Customization Tool (OCT), because there is a built-in UI dialog box for the OCT.
    2. Click Next.

  7. On the Summary page, click Next.

  8. The Progress page indicates that the share is being created. On the Confirmation page, click Finish. The New Application Wizard finishes, and the name for Office 2010 that you typed in the Application Name page is displayed in the Deployment Workbench details pane.

You can add other applications, such as Microsoft Project 2010 and Microsoft Visio 2010, and add-ins, such as PowerPivot, to the deployment share in the same manner that you added the Office 2010 suite.

  1. Under MDT Deployment Share (C:\MDT_Office_Share), right-click Applications and then click New Application. The New Application Wizard opens to the Application Type page.

  2. On the Application Type page, make sure that Application with source files is selected, and then click Next.

  3. On the Details page:

    1. Under Publisher, type the name of the application publisher (optional).

    2. Under Application Name, type a descriptive name for the application (required).

    3. Under Version, type the application version (optional).

    4. Under Language, type the application language (optional).

    5. Click Next.

  4. On the Source page:

    1. Click Browse. In the Browse for Folder dialog box, locate and select the folder that contains the setup files for the particular application, and then click OK.

      noteNote
      If you want to move the setup files instead of copying them, select the check box that is next to Move the files to the deployment share instead of copying them.
    2. Click Next.

  5. On the Destination page, accept or change the default destination folder (the deployment share folder that will contain the application source files) that was assigned by the wizard, and then click Next.

  6. On the Command Details page:

    1. Under Command line, type the command that you want to be run at the start of the application installation. For Project 2010, this would be setup.exe. Certain add-ons, such as PowerPivot, require use of the Microsoft Installer and the msiexec.exe command. You can customize both setup.exe and msiexec.exe by using various switches and parameters that are assigned to each command. For more information about the switches and parameters, see Setup command-line switches for the 2007 Office system (http://go.microsoft.com/fwlink/p/?LinkId=227579) and Knowledge Base article 227091: Command-Line Switches for the Microsoft Windows Installer Tool (http://go.microsoft.com/fwlink/p/?LinkId=227578).

      noteNote
      With setup.exe you do not have to add the /admin parameter to invoke the OCT, because there is a built-in dialog box for the OCT.
    2. Click Next.

  7. On the Summary page, click Next.

  8. The Progress page indicates that the share is being created. On the Confirmation page, click Finish. The New Application Wizard finishes, and the application name that you typed in the Application Name page appears in the Deployment Workbench details pane.

After Office 2010 is imported, you can customize items that are not called out specifically as Office 2010 items in the Help files of the Deployment Workbench.

  1. In the Deployment Workbench details pane, right-click the Office 2010 application name, and then click Properties.

  2. On the Office Products tab, in the Office products to install box, select ProPlus. You can then edit the Config.xml attributes that are displayed. You can also edit the Config.xml file directly by clicking Edit Config.xml.

  3. You can invoke the OCT by clicking Office Customization Tool. Configure the settings as required. After you complete the customizations, save the .msp file to the C:\MDT_Office_Share\Applications\<application name>\Updates folder.

If you added multiple applications to the deployment share, you can see them all by clicking Applications under MDT Deployment Share (C:\MDT_Office_Share). To make sure that certain applications are deployed ahead of other applications to account for any deployment dependencies, you can create an application bundle. The application bundle is a collection of all the applications that you added to the MDT. It enables you to easily customize the order in which the applications are deployed.

  1. Under MDT Deployment Share (C:\MDT_Office_Share), right-click Applications and then click New Application. The New Application Wizard opens to the Application Type page. Make sure that Application bundle is selected, and then click Next.

  2. On the Details page:

    1. Under Publisher, type the name of the application publisher (optional).

    2. Under Application Name, type a descriptive name for the application bundle (required).

    3. Under Version, type the application version (optional).

    4. Under Language, type the application language (optional).

    5. Click Next.

  3. On the Summary page, click Next. The Progress page, which appears next, indicates that the application bundle is being created.

  4. On the Confirmation page, click Finish. The New Application Wizard finishes, and the application bundle name that you typed in the Application Name page appears in the Deployment Workbench details pane.

  5. Right-click the application bundle name, click Properties, and then click the Dependencies tab. Here is where you can indicate the order in which the applications are to deploy.

  6. Click Add. The Select an item dialog box appears. To list an application on the Dependencies tab, highlight the application and then click OK.

    importantImportant
    Do not add the application bundle listing to the Dependencies tab.
  7. After all applications are listed on the Dependencies tab, make sure that they are in the order that you want by clicking Up and Down. When you are finished, click OK.

The next step is to create a custom task sequence that will not install an operating system. Create the task sequence as follows:

  1. Under MDT Deployment Share (C:\MDT_Office_Share), right-click Task Sequences and then click New Task Sequence.

  2. On the General Settings page:

    1. Under Task sequence ID, enter an ID (alpha or numeric characters or both).

    2. Under Task Sequence Name, enter a name.

    3. Click Next.

  3. On the Select Template page:

    1. In the task sequence pull-down menu, select Custom Task Sequence.

    2. Click Next.

  4. On the Summary page, click Next. The Progress page, which appears next, indicates that the task sequence is being created.

  5. On the Confirmation page, click Finish. The name of the custom task sequence appears in the Deployment Workbench details pane.

  6. Right-click the name of the custom task sequence, select Properties, and then select the Task Sequence tab.

  7. On the Properties tab, under Install Application select Install a single application. In Application to install, type the name of the application bundle.

  8. Click OK.

Next, you must set the deployment rules for the deployment share. This updates the CustomSettings.ini file that is in the C:\MDT_Office_Share\Control folder. At minimum, you must set a rule that the deployment does not install an operating system. You can set additional rules if you want. The rules properties are described in the Toolkit Reference as part of the print-ready documentation that is available at Microsoft Deployment Toolkit (MDT) 2010 Update 1.

  1. Right-click MDT Deployment Share (C:\MDT_Office_Share) and select Properties.

  2. Click the Rules tab and in the [Default] section, set OSInstall=N to indicate that no operating system will be installed during this deployment.

  3. As required, update or include any additional rules that are described in the Toolkit Reference. For example, if you want to use an administrator password during deployment, set SkipAdminPassword=NO. When you are finished, click OK. Open C:\MDT_Office_Share\Control\CustomSettings.ini to confirm that the updates were made.

It is recommended that you set up a silent installation. For this procedure, it is assumed that you are installing Office 2010 and no other applications.

  1. Under MDT Deployment Share (C:\MDT_Office_Share), right-click Applications, and then double-click the Office 2010 application in the details pane. The application properties dialog box appears.

  2. Click the Office Products tab. Select the Office products to install check box and select ProPlus from the pull-down menu.

  3. Select the Office languages check box and select the check boxes for the appropriate languages. Generally, this is en-us and any other languages that are set to be installed.

  4. Select the Product key check box and type a product key if you indicated in the rules that one is required.

    importantImportant
    The product key is displayed in clear text unless you set up an Office Customization Tool (OCT) configuration file (.msp) to obscure the value.
  5. Select the Customer name check box and type the name of the customer.

  6. Select the Display level check box and select Basic from the pull-down menu.

  7. Select the Accept EULA check box to accept the Microsoft Software License Terms.

  8. Click Apply to add your selections to the Config.xml file.

    • To further update the Config.xml file, click Edit Config.xml. When you are finished, save and exit the file. For more information about how to update the Config.xml file, see Config.xml file in Office 2010.

    • To update or create or update an MSP file through the OCT, click Office Customization Tool. For more information about how to use the OCT, see Office Customization Tool in Office 2010.

  9. Click the Details tab. Select the Standard application option and notice that the Quiet install command is updated to include the silent installation parameters. You are now ready to install Office 2010

We recommend that you install Office 2010 by running the LIteTouch.vbs script, which is located in the C:\MDT_Office_Share\Scripts\ folder. This method works well for automating the deployment of Office 2010 to multiple computers.

  1. Go to C:\MDT_Office_Share\Scripts\ and double-click LiteTouch.vbs to start the installation process. The way that the process runs depends on the configuration that you have set up. For example, you are not prompted for an administrator password if you set the rule SkipAdminPassword=YES, and you are not prompted for a product key if you set the rule SkipProductKey=YES.

    noteNote
    You can find the configuration files in the C:\MDT_Office_Share\Control\ folder.
  2. Observe the installation process indicator while the installation process continues silently and finishes. Office 2010 is now installed on the client computer.

As an option, you can individually install Office 2010 on each client computer by using an ISO image file that is burned onto a DVD. If the client computer is a virtual machine (VM), you can also perform the installation by using the ISO image file directly.

  1. Expand MDT Deployment Share (C:\MDT_Office_Share), expand Advanced Configuration, right-click Media, and then select New Media. The New Media Wizard dialog box appears.

  2. In the Media path field, either type a path or click Browse to locate the path of the folder that will contain the media files.

  3. Click Next to see the Summary page, and then click Next to create the image. When the process is complete, click Finish.

  4. Under Advanced Configuration, click Media. In the details pane, right-click the image, which should be MEDIA001 if it is the first image created (otherwise select the listing that has the highest number), and select Properties. The MEDIA001 dialog box appears.

  5. Click the General tab. Under Platforms Supported and keep the check box selected for the boot image you want (either 32-bit or 64-bit). To create the ISO image file (LiteTouchMedia.iso), make sure that you select the Generate a Lite Touch bootable ISO image check box.

  6. Copy the rules from the CustomSettings.ini file in the C:\MDT_Office_Share\Control\ folder. Click the Rules tab in the MEDIA001 Properties dialog box and paste the copied rules over any existing rules. Click OK.

  7. In the details pane, right-click the image and select Update Media Content. When the update is complete, click Finish.

  8. Go to the media folder that you designated in step 2 and inspect the created files. You should find the ISO image file (LiteTouchMedia.iso) and a Content folder that contains the deployment files.

  9. Start the LiteTouchMedia.iso file from the client computer to install Office 2010.

    • If the client computer is a physical computer, create a physical DVD of the LiteTouchMedia.iso file.

    • If the client computer is a VM, start the VM directly from the LiteTouchMedia.iso file, or from a physical DVD of the LiteTouchMedia.iso file.

The following example shows installation of Office 2010 by using a physical DVD on a physical client computer.

  1. After starting Windows, load the DVD into the drive.

  2. When the DVD drive is visible in the drive list, right-click the drive and select AutoPlay to start the installation process. The custom task sequence starts the installation of Office 2010.
    Office 2010 is now installed on the client computer.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft