MDT 2012: Installing a Custom Dictionary in Office 2010

So, some might not need this but thought I would share anyways.  I have created my new MDT 2012 Deployment Share and want to add Microsoft Office 2010 as an application, but I also need to customize that deployment of Office 2010 when I’m deploying my new OS.  Here are the steps on how to do this, but also how to create a custom Office 2010 Install.

  1. Once you’ve setup everything for you OS, go to the Applications folder on your Deployment Share and right click>New Application
  2. Once there, put in the relavent information including where your resource CD is located.
  3. THen once you have done this, you will notice that there is an extra tab compared to other applications.  This is because Microsoft Deployment Toolkit recognizes that it’s Office 2010 and gives you a few more options.
  4. 50
  5. Click on the Office Products Tab and you should now see this screen:
  6. 51
  7. Now click on the Office Customization Tool
  8. You will be prompted with a warning box, please read and understand this.  Any Customizations you make are saved in a customization file and need to be moved to the appropriate folder within your Office 2010 source file.
  9. 52
  10. Then the Office Customization Tool dialog box shows up.  You can do ton’s of customizations but for this post it’s all about adding a Custom Dictionary to Office 2010.
  11. 54
  12. Once there select Add Files and go to where your .Dic file is at and make sure you select INSTALLLOCATION as the option.
  13. Then click on Add Registry Entires
  14. 55
  15. Add the Registry settings that you see in the image above
  16. Here is a more detailed view of what you should see when you select Add… in the bottom corner:
  17. 57
  18. Then select Remove Registry Entries, this is needed to remove any previous settings when Office 2010 Installs originally.
  19. 56
  20. That’s it, now save your MSP File in the appropriate location and you should be good to go.

MDT 2012 Deployment Guide: Step by Step (11 of 11)

Preparing WDS to enable PXE Boot (optional but very useful)

  1. Minimize the Deployment Workbench application
  2. Open “Windows Deployment Services” from Start/Admin Tools
  3. Expand Servers / CONFIG-DEPLOY.config.local and right-click on Boot Images and select Add Boot Image. If the boot image already exists, right click on it and select Replace Boot Image to replace it with a newer version


  1. Browse to the Deployment Share location (e.g. E:\DeploymentShares\Customername) and open the Boot folder
  2. Select the LiteTouchPE_x86.wim file and click Open


  1. Click Next
  1. Enter an Image Name and Description


  1. Click Next until the wizard completes.  Adding the image may take a couple of minutes.


  1. Once completed, the image will be listed as shown below


MDT 2012 Deployment Guide: Step by Step (10 of 11)

Automating the Deployment Process

  1. Right-click on the deployment share and select Properties


  1. Select the “Rules” tab
  2. In the main window, edit the settings as required.  A sample CUSTOMSETTINGS.INI is below but feel free to change it as needed…
  3. 35



























TimeZoneName=GMT Standard Time











Sets the Company Name during the deployment

Skips unneeded wizard pages

Skips unneeded wizard pages

The Windows product key to use (only required if using MAK keys)

Sets the deployment type

Skip the domain membership screen


Credentials to use to join computers to the domain


Do not perform a user state migration

Do not ask which task sequence to run

Defautl to the task sequenceID you created earlier

Don’t display a list of possible OS packages to install Ask which regional settings to configure

Set the default UI language to English

Set the default user locale to GB English

Set the default keyboard to UK

Ask which time zone the computer is in

Set the default time zone to GMT

Set the default time zone to GMT (legacy support)

Skip the installation of BitLocker

Skip the Summary screen before deployment starts

Skip the “Build and Capture” options during deployment

Don’t ask for a local admin password for new PCs

Do not request local admin password during OS deployment

Pre-sets the admin password to the value specified

Allows you to set the local WSUS server for updates

Sets the default IE homepage for all users of new computers

Tells the computer to shut down once task sequence is completed


If you want to specify the Timezone, Locale or other settings during the deployment, simply change the YES to a NO for the relevant option and you’ll be prompted during deployment.  These settings are injected automatically during deployment into the unattend.xml so you don’t have to worry about messing around with it usually.

MDT 2012 Deployment Guide: Step by Step (9 of 11)

Creating a Deployment Task Sequence

  1. From the Deployment Workbench, expand the customer Deployment Share and right-click on Task Sequences and select New Task Sequence
  2. Enter a Task Sequence ID and Name.  Make a note of the ID as you may need it later!


  1. Accept the default “Standard Client Task Sequence” template
  2. Select the relevant OS Image to deploy


  1. This option will vary dependent on whether you are going to be using KMS or MAK licenses for their Windows 7 deployment.

KMS          –                 Select Do not specify a product key at this time

MAK         –                 Select Specify a multiple activation key (MAK key) for activating this operating system

and enter the relevant key


  1. Enter the relevant information in the OS Settings page


  1. Enter an Administrator password – this will be the local Admin password for the machines when built (Dilbert)
  2. Ensure the summary data is correct
  3. Accept the confirmation screen

The task sequence is now created.  We can customise this to our hearts content but generally we don’t need to make too many changes.



9.1  Task Sequence Properties

When you edit a Task Sequence, there are multiple areas of configuration.  The properties of a Task Sequence consists of three tabs – General, Task Sequence and OS Info.

General Tab

The General tab contains the summary information about the Task Sequence including the sequence ID, Name and any comments along with the list of client platforms which the sequence is allowed to run on.


Task Sequence Tab

The task sequence example below is based on the “Standard Client Task Sequence” template provided by MDT but the screenshot below includes quite a bit of stuff which wasn’t needed for the environment concerned (sorry).  Both 32 and 64 bit sequences are identical with the exception of the “Install Operating System” step which refers to the appropriate 32 or 64 bit custom OS image.


Set DriverGroup001 Task Sequence Variable Step

This is an additional step we’ve added which sets the “DriverGroup001” variable to “%make%\%model% which will automatically pick up the correct drivers from the repository based on manufacturer and model name.  If we do not do this, MDT will just trawl through the entire Out-of-Box Drivers repository and try to determine the correct drivers based on PnP ID and it sometimes gets it wrong!  This gives us a little more control!  NOTE: DriverGroup001 needs to go immediately before the first “Inject Drivers” step.

OS Info Tab

The OS Info Tab’s contents will vary depending on which OS is being installed by the Task Sequence.  For Windows 7, it simply consists of a single button to edit the unattend.xml file which controls the configuration settings of Windows 7 during deployment.  Most elements of unattend.xml are automatically configured on-the-fly by MDT based on information provided during the Deployment Wizard although you can add additional elements manually.  For MIL, we are letting MDT perform all of the configuration of unattend.xml based on settings we have pre-configured in the CustomSettings.ini (see section 4.1)

Copying the Default Profile we Created before we Captured our Image:


                  While within this task sequence we need to modify our Unattend.xml file so that the image will keep our Default Profile.  To do this, we must enable the CopyProfile setting within the Unattend.xml file but we can only do so from the Deployment Task Sequence, and NOT FROM THE CAPTURE TASK SEQUENCE.  View the Images below for more details:



MDT 2012 Deployment Guide: Step by Step (8 of 11)

Importing a Customer Reference Image

  1. From the Deployment Workbench, expand the customer Deployment Share and right-click on Operating Systems and select Import Operating System
  2. From the Import Operating System Wizard, select Custom Image File and click Next
  3. Browse to the path of the WIM file.  For captured images, this would by default be the \Captures folder in the Deployment Share
  4. Select “Copy Windows Vista, Windows Server 2008, or later setup files from specified path” and enter the path to the relevant OS installation media.  (Strictly speaking you shouldn’t need to do this step but it bugs out sometimes in my experience)


  1. Enter an appropriate directory name


  1. Ensure the summary is correct and click Next


  1. Wait while the image is imported then check the Confirmation shows no errors.



You should now have everything you need to deploy your Windows 7 image to any hardware.  The last step is to create a deployment Task Sequence.