Today we will show you how to deploy Microsoft Office 2016 on clients computers using Microsoft Deployment Toolkit 2013. We assume that you are already read our previous article, which describes how to install MDT 2013 and the Windows Deployment Services role on Windows Server 2012 R2 and use this combination for the network deployment of Windows 10. To accomplish this task, you need a server with installed MDT, Windows Assessment and Deployment Kit and MS Office 2016 image. You can download it from Microsoft download center.
This time we use Office Professional Plus 2016.
Open Deployment Workbench console and expand Deployment Shares -> MDT Deployment Share ->Application and on the shortcut menu click on New Application.
Select Application with Source Files
Enter Application Name (MS Office 2016 Pro Plus x86). All other fields are optional. Click Next.
Click Browse and go to the folder with distribution package of Office 2016.
Specify the name of directory on the MDT server that will be used to contain MS Office 2016 installation files.
In Command line field enter the name of Office 2016 setup file (setup.exe).
On the Summary page view the specified settings and click on Next.
Wait until the end of copying operations and Office application importing to MDT distribution directory. Usually it takes about 5–7 minutes. Click Next -> Finish.
Verify that new application MS Office 2016 Pro Plus x86 appears in the Applications section.
In the Deployment Workbench console click on Properties of the created application.
On MS Office 2016 Pro Plus x86 Properties go to Office Products tab.
Specify the following settings:
- Office product to install: ProPlus
- Office Languages: select languages to force installation of specific language packs
- Product key: input Office 2016 MAK key (if applicable)
- Display Level: None
- Accept EULA: True
- Always suppress reboot: True
Tip. To configure deployment configuration options of Office installation package you can use Office Customization Tool (OCT) from Office 2016 Deployment Tool. Using OCT, you can create a special update file with installation settings (.MSP), which will be automatically applied during Office 2016 installation. MDT allows direct access to the OCT wizard. Press Office Customization Tool button and configure which components and features of Office should be installed during deployment. Generated MSP file is automatically saved in directory Updates of the Office 2016 source directory on MDT share.
Also you can change quiet install Command line to use specific customization package:
setup.exe /adminfile “\\192.168.1.24\deploymentshare$\Applications\MS Office 2016 Pro Plus x86\Updates\setup.msp”
Next we need to create a new task sequence that will be used to deploy Office 2016 via MDT. To do this, expand Task Sequences and in context menu select New Task Sequence.
Input Task sequence ID (Office2016x86) and Task sequence name (MS Office 2016 Pro Plus x86).
From dropdown menu select Custom Sequence and click on Next.
Check your Settings, click Next and Finish to create the Task Sequence.
In the right pane of Task Sequence you will see a new task named MS Office 2016 Pro Plus x86.
Right click on task MS Office 2016 Pro Plus x86 and select Properties. Switch to tab Task Sequences and select an entry Install Applications. On right pane select Install a single Application and using Browse button select MS Office 2016 application which you created before. Click OK to save settings.
So, we have finished Task Sequence configuration, and now are ready to deploy Office 2016 on client computers. You can simply use this task inside the Windows 10 deployment task or install it independently.
To verify the Office 2016 installation package, you can run it manually from MDT server. Switch to client PC and open Deployment share using its UNC path (in our case, \\192.168.1.24\deploymentshare$\ ). Open Scripts folder and run file Litetouch.vbs.
Wait until Windows Deployment Wizard starts and select Task Sequence MS Office 2016 Pro Plus x86 and click Next.
Wait until the installation is completed and try to open desired MS Office application. If application starts correctly, you can begin to deploy this Office 2016 package on multiple computers.