The new Office Garage Series: Anatomy of Office Software Updates in Click-to-Run

This week adventurous hosts go deeper on how software updates really work for the new Office. They attempt to demystify what’s different compared to the Office Professional Plus 2013 MSI install and explain the optimized update service for the Office 365 ProPlus Click-to-Run install. They also explain how the service works in cases where you might want to test, validate and publish updates…


The new Office Garage Series: Click-to-Run Customization and Deployment Deep Dive Part 3 - Integration and Automation with Software Distribution Tools

This week marks the third in a three part series as hosts Jeremy Chapman and Yoni Kirsh take the concepts from installing and configuring Office Click-to-Run in the first two parts and integrate those with software distribution tools like System Center Configuration Manager, Microsoft Deployment Toolkit and Windows Intune. They demonstrate the specific commands used with standalone…


The new Office Garage Series: Click-to-Run Customization and Deployment Deep Dive Part 2 - Workarounds

This week marks the second in a three part series, as hosts Jeremy Chapman and Yoni Kirsh, explore specific differences between the Office Professional Plus 2013 MSI and Office 365 ProPlus Click-to-Run install and potential workarounds for your Office configuration. They cover topics from removing and blocking applications from the Office suite, using multiple languages and disabling first…


The new Office Garage Series: Click-to-Run Customization and Deployment Deep Dive Part 1 with High-G Aerobatics

In this week’s episode, hosts Jeremy Chapman and Yoni Kirsh kick off a three-part series deep dive on customizing and deploying Office Click-to-Run packages. The first part of the series describes how the Office Deployment Tool for Click-to-Run is used to download, install, uninstall and convert Office packages for use with Application Virtualization. Yoni also…


The new Office Garage Series: Client Configuration Management 101

In this blog post, our animated hosts Jeremy Chapman and Yoni Kirsh begin to tackle the frequently asked question, “Do I get more control if I use the traditional Office installation?” They look at automation support and install-time controls, configuration management via Group Policy and new Office Telemetry tools with a special visit from the…


The new Office Garage Series: Who Moved My MSI?

In this blog post, our adventurous hosts Yoni Kirsh and Jeremy Chapman explain the differences between Windows Installer Package (MSI) and Click-to-Run package types, how to download Click-to-Run builds for use with software distribution tools, when its necessary to provision user accounts in Office 365 and Yoni tests whether Office 365 ProPlus can be installed…


The new Office: What are your options, what's changed and what's new?

In this blog post, our desktop specialist hosts Jeremy Chapman and Yoni Kirsh, walk us through the differences between the Click-to-Run and MSI-based Office versions, the new IT Pro capabilities, and the premise of the new Office including a demo of user based multi-device support. <a title=”The New Office: Garage Series for IT Pros – What’s…


Office Customization Tool: FAQs

The OCT is the main client customization tool for Office 2010 (and Office 2007). This tool is part of the Setup program and is included only in volume license versions of Office, such as Office 2010 Professional Plus. You use the OCT to configure settings in these areas: Setup Install location and organization name Additional network…

2

Configure a silent install of the 2007 Office system with Config.xml

The Config.xml file is used to configure installation tasks and is used only while running Setup; it is not installed or cached on users’ computers. You can edit the Config.xml file to customize the installation. By default, the Config.xml file that is stored in the core product folders (core_product_folder_name.WW folder, for example, Enterprise.WW or Pro.WW)…

8

How to customize a configuration for users by using a separate installation folder

To create a custom configuration for users with specific requirements, you can use the Config.xml file and Setup customization files (MSP files created with the Office Customization Tool), and create a separate installation folder that contains the Setup program and customizations for that group’s configuration. Then you can run (or have users run) Setup from…

1