Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture customized Windows 7 Images – Part II

IMPORTANT: Updated versions from this series using Windows 7 + Microsoft Office 2010 in automated deployment with MDT 2010 can be found here:

Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I

Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II

Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III


On the first post of this series, we’ve managed to install MDT 2010 and its requirements, prepare distribution share and task sequence, add Windows 7 image to use it as reference and create the deployment point. We are now going to add Office 2007 as an application to be deployed included in the OS image and complete the environment to generate the reference image.

The process of adding an application like Office 2007 it is quite simple, the only trick is to get the application to install silently (or unattended) without requiring for user intervention , we’ll see how that works.

Adding Applications to MDT 2010: Office 2007

We’ll add the application using also a simple wizard, but the interesting part comes when you get the chance to modify default settings on the Office 2007 package:

1. “Deployment Workbench” > “Distribution Share” > “Applications” > “New”.

2. Select “Application with source files”.

3. Complete the data about the application.

4. Select the “Source Directory”. Since I have it on the hard drive, I’ll check “Move the files to the distribution share instead of copying them”.

5. Keep the directory name as suggested: “Microsoft Office 2007”.

6. On “Command Details” introduce the name of the executable for Office 2007: “setup.exe” and click on “Finish”. We’ll add the special arguments to achieve silent installations in next steps.

With that performed the Office 2007 is added as an application in Microsoft Deployment Toolkit. MDT also detects automatically the options available for Office products, this way we can modify them in a simple way.

Office 2007: Silent and personalized installation

To achieve this, we are going to use the mentioned feature of MDT to generate a “Config.xml” file that is used for personalizing installations of Office 2007. This XML is a very flexible option that we can modify according to our needs and generate ourselves custom and unattended Office suite installations.

1. Access the Application Properties from the “Deployment Workbench” console. And get to the “Office Products” tab.

2.  Now we are going to select the following options:

Office 2007 Product to Install: Enterprise (this is the version that I’m using).
Office 2007 Languages: en-us.
Product Key: If applies, select your PID.
Customer Name: Augusto Alvarez
Display Level: None. This will generate the silent installation.
Accept EULA: Checked.

3. Click on “Apply”.

This will generate the XML file that you can check it clicking on “Edit Config.xml”. You should see something like this (notice that the first section it’s just a sample):

You can check also on “Details” tab that “setup.exe” command line has been modified to use the recently generated XML: “setup.exe /config Enterprise.WW\config.xml(Enterprise.WW is the folder where the XML file is stored)

This XML file will install all the components of the Office 2007 Enterprise suite. If you want to continue customizing the components to be installed, check this example of Config.xml that selects only Word, Excel, OneNote, Outlook, PowerPoint and remove remaining components.

Config.xml Example

<Configuration Product=”Enterprise”>

<Display Level=”none” CompletionNotice=”no” SuppressModal=”no” AcceptEula=”yes” />
<USERNAME Value=”Augusto Alvarez” />
<AddLanguage Id=”match” />
<AddLanguage Id=”en-us” ShellTransform=”Yes” />
<OptionState Id=”AccessFiles” State=”absent” Children=”force” />
<OptionState Id=”ExcelFiles” State=”Local” />
<OptionState Id=”GrooveFiles” State=”Absent” Children=”force” />
<OptionState Id=”OneNoteFiles” State=”Local” Children=”force” />
<OptionState Id=”OUTLOOKFiles” State=”Local” />
<OptionState Id=”PPTFiles” State=”Local” />
<OptionState Id=”PubPrimary” State=”Absent” Children=”force” />
<OptionState Id=”RMSFiles” State=”Local” Children=”force” />
<OptionState Id=”WORDFiles” State=”Local” />
<OptionState Id=”XDOCSFiles” State=”Local” Children=”force” />
<OptionState Id=”SHAREDFiles” State=”Local” />
<OptionState Id=”TOOLSFiles” State=”Local” />
<OptionState Id=”EXCELFiles” State=”Local” />

</Configuration>

For more information about Config.xml customization check this link: Config.xml file in the 2007 Office system.

Adding Office 2007 to the Task Sequence

With the previous steps we have already added the Office suite and configured to a silent installation. Now we need to introduce it on the task sequence prepared on the previous post.

1. “Deployment Workbench” > “Task Sequences” > “Win7” > “Properties”.

2. Access the tab “Task Sequence”. Here are all the steps involved in the process, you can check all the options (most of them did not appear on the Task Sequence wizard) and change their values or disable specific steps.

3. The step that we are interested in is “State Restore” > “Install Applications”. Select “Install a single application” > “Microsoft Office 2007”. Click “OK”.

If you later want to add more applications to the same task sequence, use the same step on this task sequence, select “Add” > “General” > “Install Application”. The application must, of course, added already to MDT.

Now the installation of Office 2007 it’s included on the “Deploy Windows 7” sequence and will occur silently with the parameters included.

On the next post we’ll see how to boot and generate the Windows 7 image that will be captured and ready to be deployed on your environment.

Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture customized Windows 7 Images – Part I

Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture customized Windows 7 Images – Part III

Cheers!

IMPORTANT: Updated versions from this series using Windows 7 + Microsoft Office 2010 in automated deployment with MDT 2010 can be found here:

Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I

Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II

Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III


 

16 Comments »

  1. Hi,
    The articles is great, good work. The only issues is that i can not find the MDT 2010 beta 1 installation files anywhere. The MDT 2010 beta 2 is slightly different and can find any step-by-step guide to deploy. Can you help is any ways. Thanks

  2. First of all i would like to thank you for the great article!
    I have a question to ask you!
    Is it possible to use MDT 2010 to deploy applications to already preinstalled windows 7?
    For example i would like to deploy only office 2007 or another application.
    An another wuestin is it possible to use MDT to update already installed applications.

    Thank you

    • Hello Kon,
      To deploy and update applications you can use System Center Configuration Manager 2007 (SCCM), that also works with MDT task sequences.
      Cheers!
      Augusto

      • Or you create a new Tasksequence that only installs applications then create a cmd-file which has the following content(example)

        \\servername\mdtshare$\scripts\litetouch.vbs /SkipTaskSequence:YES /TaskSequenceID:TASKID

  3. Hi,

    Thanks for the guide, its really good. But I need to install the multiple applications (so end user can decide if they want all or some of them….) can you tell me how to do that ?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s