How To Use The Office DEPLOYMENT TOOL
TLDRThis tutorial walks through the process of using the Microsoft Office Deployment Tool, explaining each step from downloading and extracting the tool to configuring installations through a dedicated website. It covers selecting the desired Office suite, architecture, languages, installation options, update sources, and customization preferences. The guide also details how to export an XML configuration file and use it with command-line instructions for a silent installation, emphasizing the importance of following the steps precisely for successful Office deployment.
Takeaways
- 📂 The Microsoft Office Deployment Tool is a command-line application that streamlines the process of deploying Office installations across multiple systems.
- 🔧 It's important to run the tool as an administrator to ensure proper functionality and permissions.
- 📋 The tool requires a configuration file, which can be created using a dedicated Microsoft website or by manually specifying parameters.
- 🖥️ You can choose the Office architecture (32-bit or 64-bit), suite, and default applications to be deployed during the configuration process.
- 📱 The configuration file allows for customization, such as disabling specific apps, setting languages, and choosing installation options.
- 🔄 The tool can deploy Office from an existing path or download it from the Office Content Delivery Network.
- 📂 Specify a local source path for the tool to download and store Office installation files.
- 🔒 Silent installations can be achieved by using the appropriate switches and ensuring the EULA is accepted in the configuration file.
- 🔄 Updates can be managed through various options, including direct downloads from Microsoft, a local source, or SCCM management.
- 🏢 The tool is particularly useful for organizations looking to standardize their Office installations and manage updates efficiently.
- 🚫 When deploying for imaging or cloning, avoid opening Office applications to prevent the generation of a randomized product key, which could complicate activation and licensing.
Q & A
What is the main topic of the video?
-The main topic of the video is how to use the Microsoft Office Deployment Tool for deploying Office applications in a more efficient and customizable way.
Why is the Office Deployment Tool considered convoluted and not straightforward?
-The Office Deployment Tool is considered convoluted and not straightforward because its documentation is weak and it requires a certain level of technical understanding to effectively use its command-line interface and configuration files.
How does one access the dedicated website for customizing the configuration file?
-The dedicated website for customizing the configuration file can be accessed by searching for 'config is calm' or by using an existing Office 365 admin portal account to sign in and configure the settings.
What is the purpose of the configuration file in the Office Deployment Tool?
-The configuration file is used to specify the settings and options for the deployment of Office applications, such as the architecture (32-bit or 64-bit), the Office suites, languages, installation options, and other preferences.
How can you ensure a silent installation of Office using the Deployment Tool?
-A silent installation can be ensured by using the '/setup:configure' switch with the configuration file in the command line, and by selecting options such as 'Do not display the user interface' and 'Do not display any error messages' in the configuration file settings.
What is the significance of specifying a local source for Office installation files?
-Specifying a local source for Office installation files allows for more control over the download and installation process, reducing reliance on the Office Content Delivery Network and potentially speeding up the installation process in a local network environment.
How can automatic updates be managed with the Office Deployment Tool?
-Automatic updates can be managed by selecting the desired update source in the configuration file, such as directly from Microsoft, from a local source, or through a SCCM (System Center Configuration Manager) deployment.
What is the purpose of the 'Uninstall existing products' option in the configuration file?
-The 'Uninstall existing products' option is useful for removing older versions of Office before deploying a new one, ensuring a clean installation and avoiding potential conflicts or compatibility issues.
Why is it important to have the EULA accepted for silent installations?
-Having the EULA (End User License Agreement) accepted is crucial for silent installations because it ensures that the software is installed legally and in compliance with Microsoft's terms and conditions.
How can the Office Deployment Tool be used for cloning a system?
-The Office Deployment Tool can be used for cloning a system by creating a base image with the desired Office configuration, then deploying that image across multiple systems. It's important to snapshot the base image before opening any Office applications to avoid associating a randomized product key with the image.
Outlines
📚 Introduction to Office Deployment Tool
The video begins with a brief introduction to the Office Deployment Tool, acknowledging its complexity and the lack of comprehensive documentation. The speaker shares their recent experience assisting a coworker with the tool, which inspired the video's topic. They guide the audience through the process of locating and downloading the Microsoft Office Deployment Tool, emphasizing the importance of running it as an administrator. The speaker also discusses the extraction of files and the creation of a dedicated folder on the C Drive for organizational purposes. A potential issue with the tool's prompt is mentioned, but the speaker reassures viewers that the tool usually works despite this. The setup file is highlighted as a command line-based application, requiring a configuration file for execution. The speaker introduces a new Microsoft website that simplifies the configuration process by allowing users to customize and export an XML file, which will be used in the demonstration.
🔧 Customizing Configuration with Microsoft's Dedicated Website
In this paragraph, the speaker takes the audience through the process of using Microsoft's dedicated website to customize the configuration for their Office Deployment. They explain how to sign in with Office 365 admin portal credentials and create a new configuration. The speaker details the selection of architecture (32-bit or 64-bit), choice of Office suites (with a focus on Business as the default), and the option to disable unnecessary applications like Access, Publisher, Teams, and Skype for Business. The importance of selecting a primary language and the option to include additional languages and proofing tools are also discussed. The speaker then moves on to the installation options, explaining the choice between deploying from an existing path or downloading from the Office Content Delivery Network. They demonstrate how to specify a local source for the installation files and discuss the options for handling updates, including automatic updates from Microsoft, a local source, or SCCM management. The paragraph concludes with the configuration of uninstalling pre-existing Office versions and the selection of product activation methods, with a focus on the default setting for most users.
📄 Exporting Configuration and Initiating Silent Installation
The speaker continues by guiding the audience through the final steps of configuring the Office Deployment Tool. They explain how to provide an organization name, which will be displayed in the properties of Office documents. The absence of special characters in the organization name is noted, and the speaker proceeds to the next step. Additional application preferences are briefly mentioned, highlighting the level of customization possible. The speaker then moves on to exporting the configuration as an XML file, which will be used as a reference during the setup process. They demonstrate how to save this file in the designated folder and overwrite any existing configuration. The paragraph concludes with the speaker minimizing the configuration tool and transitioning to PowerShell or command prompt to execute the silent installation. The speaker provides instructions on running the setup with the download option and referencing the configuration file. They also share a tip on monitoring the download progress through the task manager and reassure viewers of the tool's effectiveness by demonstrating the download speed.
🚀 Completing the Installation and Verifying Activation
The paragraph starts with the speaker resuming the video after the installation files have been downloaded. They guide the audience through the final steps of the installation process, which involves running the setup.exe with the configure switch and referencing the XML configuration file. The speaker emphasizes the silent nature of the installation, noting that it will proceed without any user input. The option to hide the installation entirely is also discussed. After the installation is completed, the speaker demonstrates how to open Word and sign in with an Office 365 account. They verify the product activation by navigating to the account settings and confirming the subscription product. The speaker concludes the video by advising viewers on the importance of not opening Office on a base image if they intend to use it for cloning purposes. They also remind viewers to snapshot the base image before opening Office to ensure they can revert to the original state. The video ends with a call to action, encouraging viewers to leave comments, like, and subscribe.
Mindmap
Keywords
💡Office Deployment Tool
💡Configuration File
💡Command Line
💡Silent Installation
💡Taskbar Pinning
💡Updates
💡EULA
💡Product Activation
💡Organization Name
💡Application Preferences
Highlights
Introduction to the Office Deployment Tool and its purpose.
The complexity of using the Office Deployment Tool and the limitations of existing documentation.
Downloading and installing the Office Deployment Tool with administrative privileges.
Extraction of files and choosing the storage location for the tool.
Addressing common issues during the setup process.
Introduction to the new dedicated website for configuring the deployment parameters.
Customizing the configuration file with the desired Office architecture, suite, and applications.
Selecting installation options, including the source of Office files and installation visibility to users.
Pin Office icons to the taskbar and specify update sources.
Silent installation process and EULA acceptance for smooth deployment.
Product activation and user base configuration.
Adding organization name and properties to Office documents.
Customizing application preferences for specific use cases.
Exporting the configuration as an XML file for command-line usage.
Using PowerShell or Command Prompt for the deployment process.
Downloading required installation files using the setup utility.
Executing the silent installation with the configuration XML file.
Verifying the successful installation and activation of Office.
Important notes for deploying Office in a cloned system or imaging environment.