ࡱ > V X = > ? @ A B C D E F G H I J K L M N O P Q R S T U H bjbj + , ߤ ߤ ߤ ߤ ߤ D # # # W # g b v] " "5 P \ ]_ $ k t 5 ߤ
g "
g
g ߤ ߤ
! t t t
g ߤ ߤ t
g t t @ 4 ]; # g H H 7 0 g q @ N ߤ b P
g
g t
g
g
g
g
g t
g
g
g g
g
g
g
g
g
g
g
g
g
g
g
g
g :
For IT professionals: Deployment guide for Microsoft Office 2010
Microsoft Corporation
Published: September 2010
Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com)
Abstract
This book contains information about how to install, configure, and upgrade to Microsoft Office 2010. The audience for this book includes IT generalists, IT operations, help desk anddeployment staff, IT messaging administrators, consultants, and other IT professionals.
The content in this book is a copy of selected content in the HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=181453"Office 2010 Resource Kit technical library (http://go.microsoft.com/fwlink/?LinkId=181453) as of the publication date. For the most current content, see the technical library on the Web.
This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
2010 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, WindowsServer, and WindowsVista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Contents
TOC \o "1-4" \h HYPERLINK \l "_Toc268851628" Getting help PAGEREF _Toc268851628 \h x
HYPERLINK \l "_Toc268851629" Configuring and deploying Office 2010 PAGEREF _Toc268851629 \h 1
HYPERLINK \l "_Toc268851630" Configure and deploy volume activation of Office 2010 PAGEREF _Toc268851630 \h 2
HYPERLINK \l "_Toc268851631" Deploy volume activation of Office 2010 PAGEREF _Toc268851631 \h 3
HYPERLINK \l "_Toc268851632" Prepare and configure the Office 2010 client PAGEREF _Toc268851632 \h 3
HYPERLINK \l "_Toc268851633" KMS clients PAGEREF _Toc268851633 \h 3
HYPERLINK \l "_Toc268851634" MAK clients PAGEREF _Toc268851634 \h 4
HYPERLINK \l "_Toc268851635" Office Customization Tool (OCT) PAGEREF _Toc268851635 \h 4
HYPERLINK \l "_Toc268851636" Config.xml file PAGEREF _Toc268851636 \h 4
HYPERLINK \l "_Toc268851637" Volume Activation Management Tool PAGEREF _Toc268851637 \h 4
HYPERLINK \l "_Toc268851638" The Backstage view PAGEREF _Toc268851638 \h 5
HYPERLINK \l "_Toc268851639" The ospp.vbs script PAGEREF _Toc268851639 \h 5
HYPERLINK \l "_Toc268851640" Rearm the Office 2010 installation PAGEREF _Toc268851640 \h 5
HYPERLINK \l "_Toc268851641" Prepare and configure the KMS host PAGEREF _Toc268851641 \h 6
HYPERLINK \l "_Toc268851642" Set up and activate the KMS host PAGEREF _Toc268851642 \h 6
HYPERLINK \l "_Toc268851643" Sppsvc state stopped error PAGEREF _Toc268851643 \h 8
HYPERLINK \l "_Toc268851644" Manually install the Office 2010 KMS host key and activate PAGEREF _Toc268851644 \h 9
HYPERLINK \l "_Toc268851645" Configure the Office 2010 KMS host PAGEREF _Toc268851645 \h 9
HYPERLINK \l "_Toc268851646" Verify successful activation of the Office KMS host PAGEREF _Toc268851646 \h 10
HYPERLINK \l "_Toc268851647" Configure DNS PAGEREF _Toc268851647 \h 12
HYPERLINK \l "_Toc268851648" Deploy Visio 2010 PAGEREF _Toc268851648 \h 12
HYPERLINK \l "_Toc268851649" Post-deployment PAGEREF _Toc268851649 \h 13
HYPERLINK \l "_Toc268851650" Migrate an Office KMS host PAGEREF _Toc268851650 \h 13
HYPERLINK \l "_Toc268851651" Tools to configure client computers in Office 2010 PAGEREF _Toc268851651 \h 15
HYPERLINK \l "_Toc268851652" The ospp.vbs script PAGEREF _Toc268851652 \h 15
HYPERLINK \l "_Toc268851653" Scenarios that use ospp.vbs PAGEREF _Toc268851653 \h 17
HYPERLINK \l "_Toc268851654" VAMT 2.0 PAGEREF _Toc268851654 \h 18
HYPERLINK \l "_Toc268851655" Volume activation quick start guide for Office 2010 PAGEREF _Toc268851655 \h 20
HYPERLINK \l "_Toc268851656" Differences between Windows and Office activation PAGEREF _Toc268851656 \h 20
HYPERLINK \l "_Toc268851657" Scenarios for Office 2010 volume activation PAGEREF _Toc268851657 \h 21
HYPERLINK \l "_Toc268851658" Office 2010 volume activation methods PAGEREF _Toc268851658 \h 21
HYPERLINK \l "_Toc268851659" KMS activation PAGEREF _Toc268851659 \h 21
HYPERLINK \l "_Toc268851660" MAK activation PAGEREF _Toc268851660 \h 21
HYPERLINK \l "_Toc268851661" Install and configure the KMS host PAGEREF _Toc268851661 \h 22
HYPERLINK \l "_Toc268851662" Co-hosting an Office KMS host with a Windows KMS host PAGEREF _Toc268851662 \h 22
HYPERLINK \l "_Toc268851663" Prepare the infrastructure for Office 2010 PAGEREF _Toc268851663 \h 24
HYPERLINK \l "_Toc268851664" Create a network installation point for Office 2010 PAGEREF _Toc268851664 \h 25
HYPERLINK \l "_Toc268851665" Create the network installation point PAGEREF _Toc268851665 \h 25
HYPERLINK \l "_Toc268851666" Replicate the network installation point PAGEREF _Toc268851666 \h 26
HYPERLINK \l "_Toc268851667" Secure the network installation point PAGEREF _Toc268851667 \h 27
HYPERLINK \l "_Toc268851668" Customize the installation for Office 2010 PAGEREF _Toc268851668 \h 28
HYPERLINK \l "_Toc268851669" Customization overview for Office 2010 PAGEREF _Toc268851669 \h 29
HYPERLINK \l "_Toc268851670" Summary of customization methods PAGEREF _Toc268851670 \h 29
HYPERLINK \l "_Toc268851671" Office Customization Tool PAGEREF _Toc268851671 \h 31
HYPERLINK \l "_Toc268851672" Config.xml file PAGEREF _Toc268851672 \h 32
HYPERLINK \l "_Toc268851673" Setup command-line options PAGEREF _Toc268851673 \h 33
HYPERLINK \l "_Toc268851674" Configure user and computer settings PAGEREF _Toc268851674 \h 34
HYPERLINK \l "_Toc268851675" Configuring user and computer settings by using Group Policy PAGEREF _Toc268851675 \h 34
HYPERLINK \l "_Toc268851676" Configuring user and computer settings by using the Office Customization Tool PAGEREF _Toc268851676 \h 35
HYPERLINK \l "_Toc268851677" Office 2010 licensing and activation PAGEREF _Toc268851677 \h 36
HYPERLINK \l "_Toc268851678" Summary of client customization tasks PAGEREF _Toc268851678 \h 36
HYPERLINK \l "_Toc268851679" Customize setup for Office 2010 PAGEREF _Toc268851679 \h 39
HYPERLINK \l "_Toc268851680" Customize Office 2010 PAGEREF _Toc268851680 \h 40
HYPERLINK \l "_Toc268851681" Customize Office PAGEREF _Toc268851681 \h 40
HYPERLINK \l "_Toc268851682" Customize Setup before installing Office 2010 PAGEREF _Toc268851682 \h 42
HYPERLINK \l "_Toc268851683" Customize Setup PAGEREF _Toc268851683 \h 42
HYPERLINK \l "_Toc268851684" Install Office silently PAGEREF _Toc268851684 \h 44
HYPERLINK \l "_Toc268851685" Configure feature installation states for Office 2010 PAGEREF _Toc268851685 \h 46
HYPERLINK \l "_Toc268851686" Configure installation states PAGEREF _Toc268851686 \h 46
HYPERLINK \l "_Toc268851687" Configure user settings for Office 2010 PAGEREF _Toc268851687 \h 50
HYPERLINK \l "_Toc268851688" Configure user settings PAGEREF _Toc268851688 \h 50
HYPERLINK \l "_Toc268851689" Create different configurations of Office 2010 for different groups of users PAGEREF _Toc268851689 \h 52
HYPERLINK \l "_Toc268851690" Create custom configurations for a group of users PAGEREF _Toc268851690 \h 52
HYPERLINK \l "_Toc268851691" Create a custom configuration for a group of users by using a separate installation folder PAGEREF _Toc268851691 \h 53
HYPERLINK \l "_Toc268851692" Import an Office 2010 Setup customization file PAGEREF _Toc268851692 \h 56
HYPERLINK \l "_Toc268851693" Overview PAGEREF _Toc268851693 \h 56
HYPERLINK \l "_Toc268851694" Import a Setup customization file PAGEREF _Toc268851694 \h 57
HYPERLINK \l "_Toc268851695" Import languages to an existing installation PAGEREF _Toc268851695 \h 57
HYPERLINK \l "_Toc268851696" Configure a silent installation of Office 2010 by using Config.xml PAGEREF _Toc268851696 \h 59
HYPERLINK \l "_Toc268851697" Modify the Config.xml file to configure a silent installation PAGEREF _Toc268851697 \h 59
HYPERLINK \l "_Toc268851698" Run arbitrary commands with installations of Office 2010 PAGEREF _Toc268851698 \h 61
HYPERLINK \l "_Toc268851699" How it works PAGEREF _Toc268851699 \h 63
HYPERLINK \l "_Toc268851700" Create custom configurations of Office 2010 PAGEREF _Toc268851700 \h 64
HYPERLINK \l "_Toc268851701" Office Customization Tool changes in Office 2010 PAGEREF _Toc268851701 \h 64
HYPERLINK \l "_Toc268851702" Creating a custom configuration PAGEREF _Toc268851702 \h 65
HYPERLINK \l "_Toc268851703" Config.xml example PAGEREF _Toc268851703 \h 80
HYPERLINK \l "_Toc268851704" View XML content from Office Customization Tool customization files PAGEREF _Toc268851704 \h 81
HYPERLINK \l "_Toc268851705" Windows Script Host overview PAGEREF _Toc268851705 \h 81
HYPERLINK \l "_Toc268851706" ExtractOctXml.vbs script sample PAGEREF _Toc268851706 \h 81
HYPERLINK \l "_Toc268851707" Running the script PAGEREF _Toc268851707 \h 84
HYPERLINK \l "_Toc268851708" Viewing the XML contents from an .msp customization file PAGEREF _Toc268851708 \h 85
HYPERLINK \l "_Toc268851709" Example PAGEREF _Toc268851709 \h 87
HYPERLINK \l "_Toc268851710" Customize specific features in Office 2010 PAGEREF _Toc268851710 \h 89
HYPERLINK \l "_Toc268851711" Customize language setup and settings for Office 2010 PAGEREF _Toc268851711 \h 90
HYPERLINK \l "_Toc268851712" Overview PAGEREF _Toc268851712 \h 90
HYPERLINK \l "_Toc268851713" Before you begin PAGEREF _Toc268851713 \h 91
HYPERLINK \l "_Toc268851714" Deploy a default language version of Office PAGEREF _Toc268851714 \h 91
HYPERLINK \l "_Toc268851715" Specify which languages to install PAGEREF _Toc268851715 \h 92
HYPERLINK \l "_Toc268851716" Deploy different languages to different groups of users PAGEREF _Toc268851716 \h 93
HYPERLINK \l "_Toc268851717" Identify installed languages PAGEREF _Toc268851717 \h 94
HYPERLINK \l "_Toc268851718" Customize language settings PAGEREF _Toc268851718 \h 94
HYPERLINK \l "_Toc268851719" Use Group Policy to enforce language settings PAGEREF _Toc268851719 \h 94
HYPERLINK \l "_Toc268851720" Use a Setup customization file to specify default language settings PAGEREF _Toc268851720 \h 95
HYPERLINK \l "_Toc268851721" Use the Language Preferences tool to modify language settings PAGEREF _Toc268851721 \h 95
HYPERLINK \l "_Toc268851722" Customize and install the Office 2010 Proofing Tools Kit PAGEREF _Toc268851722 \h 96
HYPERLINK \l "_Toc268851723" Customize the Office 2010 Proofing Tools Kit PAGEREF _Toc268851723 \h 96
HYPERLINK \l "_Toc268851724" Installing the Office Proofing Tools Kit 2010 on a single computer PAGEREF _Toc268851724 \h 96
HYPERLINK \l "_Toc268851725" Customize the Office user interface in Office 2010 PAGEREF _Toc268851725 \h 98
HYPERLINK \l "_Toc268851726" Customize the Backstage view PAGEREF _Toc268851726 \h 98
HYPERLINK \l "_Toc268851727" Customize the ribbon, Quick Access Toolbar, and context menus PAGEREF _Toc268851727 \h 98
HYPERLINK \l "_Toc268851728" Enforce settings by using Group Policy in Office 2010 PAGEREF _Toc268851728 \h 99
HYPERLINK \l "_Toc268851729" Start GPMC PAGEREF _Toc268851729 \h 99
HYPERLINK \l "_Toc268851730" Create a GPO PAGEREF _Toc268851730 \h 99
HYPERLINK \l "_Toc268851731" Load Office 2010 Administrative Templates to a GPO PAGEREF _Toc268851731 \h 100
HYPERLINK \l "_Toc268851732" Edit a GPO PAGEREF _Toc268851732 \h 101
HYPERLINK \l "_Toc268851733" Link a GPO PAGEREF _Toc268851733 \h 102
HYPERLINK \l "_Toc268851734" Disable user interface items and shortcut keys in Office 2010 PAGEREF _Toc268851734 \h 104
HYPERLINK \l "_Toc268851735" Using Group Policy to disable UI items and keyboard shortcuts PAGEREF _Toc268851735 \h 104
HYPERLINK \l "_Toc268851736" Disabling commands by using control IDs PAGEREF _Toc268851736 \h 105
HYPERLINK \l "_Toc268851737" Disabling shortcut keys by using virtual key codes PAGEREF _Toc268851737 \h 106
HYPERLINK \l "_Toc268851738" Disabling predefined user interface items and shortcut keys PAGEREF _Toc268851738 \h 108
HYPERLINK \l "_Toc268851739" Enable SharePoint Server 2010 Colleague in Outlook 2010 PAGEREF _Toc268851739 \h 110
HYPERLINK \l "_Toc268851740" Overview PAGEREF _Toc268851740 \h 110
HYPERLINK \l "_Toc268851741" Before you begin PAGEREF _Toc268851741 \h 110
HYPERLINK \l "_Toc268851742" Configure Colleagues for My Site PAGEREF _Toc268851742 \h 110
HYPERLINK \l "_Toc268851743" Configure security for Office 2010 PAGEREF _Toc268851743 \h 113
HYPERLINK \l "_Toc268851744" Process overview PAGEREF _Toc268851744 \h 113
HYPERLINK \l "_Toc268851745" Before you begin PAGEREF _Toc268851745 \h 113
HYPERLINK \l "_Toc268851746" Plan security settings PAGEREF _Toc268851746 \h 113
HYPERLINK \l "_Toc268851747" Review required permissions PAGEREF _Toc268851747 \h 114
HYPERLINK \l "_Toc268851748" Tool prerequisites PAGEREF _Toc268851748 \h 114
HYPERLINK \l "_Toc268851749" Configure security settings by using the OCT PAGEREF _Toc268851749 \h 114
HYPERLINK \l "_Toc268851750" Configure security settings by using Group Policy PAGEREF _Toc268851750 \h 115
HYPERLINK \l "_Toc268851751" Configure Information Rights Management in Office 2010 PAGEREF _Toc268851751 \h 116
HYPERLINK \l "_Toc268851752" Overview PAGEREF _Toc268851752 \h 116
HYPERLINK \l "_Toc268851753" Before you begin PAGEREF _Toc268851753 \h 116
HYPERLINK \l "_Toc268851754" Turn off Information Rights Management PAGEREF _Toc268851754 \h 117
HYPERLINK \l "_Toc268851755" Configure automatic license caching for Outlook PAGEREF _Toc268851755 \h 117
HYPERLINK \l "_Toc268851756" Enforce e-mail expiration PAGEREF _Toc268851756 \h 117
HYPERLINK \l "_Toc268851757" Deploy rights policy templates PAGEREF _Toc268851757 \h 118
HYPERLINK \l "_Toc268851758" Configure Outlook 2010 PAGEREF _Toc268851758 \h 119
HYPERLINK \l "_Toc268851759" Configure Outlook Anywhere in Outlook 2010 PAGEREF _Toc268851759 \h 120
HYPERLINK \l "_Toc268851760" Overview PAGEREF _Toc268851760 \h 120
HYPERLINK \l "_Toc268851761" Before you begin PAGEREF _Toc268851761 \h 121
HYPERLINK \l "_Toc268851762" Use the OCT to configure Outlook Anywhere PAGEREF _Toc268851762 \h 121
HYPERLINK \l "_Toc268851763" Use Group Policy to lock down Outlook Anywhere settings PAGEREF _Toc268851763 \h 122
HYPERLINK \l "_Toc268851764" Verification PAGEREF _Toc268851764 \h 122
HYPERLINK \l "_Toc268851765" Configure Cached Exchange Mode in Outlook 2010 PAGEREF _Toc268851765 \h 123
HYPERLINK \l "_Toc268851766" Overview PAGEREF _Toc268851766 \h 123
HYPERLINK \l "_Toc268851767" Before you begin PAGEREF _Toc268851767 \h 124
HYPERLINK \l "_Toc268851768" Configure Cached Exchange Mode PAGEREF _Toc268851768 \h 124
HYPERLINK \l "_Toc268851769" Configure Exchange Server send/receive settings in Outlook 2010 PAGEREF _Toc268851769 \h 128
HYPERLINK \l "_Toc268851770" Overview PAGEREF _Toc268851770 \h 128
HYPERLINK \l "_Toc268851771" Before you begin PAGEREF _Toc268851771 \h 128
HYPERLINK \l "_Toc268851772" Create and configure Send/Receive groups in Outlook 2010 PAGEREF _Toc268851772 \h 129
HYPERLINK \l "_Toc268851773" To create and configure Send/Receive groups for Exchange accounts and folders PAGEREF _Toc268851773 \h 129
HYPERLINK \l "_Toc268851774" Configure multiple Exchange accounts for Outlook 2010 PAGEREF _Toc268851774 \h 130
HYPERLINK \l "_Toc268851775" Overview PAGEREF _Toc268851775 \h 130
HYPERLINK \l "_Toc268851776" Before you begin PAGEREF _Toc268851776 \h 130
HYPERLINK \l "_Toc268851777" Add multiple Exchange accounts to a profile PAGEREF _Toc268851777 \h 131
HYPERLINK \l "_Toc268851778" Modify or remove Exchange accounts on a profile PAGEREF _Toc268851778 \h 131
HYPERLINK \l "_Toc268851779" Configure security and protection in Outlook 2010 PAGEREF _Toc268851779 \h 133
HYPERLINK \l "_Toc268851780" Configure junk e-mail settings in Outlook 2010 PAGEREF _Toc268851780 \h 134
HYPERLINK \l "_Toc268851781" Overview PAGEREF _Toc268851781 \h 134
HYPERLINK \l "_Toc268851782" Before you begin PAGEREF _Toc268851782 \h 134
HYPERLINK \l "_Toc268851783" Create and deploy Junk E-mail Filter lists PAGEREF _Toc268851783 \h 135
HYPERLINK \l "_Toc268851784" Configure the Junk E-mail Filter PAGEREF _Toc268851784 \h 136
HYPERLINK \l "_Toc268851785" Configure automatic picture download PAGEREF _Toc268851785 \h 137
HYPERLINK \l "_Toc268851786" Customize Outlook profiles by using an Outlook Profile (PRF) file PAGEREF _Toc268851786 \h 138
HYPERLINK \l "_Toc268851787" Overview PAGEREF _Toc268851787 \h 138
HYPERLINK \l "_Toc268851788" Before you begin PAGEREF _Toc268851788 \h 138
HYPERLINK \l "_Toc268851789" Procedures PAGEREF _Toc268851789 \h 138
HYPERLINK \l "_Toc268851790" Create a .prf file PAGEREF _Toc268851790 \h 139
HYPERLINK \l "_Toc268851791" Manually edit a .prf file PAGEREF _Toc268851791 \h 139
HYPERLINK \l "_Toc268851792" Apply a .prf file PAGEREF _Toc268851792 \h 144
HYPERLINK \l "_Toc268851793" Configure SharePoint Workspace 2010 PAGEREF _Toc268851793 \h 146
HYPERLINK \l "_Toc268851794" Configure and customize SharePoint Workspace 2010 PAGEREF _Toc268851794 \h 147
HYPERLINK \l "_Toc268851795" Before you begin PAGEREF _Toc268851795 \h 147
HYPERLINK \l "_Toc268851796" Review customization options for SharePoint Workspace 2010 PAGEREF _Toc268851796 \h 148
HYPERLINK \l "_Toc268851797" Control use of Groove workspaces PAGEREF _Toc268851797 \h 148
HYPERLINK \l "_Toc268851798" Enable IPv6 PAGEREF _Toc268851798 \h 148
HYPERLINK \l "_Toc268851799" Prefer IPv4 PAGEREF _Toc268851799 \h 149
HYPERLINK \l "_Toc268851800" Remove legacy files and registry settings PAGEREF _Toc268851800 \h 149
HYPERLINK \l "_Toc268851801" Prevent Windows Search crawling for SharePoint Workspace PAGEREF _Toc268851801 \h 149
HYPERLINK \l "_Toc268851802" Force Secure Socket Layer protection for external connections PAGEREF _Toc268851802 \h 149
HYPERLINK \l "_Toc268851803" Customize SharePoint Workspace in a managed environment PAGEREF _Toc268851803 \h 150
HYPERLINK \l "_Toc268851804" Customize SharePoint Workspace 2010 by using Active Directory Group Policy objects or Office Customization Tool settings PAGEREF _Toc268851804 \h 150
HYPERLINK \l "_Toc268851805" Verify installation PAGEREF _Toc268851805 \h 152
HYPERLINK \l "_Toc268851806" Test SharePoint Workspace connections PAGEREF _Toc268851806 \h 153
HYPERLINK \l "_Toc268851807" Before you begin PAGEREF _Toc268851807 \h 153
HYPERLINK \l "_Toc268851808" Test SharePoint Workspace synchronization with SharePoint Server PAGEREF _Toc268851808 \h 153
HYPERLINK \l "_Toc268851809" Test Groove workspace synchronization among peer clients PAGEREF _Toc268851809 \h 155
HYPERLINK \l "_Toc268851810" Deploy Office 2010 PAGEREF _Toc268851810 \h 157
HYPERLINK \l "_Toc268851811" Run Setup from a network installation point PAGEREF _Toc268851811 \h 159
HYPERLINK \l "_Toc268851812" Install an Office 2010 product PAGEREF _Toc268851812 \h 159
HYPERLINK \l "_Toc268851813" Precache the local installation source for Office 2010 PAGEREF _Toc268851813 \h 161
HYPERLINK \l "_Toc268851814" Deploy the local installation source PAGEREF _Toc268851814 \h 161
HYPERLINK \l "_Toc268851815" Run Setup from the local installation source to install Office 2010 PAGEREF _Toc268851815 \h 163
HYPERLINK \l "_Toc268851816" Run Setup PAGEREF _Toc268851816 \h 163
HYPERLINK \l "_Toc268851817" MSOCache folder PAGEREF _Toc268851817 \h 164
HYPERLINK \l "_Toc268851818" Office product download codes PAGEREF _Toc268851818 \h 164
HYPERLINK \l "_Toc268851819" Deploy Office 2010 to users who are not administrators PAGEREF _Toc268851819 \h 165
HYPERLINK \l "_Toc268851820" Logging on as an administrator PAGEREF _Toc268851820 \h 166
HYPERLINK \l "_Toc268851821" Using a software management tool PAGEREF _Toc268851821 \h 166
HYPERLINK \l "_Toc268851822" Deploying Office by using Group Policy computer startup scripts PAGEREF _Toc268851822 \h 166
HYPERLINK \l "_Toc268851823" Using application virtualization PAGEREF _Toc268851823 \h 166
HYPERLINK \l "_Toc268851824" Deploy Office 2010 with limited network capacity PAGEREF _Toc268851824 \h 167
HYPERLINK \l "_Toc268851825" Recommended solution PAGEREF _Toc268851825 \h 167
HYPERLINK \l "_Toc268851826" How this solution works PAGEREF _Toc268851826 \h 167
HYPERLINK \l "_Toc268851827" Deploy Office 2010 by running Setup from a network share PAGEREF _Toc268851827 \h 169
HYPERLINK \l "_Toc268851828" Deploying in a test environment PAGEREF _Toc268851828 \h 170
HYPERLINK \l "_Toc268851829" Resources for configuring the test computers PAGEREF _Toc268851829 \h 170
HYPERLINK \l "_Toc268851830" Preparing the infrastructure PAGEREF _Toc268851830 \h 171
HYPERLINK \l "_Toc268851831" Customizing the installation PAGEREF _Toc268851831 \h 172
HYPERLINK \l "_Toc268851832" Running Setup from the network installation point PAGEREF _Toc268851832 \h 175
HYPERLINK \l "_Toc268851833" Deploy Office 2010 by using System Center Configuration Manager 2007 PAGEREF _Toc268851833 \h 177
HYPERLINK \l "_Toc268851834" Overview of the deployment process PAGEREF _Toc268851834 \h 177
HYPERLINK \l "_Toc268851835" Deploying Office 2010 in a test environment PAGEREF _Toc268851835 \h 178
HYPERLINK \l "_Toc268851836" Network environment PAGEREF _Toc268851836 \h 178
HYPERLINK \l "_Toc268851837" Procedural steps for deploying Office 2010 by using Configuration Manager 2007 PAGEREF _Toc268851837 \h 179
HYPERLINK \l "_Toc268851838" Resources for deploying the infrastructure PAGEREF _Toc268851838 \h 184
HYPERLINK \l "_Toc268851839" Active Directory, DNS, DHCP PAGEREF _Toc268851839 \h 184
HYPERLINK \l "_Toc268851840" SQL Server 2008 PAGEREF _Toc268851840 \h 184
HYPERLINK \l "_Toc268851841" System Center Configuration Manager 2007 SP2 (Management Point, Distribution Point) PAGEREF _Toc268851841 \h 184
HYPERLINK \l "_Toc268851842" Windows Vista Enterprise, System Center Configuration Manager client PAGEREF _Toc268851842 \h 184
HYPERLINK \l "_Toc268851843" Deploy Office 2010 by using System Center Essentials 2010 PAGEREF _Toc268851843 \h 185
HYPERLINK \l "_Toc268851844" Deploying Office 2010 in a test environment PAGEREF _Toc268851844 \h 185
HYPERLINK \l "_Toc268851845" Network environment PAGEREF _Toc268851845 \h 185
HYPERLINK \l "_Toc268851846" Procedural steps for deploying Office 2010 by using System Center Essentials 2010 PAGEREF _Toc268851846 \h 186
HYPERLINK \l "_Toc268851847" Create a Setup customization file for Office 2010 PAGEREF _Toc268851847 \h 186
HYPERLINK \l "_Toc268851848" Create a computer group PAGEREF _Toc268851848 \h 187
HYPERLINK \l "_Toc268851849" Create and distribute a package for Office 2010 PAGEREF _Toc268851849 \h 187
HYPERLINK \l "_Toc268851850" Verify package deployment status PAGEREF _Toc268851850 \h 188
HYPERLINK \l "_Toc268851851" Resources for deploying the infrastructure PAGEREF _Toc268851851 \h 188
HYPERLINK \l "_Toc268851852" System Center Essentials 2010 PAGEREF _Toc268851852 \h 188
HYPERLINK \l "_Toc268851853" Active Directory, DNS, DHCP PAGEREF _Toc268851853 \h 188
HYPERLINK \l "_Toc268851854" SQL Server 2008 PAGEREF _Toc268851854 \h 188
HYPERLINK \l "_Toc268851855" Windows 7 PAGEREF _Toc268851855 \h 189
HYPERLINK \l "_Toc268851856" Deploy Office 2010 by using Group Policy computer startup scripts PAGEREF _Toc268851856 \h 190
HYPERLINK \l "_Toc268851857" Deploying Office 2010 in a test environment PAGEREF _Toc268851857 \h 190
HYPERLINK \l "_Toc268851858" Network environment PAGEREF _Toc268851858 \h 190
HYPERLINK \l "_Toc268851859" Customize Setup for Office 2010 PAGEREF _Toc268851859 \h 191
HYPERLINK \l "_Toc268851860" Configure script on domain controller PAGEREF _Toc268851860 \h 192
HYPERLINK \l "_Toc268851861" Verify computer startup script status PAGEREF _Toc268851861 \h 195
HYPERLINK \l "_Toc268851862" Deploy Office 2010 by using Microsoft Application Virtualization PAGEREF _Toc268851862 \h 197
HYPERLINK \l "_Toc268851863" Overview of Application Virtualization PAGEREF _Toc268851863 \h 197
HYPERLINK \l "_Toc268851864" Audience PAGEREF _Toc268851864 \h 197
HYPERLINK \l "_Toc268851865" Prerequisites PAGEREF _Toc268851865 \h 197
HYPERLINK \l "_Toc268851866" Introduction to the deployment process PAGEREF _Toc268851866 \h 197
HYPERLINK \l "_Toc268851867" Deploy Office 2010 in a test environment PAGEREF _Toc268851867 \h 198
HYPERLINK \l "_Toc268851868" Create a sequenced package for Office 2010 PAGEREF _Toc268851868 \h 198
HYPERLINK \l "_Toc268851869" Publish a sequenced package for Office 2010 PAGEREF _Toc268851869 \h 200
HYPERLINK \l "_Toc268851870" Configure the client computer to run Office 2010 PAGEREF _Toc268851870 \h 200
HYPERLINK \l "_Toc268851871" Resources to deploy the infrastructure PAGEREF _Toc268851871 \h 201
HYPERLINK \l "_Toc268851872" Deploy Microsoft Silverlight with Office 2010 PAGEREF _Toc268851872 \h 202
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at:
itspdocs@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
http://support.microsoft.com
Configuring and deploying Office 2010
This section provides how-to information for specific deployment tasks, such as customizing the installation, and installing Microsoft Office 2010 on users' computers. It also provides information about the new licensing options for Office 2010, including instructions for configuring the infrastructure for volume licensing and activation.
In this section:
ArticleDescriptionHYPERLINK \l "z0327f69ab9084a72bbc29be13e359115"Configure and deploy volume activation of Office 2010Provides information and procedures to help you plan the volume activation of Office 2010.HYPERLINK \l "z46d26f2e4eba4d419d66a7f3fd383501"Prepare the infrastructure for Office 2010Provides information and procedures to create a network installation point for the deployment of Office 2010.HYPERLINK \l "z64c1901c2b1546fdadc64df6c1b4c347"Customize the installation for Office 2010Provides information and procedures for customizing the Office 2010 installation, including customizing Setup options, configuring user settings, configuring silent installations, and importing Setup customization files. This section also includes information and procedures for customizing Outlook and Microsoft SharePoint Workspace 2010.HYPERLINK \l "z90ae3e01b598478caf6f8d24de33a9c3"Deploy Office 2010Provides information and procedures for running Setup for Office 2010, precaching the local installation source, and deploying to users who are not administrators.
Configure and deploy volume activation of Office 2010
Once you complete the volume activation planning phase for your organization, the next step is to deploy the volume activation methods you have chosen. This section describes how to deploy volume activation.
In this section:
ArticleDescriptionHYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010Provides information about how to deploy Volume License editions of Microsoft Office 2010 through Office Activation Technologies.HYPERLINK \l "z1825df767e23459ba6c1224dd6eab81e"Tools to configure client computers in Office 2010Describes the tools available for configuring and testing Volume License editions of Office 2010 through Office Activation Technologies.HYPERLINK \l "zdbff777c3a2d4d8ea7be6c45900c73c2"Volume activation quick start guide for Office 2010Provides information and procedures to quickly activate Volume License editions of Office 2010 through Office Activation Technologies.
See Also
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
Deploy volume activation of Office 2010
This article describes how to deploy Office Activation Technologies. Before you read this article, we recommend that you read HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx). For additional planning resources, see Evaluate Client Connectivity in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183041"Volume Activation for Windows Planning Guide (http://go.microsoft.com/fwlink/?LinkId=183041).
In this article:
H Y P E R L I N K \ l " z 6 1 " P r e p a r e a n d c o n f i g u r e t h e O f f i c e 2 0 1 0 c l i e n t
H Y P E R L I N K \ l " z 6 2 " P r e p a r e a n d c o n f i g u r e t h e K M S h o s t
H Y P E R L I N K \ l " z 6 3 " C o n f i g u r e D N S
H Y P E R L I N K \ l " z 6 4 " D e p l o y V i s i o 2 0 1 0
H Y P E R L I N K \ l " z 6 5 " P o s t - d e p l o y m e n t
P r e p a r e a n d c onfigure the Office 2010 client
You must decide whether each computer in your organization is to be activated by using Key Management Service (KMS) or Multiple Activation Key (MAK). The product key that is installed on the computer indicates whether Microsoft Office 2010 is to activate through KMS or MAK. This section describes how to enter the product key.
Important:
If you deploy an image or create a virtual machine (VM), you must rearm the installation of Office 2010 before you capture the image or VM. For more information, see HYPERLINK \l "z66"Rearm the Office 2010 installation later in this article.
KMS clients
In the 2007 Microsoft Office system and previous versions of Microsoft Office, you had to enter a product key when you deployed Office. If you use Key Management Service (KMS), you do not have to do this for Office 2010, because all volume license editions of Office 2010 have a KMS client key preinstalled.
Important
B y d e f a u l t , M i c r o s o f t V i s i o 2 0 1 0 i s p r e i n s t a l l e d w i t h t h e M i c r o s o f t V i s i o P r e m i u m 2 0 1 0 K M S c l i e n t k e y , w h i c h e n a b l e s a l l t h e f e a t u r e s t h a t a r e a v a i l a b l e f o r V i s i o P r e m i u m 2 0 1 0 . I f y o u r l i c e n s e a g r e e m e n t w i t h M i c r o s o f t i s f o r V i s i o S t a n d a r d 2 0 1 0 o r V i s i o Professional 2010, you must enter the appropriate KMS client key as described in HYPERLINK \l "z64"Deploy Visio 2010 later in this article.
Only one key must be installed and activated on the Office 2010 KMS host to activate all volume license editions of Office 2010 KMS clients. If the Office 2010 KMS host is installed and configured, KMS activation occurs transparently to the user when an Office 2010 client first installs.
For additional configuration options, such as how to specify the KMS host name on t h e K M S c l i e n t , s e e H Y P E R L I N K \ l " z 1 8 2 5 d f 7 6 7 e 2 3 4 5 9 b a 6 c 1 2 2 4 d d 6 e a b 8 1 e " T o o l s t o c o n f i g u r e c l i e n t c o m p u t e r s i n O f f i c e 2 0 1 0 .
M A K c l i e n t s
I f y o u u s e M u l t i p l e A c t i v a t i o n K e y ( M A K ) , y o u m u s t e n t e r t h e M A K k e y b y u s i n g o n e o f t h e f o l l o w i n g s u p p o r t e d m e t h o d s :
B e f o r e y o u d e p l o y O f f i c e 2 0 1 0
O f f i c e C u s t o m i z a t i o n T o o l ( O C T )
C o n f i g . x m l f i l e
A f t e r y o u d e p l o y O f f i c e 2 0 1 0
V o l u m e A c t i v a t i o n M a n a g e m e n t T o o l ( V A M T ) 2 . 0
T h e B a c k s t a g e v i e w
T h e o s p p . v b s s c r i p t
I m p o r t a n t :
B e c a u s e d i f f e r e n t p r o d u c t s r e q u i r e d i f f erent MAK keys, you should first verify that the MAK key for the product is correct.
Office Customization Tool (OCT)
To enter a MAK by using the OCT, follow these steps:
1. In the Type a valid 25-character volume license key with no spaces field, enter the MAK key (five sets of five numbers or characters), and then press ENTER.
2. After making any other necessary changes in the OCT, save the .msp file.
Remember that you do not have to enter a product key in the OCT if you are using KMS activation. For more information about the OCT, see HYPERLINK \l "z9c14db60b59141f9a94b50627d2daa81"Customize Setup before installing Office 2010.
Config.xml file
To enter a MAK by using the Config.xml file, follow these steps:
1. Add the following line to the Config.xml file:
Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key.
2. To apply the settings in Config.xml, at a command prompt, type the following command, and then press ENTER:
Setup.exe /config
You do not have to enter the MAK key in the Config.xml file if you are using KMS activation. For more information about how to use the Config.xml file, see HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
Volume Activation Management Tool
Volume Activation Management Tool (VAMT) 2.0 is the recommended method if you need to change the product key on Office 2010 clients after installation. For additional information, see the Help file in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183042"VAMT 2.0 (http://go.microsoft.com/fwlink/?LinkId=183042). Perform the following steps:
1. Add the computer to the VAMT 2.0 view.
2. Under Product Keys, add a MAK key.
3. Right-click the computer name, and then select Install Product Key.
The Backstage view
This method lets you change the product key on one computer at a time. If you want to change multiple computers, follow these steps:
1. Open an Office 2010 application.
2. Click the File tab.
3. Click Help.
4. Click Change Product Key and enter the product key.
Note
An administrator can create a registry key that allows a standard user (a user who is not an administrator) to apply a MAK key and activate an Office 2010 application. This means that a standard user can switch a KMS client to MAK activation, manually activate a computer, and, if it is necessary, replace an existing MAK with a new MAK key. By default, all volume license editions of Office 2010 disable this behavior. To enable this behavior, add the following line to the Config.xml file:
Or, you can set the following registry key to enable or disable standard user (a user who is not an administrator) activation:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform]
Enable Standard User Activation: "UserOperations"=dword:00000001Disable Standard User Activation: "UserOperations"=dword:00000000 (Office 2010 volume license products default setting)
The ospp.vbs script
For information about how to enter a product key by using the ospp.vbs script, see HYPERLINK \l "z1825df767e23459ba6c1224dd6eab81e"Tools to configure client computers in Office 2010.
Rearm the Office 2010 installation
There is a 25-day grace period from the time of installation of KMS clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm y o u r O f f i c e 2 0 1 0 i n s t a l l a t i o n b e f o r e y o u c a p t u r e t h e i m a g e . R e a r m i n g i s i m p o r t a n t f o r t h e s e r e a s o n s :
T h e g r a c e t i m e r i s r e s e t t o 3 0 d a y s o f g r a c e .
T h e g r a c e t i m e r i s f r o z e n .
I f y o u d o n o t r e a r m , u s e r s s e e n o t i f i c a t i o n d i a l o g b o x e s a t t h e t i m e t h a t t h e i m a g e i s d e p l o y e d , i n s t e a d o f 2 5 - d a y s a f t e r d e p l o y m e n t . T h e 2 5 - d a y g r a c e p e r i o d a l l o w s a m p l e t i m e f o r a K M S h o s t t o b e f o u n d a n d a c t i v a t i o n t o s u c c e e d . I f a c t i v a t i o n i s s u c c e s s f u l , u s e r s d o n o t s e e n o t i f i c a t i o n s t o a c t i v a t e .
T h e c l i e n t m a c h i n e I D ( C M I D ) i s r e s e t .
T h e K M S h o s t c o u n t s t h e n u m b e r o f u n i q u e c l i e n t s b a s e d o n t h e C M I D .
U s e t h e c o m m a n d o s p p . v b s / d c m i d t o c h e c k t h e C M I D .
R e a r m i s a l s o r e c o m m e n d e d f o r M A K d e p l o y m e n t . I f y o u a r e d e p l o y i n g O f f i c e 2 0 1 0 c o n f i g u r e d f o r M A K a c t i v a t i o n , a n d y o u d i d not remotely activate for end-users through VAMT 2.0 or ospp.vbs, users will see an activation dialog box the first time that an Office 2010 application starts. The activation dialog box is slightly different 25 days after installation. Also, users might immediately see a red title bar if Office 2010 had not been rearmed before image capture.
To rearm your Office 2010 installation
1. Make sure all Office 2010 applications are closed.
2. Open an elevated command prompt.
3. Go to %installdir%\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform. If you installed the 32-bit edition of Office 2010 on a 64-bit operating system, %Program Files% is the Program Files (x86) folder.
4. Run ospprearm.exe. If you see a message that indicates success, you are ready for image capture.
Important:
Do not open an Office application, ospp.vbs, or anything related to Office 2010. Doing so starts the grace timer.
5. Capture the image or save the VM.Prepare and configure the KMS host
This section contains information about how to prepare and configure the Office 2010 KMS host to enable Office 2010 clients to activate through KMS.
Important:
At minimum, membership in the Administrators group of the KMS host server is required to prepare and configure the KMS host.
Set up and activate the KMS host
Only the following operating systems can serve as the Office 2010 KMS host:
W i n d o w s S e r v e r 2 0 0 3 o r w i t h a n y s e r v i c e p a c k s
V o l u m e l i c e n s e e d i t i o n s o f W i n d o w s 7
W i n d o w s S e r v e r 2 0 0 8 R 2
I m p o r t a n t :
T h e K M S h o s t k e y f o r O f f i c e 2 0 1 0 i s n o t s p e c i f i c t o a p a r t i c u l a r o p e r a t i n g s y s t e m . I t i s d e s i g n e d t o b e u s e d o n a n y o f t h e o p e r a t i n g s y s t e m s m e n t i o n e d e a r l i e r . T h i s i n c l u d e s b o t h 3 2 - b i t a n d 6 4 - b i t e d i t i o n s .
T h e f o l l o w i n g o p e r a t i n g s y s t e m s a r e n o t s u p p o r t e d a s t h e O f f i c e 2 0 1 0 K M S h o s t :
W i n d o w s V i s t a o r w i t h a n y s e r v i c e p a c k s
W i n d o w s S e r v e r 2 0 0 8 o r w i t h a n y s e r v i c e p a c k s
F o r m o r e i nformation, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=151726"Volume Activation 2.0 for Windows Vista and Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=151726).
Co-hosting with a Windows KMS host
If currently you have a Windows KMS host running on an operating system that supports an Office KMS host, we recommend that you use the same computer as your Office KMS host. You still need to run the steps in the following sections to install and activate an Office 2010 KMS host key. For more information, see HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx).
To activate a KMS host on Windows Server 2003
1. If you do not have Key Management Service (KMS) 1.2 on Windows Server 2003, follow the instructions specified in Microsoft Knowledge Base article HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183046" 968915: An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=183046).
2. To download and run KeyManagementServiceHost.exe, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=169244"Microsoft Office 2010 KMS Host License Pack (http://go.microsoft.com/fwlink/?LinkID=169244).
3. When prompted, enter your KMS host key.
4. When prompted, continue with the activation. If your KMS host does not have an Internet connection, see HYPERLINK \l "z69"To activate a KMS host by telephone later in this article.
5. If you have a firewall enabled, open TCP port 1688, which is the default port number.
To activate a KMS host on Windows 7 or Windows Server 2008 R2
1. On the HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=169244"Microsoft Office 2010 KMS Host License Pack (http://go.microsoft.com/fwlink/?LinkID=169244) Web site, download and then run KeyManagementServiceHost.exe.
2. When prompted, enter your KMS host key.
3. When prompted, continue with the activation. If your KMS host does not have an Internet connection, see HYPERLINK \l "z69"To activate a KMS host by telephone later in this article.
4. If you have a firewall enabled, follow these steps to enable KMS through the firewall:
a. In Control Panel, open Windows Firewall.
b. Click the Allow a program through Windows Firewall link.
c. Click the Change Settings button.
d. Select the Key Management Service check box, and then click OK.Activating a KMS host by telephone
If your KMS host does not have an Internet connection, you can activate the KMS host by telephone.
To activate a KMS host by telephone
1. Run the following command under C:\Windows\system32. The result is the installation ID for Office 2010. You will type this installation ID number into the telephone in Step 3.
cscript slmgr.vbs /dti bfe7a195-4f8f-4f0b-a622-cf13c7d16864
Note:
The bfe7a195-4f8f-4f0b-a622-cf13c7d16864 value is the Office 2010 activation ID. Therefore, paste this value exactly as shown. We recommend pasting this number into Notepad, and then breaking the number up into six groups of six numbers.
1. Run slui.exe 4, and then call the telephone number displayed.
Note:
Ignore the installation ID shown in the dialog box. This is for Windows.
2. As you are prompted, enter each group of six numbers. This is the installation ID for Office 2010 that you obtained in Step 1.
3. When you hear the response, write down the numbers.
4. Run cscript slmgr.vbs /atp xxxxxxxxxxxx bfe7a195-4f8f-4f0b-a622-cf13c7d16864, where xxxxxxxxxxxx is the confirmation ID that you receive by telephone (there should be 48 numbers).
Note:
The bfe7a195-4f8f-4f0b-a622-cf13c7d16864 value is the Office 2010 activation ID. Therefore, paste this value exactly as shown.
5. You should see a message that the confirmation ID was successfully deposited.Sppsvc state stopped error
Because the KMS host service automatically stops, you might encounter the following error when you run KeyManagementServiceHost.exe.
Error: The Software Protection Platform service is not running: sppsvc State: Stopped
If you receive this error, perform the following:
1. At the command prompt, type the following command, and then press ENTER:
net start sppsvc
2. Re-run KeyManagementServiceHost.exe.
Alternately, you can perform the following:
1. Right-click My Computer and select Manage.
2. Under Services and Applications, select Software Protection Service.
3. Click Start, and then OK to start the service.
4. Re-run KeyManagementServiceHost.exe.
Manually install the Office 2010 KMS host key and activate
KeyManagementServiceHost.exe installs the Office 2010 KMS host license files on your KMS host. KeyManagementServiceHost.exe also prompts you for an Office 2010 KMS host key and attempts activation. If you did not enter the Office 2010 KMS host key correctly, run KeyManagementServiceHost.exe again.
The slmgr.vbs script
If you want to manually enter the Office 2010 KMS host key and activate it, use the slmgr.vbs script. For more information, see HYPERLINK \l "z612"Configure the Office 2010 KMS host later in this article. Open an elevated command prompt, and then run the following commands:
slmgr.vbs /ipk
slmgr.vbs /ato
The Office 2010 activation ID is bfe7a195-4f8f-4f0b-a622-cf13c7d16864.
Configure the Office 2010 KMS host
The Software License Manager (slmgr.vbs) script is used to configure and retrieve volume activation information for the Office 2010 KMS host, in addition to the Windows host. For more information about this script, see KMS Activation in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183043"Windows Volume Activation Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=183043).
The script can be run locally on the target computer or remotely from another computer. If a standard user runs slmgr.vbs, some license data might be missing or incorrect, and many operations are prohibited.
The slmgr.vbs script can use wscript.exe or cscript.exe, and administrators can specify which script engine to use. If no script engine is specified, slmgr.vbs runs by using the default script engine, wscript.exe. The cscript.exe script engine is recommended.
The Software Licensing Service must be restarted for any changes to take effect. To restart the Software Licensing Service, use the Microsoft Management Console (MMC) Services snap-in or run the following command:
net stop sppsvc && net start sppsvc
The slmgr.vbs script requires at least one parameter. If the script is run that has no parameters, it displays help information. The following table lists slmgr.vbs command-line options, and a description of each. Most of the parameters in the table configure the KMS host. However, the parameters /sai and /sri are passed to KMS clients after they make contact with the host. The general syntax of slmgr.vbs is as follows (assuming cscript.exe is the script engine that you are using):
cscript slmgr.vbs /parameter
cscript slmgr.vbs [ComputerName] [User] [Password] [Option]
ComputerNameName of remote computer. If a computer name is not passed local computer is used.
UserAccount with required permission on remote computer.
PasswordPassword for the account. If a user account and password are not passed, current credentials are used.
OptionOptions are shown in the following table.
OptionDescription/ipk [ProductKey]Installs the product key for Windows (default) or other application identified by the product key./ato [ActivationID]Activates the KMS host for Windows (default), or the application identified by the Activation ID when provided. The Office 2010 Activation ID is bfe7a195-4f8f-4f0b-a622-cf13c7d16864./dlv [ActivationID]Displays detailed license information for Windows (default), or the application identified by the Activation ID when provided. The Office 2010 Activation ID is bfe7a195-4f8f-4f0b-a622-cf13c7d16864./dli [ActivationID]Displays license information for Windows (default), or the application identified by the application ID when provided. The Office 2010 Activation ID is bfe7a195-4f8f-4f0b-a622-cf13c7d16864./upk [ActivationID]Uninstalls the product key for Windows (default) or other application identified by the Activation ID when provided. The Office 2010 Activation ID is bfe7a195-4f8f-4f0b-a622-cf13c7d16864.
Caution:
If you intend to uninstall the product key for Office 2010, for example, and inadvertently forget to enter the Activation ID, all installed product keys will be uninstalled, including the one for Windows./sprt [PortNumber]Sets the TCP communications port on a KMS host. Replaces PortNumber with the TCP port number to use. The default setting is 1688./cdnsDisables automatic DNS publishing by a KMS host./sdnsEnables automatic DNS publishing by the KMS host./cpriLowers the priority of KMS host processes./sai [ActivationInterval]Changes how often a KMS client attempts to activate itself when it cannot find a KMS host. Replaces ActivationInterval with a number of minutes. The default setting is 120./sri [RenewalInterval]Changes how often a KMS client attempts to renew its activation by contacting a KMS host. Replaces RenewalInterval with a number of minutes. The default setting is 10080 (7 days). This setting overrides the local KMS client settings.Verify successful activation of the Office KMS host
To verify that the Office 2010 KMS host key is successfully installed and activated, use the slmgr.vbs script. Open an elevated command prompt on the KMS host, type the following command, and then press ENTER:
cscript slmgr.vbs /dlv all
To view information only for Office 2010, specify the Activation ID after the /dlv parameter:
cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864
The output should resemble the following:
Name: Microsoft Office 2010, KMSHost edition
Description: Microsoft Office 2010 KMS, VOLUME_KMS channel
Activation ID: bfe7a195-4f8f-4f0b-a622-cf13c7d16864
Application ID: 59a52881-a989-479d-af46-f275c6370663
Extended PID: 55041-00096-199-000004-03-1033-7600.0000-3632009
Installation ID: 008585014214769124199722184000850026888810090785321136
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: RP3HH
License Status: Licensed
Remaining Windows rearm count: 1
Trusted time: 12/29/2009 1:45:54 PM
Key Management Service is enabled on this computer
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
If the output shows License Status: Licensed, the Office 2010 KMS host key is successfully installed and activated.
Once KMS clients send requests for activation, the current count is incremented. The current count must be 5 or greater before KMS clients activate. The maximum current count will be twice the activation threshold, or 10. Administrators can also check the KMS log that is in the Applications and Services Logs folder for event ID12290, the ID for KMS-related activity. The KMS log records activation requests from KMS clients. Each event displays the name of the computer and the time stamp of each activation request.
Configure DNS
KMS hosts automatically publish their existence by creating service (SRV) resource records (RRs) on the DNS server. If there is only one KMS host and dynamic update, no action is required for the KMS host to create the SRV RR that publishes the KMS service location.
If there is more than one KMS host, only the first KMS host can create an SRV RR. Subsequent KMS hosts cannot change or update SRV RRs unless the default permissions on the DNS server are changed.
Changing the default permissions on the DNS server requires administrative rights in the domain, and the KMS hosts must all belong to the same Active Directory Domain Services (ADDS) domain. Create a global security group in ADDS for your KMS hosts. Add each KMS host to the new security group, and set the permissions on the DNS server to allow updates by members of the newly created security group.
For more information about how to configure DNS for the KMS host, see Understanding KMS in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=187539"Customer Hosted Volume Activation Guide (http://go.microsoft.com/fwlink/?LinkId=187539).
Deploy Visio 2010
By default, Visio 2010 is preinstalled with the Visio Premium 2010 KMS client key, which enables all the features that are available for Visio Premium 2010. If you are licensed to use Visio Standard 2010 or Visio Professional 2010, you must install the appropriate KMS client key. Different features or applications are available depending on the type of key that is installed. This makes it easier for you to upgrade or downgrade without having to deploy a different product edition.
If you already deployed Visio 2010, you can remotely install the new KMS client key by using either of the following options:
T h e o s p p . v b s s c r i p t F o r m o r e i n f o r m a t i o n a b o u t o s p p . v b s , s e e H Y P E R L I N K \ l " z 1 8 2 5 d f 7 6 7 e 2 3 4 5 9 b a 6 c 1 2 2 4 d d 6 e a b 8 1 e " T o o l s t o c o n f i g u r e c l i e n t c o m p u t e r s i n O f f i c e 2 0 1 0 .
V A M T 2 . 0 T h i s a l l o w s y o u t o s e e w h i c h p r o d u c t s a r e i n s t a l l e d i n e a c h c o m p u t e r . I f y o u see installations of Visio Premium 2010 in VAMT 2.0, you can remotely install the Visio Professional 2010 or the Visio Standard 2010 KMS client key.
You must restart Visio 2010 for the new KMS client key to be recognized and the appropriate features enabled.
You can have the new KMS client key installed from a network share by entering the key in the Office Customization Tool (OCT). For more information, see HYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010.
If your license agreement with Microsoft is for Visio Standard 2010 or Visio Professional 2010, enter the appropriate KMS client key shown in the following table.
Visio editionKMS client keyVisio Standard 2010767HD-QGMWX-8QTDB-9G3R2-KHFGJVisio Professional 20107MCW8-VRQVK-G677T-PDJCM-Q8TCPVisio Premium 2010D9DWC-HPYVV-JGF4P-BTWQB-WX8BJPost-deployment
This section contains possible actions that might occur after Office 2010 deployment is completed.
Migrate an Office KMS host
After deployment of Office 2010, the network must undergo topology changes that require you to migrate your Office KMS host to another server on that network or on another network completely.
To migrate an Office KMS host
1. Uninstall the Office KMS host key by running the following command: cscript C:\windows\system32\ slmgr /upk [ActivationID]
2. Delete the record from the DNS as follows: open the DNS console, expand the _tcp node under domain.com, and then delete the _VLMCS record. Once you do this, the Office KMS host is uninstalled.
3. On the new server, install the product key for the Office KMS host by running the following command:cscript C:\windows\system32\ slmgr /ipk [ProductKey]
4. Activate the Office KMS host by running the following command: cscript C:\windows\system32\slmgr.vbs /ato 86f3489b-e730-45ee-ad42-039a64c82ba4
5. After activation is complete, restart the Software Licensing Service and verify in the DNS that the record is created for the new KMS host server.
6. To verify that the Office KMS host is configured correctly, check the KMS activation request count to see whether it is increasing. On the KMS host, the current count is displayed by running the following command: cscript C:\windows\system32\slmgr.vbs /dli
You can also check the Key Management Service log in the Applications and Services Logs folder for 12290 events, which is where activation requests from KMS clients are recorded. Each event displays the name of the computer and the time-stamp of the activation request.See Also
HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
HYPERLINK \l "z1825df767e23459ba6c1224dd6eab81e"Tools to configure client computers in Office 2010
HYPERLINK "http://technet.microsoft.com/library/976fc06b-faed-4682-b41f-4a19d8eb3302(Office.14).aspx"Troubleshoot volume activation for Office 2010 (http://technet.microsoft.com/library/976fc06b-faed-4682-b41f-4a19d8eb3302(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/22fefb4f-4317-4f3c-8122-f86bde77f3f0(Office.14).aspx"Plan KMS activation of Office 2010 (http://technet.microsoft.com/library/22fefb4f-4317-4f3c-8122-f86bde77f3f0(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/61bb4ce1-1d5f-4596-bd7d-21f2b867b376(Office.14).aspx"Plan MAK independent activation of Office 2010 (http://technet.microsoft.com/library/61bb4ce1-1d5f-4596-bd7d-21f2b867b376(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/9194ac1f-7285-4db3-b801-0d0166d6f998(Office.14).aspx"Plan MAK proxy activation of Office 2010 (http://technet.microsoft.com/library/9194ac1f-7285-4db3-b801-0d0166d6f998(Office.14).aspx)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=180346"Office Volume Activation forum (http://go.microsoft.com/fwlink/?LinkId=180346)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=180345"Office IT Pro forums (http://go.microsoft.com/fwlink/?LinkId=180345)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=195811"Office Resource Kit Blog (http://go.microsoft.com/fwlink/?LinkId=195811)
Tools to configure client computers in Office 2010
This article describes how to use tools to configure and test Volume License editions of Microsoft Office 2010. Before you read this article, we recommend that you read HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx), HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecb b 9 1 7 d c 4 ( O f f i c e . 1 4 ) . a s p x ) , a n d H Y P E R L I N K \ l " z b 4 1 8 5 0 1 a e b 8 3 4 9 9 1 8 e a 9 b 1 8 e 7 3 0 9 e 0 6 0 " D e p l o y v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0 .
I n t h i s a r t i c l e :
H Y P E R L I N K \ l " z 7 1 3 " T h e o s p p . v b s s c r i p t
H Y P E R L I N K \ l " z 7 1 4 " V A M T 2 . 0
T h e o s p p . v b s s c r i p t
T h e O f f i c e S o f t w a r e Protection Platform script (ospp.vbs script) enables you to configure volume editions of Office 2010 client products. You must open a command prompt by using administrator permissions and navigate to the folder that contains the script. The script is located in the %installdir%\Program Files\Microsoft Office\Office14 folder. If you are running 32-bit Office 2010 on a 64-bit operating system, the script is located in the %installdir%\Program Files (x86)\Microsoft Office\Office14 folder.
Running ospp.vbs requires the cscript.exe script engine. To see the Help file, type the following command, and then press ENTER:
cscript ospp.vbs /?
The general syntax is as follows:
cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]
OptionSpecifies the option and value to use to activate a product, install or uninstall a product key, install and display license information, set Key Management Service (KMS) host name and port, and remove KMS host. The options and values are listed in the tables in this section.
ComputerNameName of the remote computer. If a computer name is not provided, the local computer is used.
UserAccount that has the required permission on the remote computer.
PasswordPassword for the account. If a user account and password are not provided, the current credentials are used.
The following tables list the ospp.vbs options and values.
Global optionDescription/actActivates installed Office 2010 product keys./inpkey:valueInstalls a product key (replaces existing key) with user-provided product key. Value parameter required./unpkey:valueUninstalls an installed product key with the last five digits of the product key to uninstall (as displayed by the /dstatus option). Value parameter required./inslic:valueInstalls a license with user-provided path of the .xrm-ms license. Value parameter required./dstatusDisplays license information for installed product keys./dstatusallDisplays license information for all installed licenses./dinstidDisplays Installation ID for offline activation./actcid:valueActivates product with user-provided Confirmation ID. Value parameter required./puseropsPermits administrator-privileged license operations including Internet or telephone activation by standard users. This sets HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform\UserOperations =dword:00000001./duseropsDenies administrator-privileged license operations including Internet or telephone activation by standard users. This sets HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform\UserOperations =dword:00000000./ddescr:valueDisplays the description for a user-provided error code. Value parameter applies.
KMS client optionDescription/dhistorykmsDisplays KMS client activation history./dcmidDisplays KMS client machine ID (CMID)./sethst:valueSets a KMS host name with a user-provided host name. Value parameter applies. This sets HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName (REG_SZ)./setprt:valueSets a KMS port with a user-provided port number. Value parameter applies. This sets HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServicePort (REG_SZ)./remhstRemoves KMS host name (sets port to default).
OSPPSVC optionDescription/osppsvcrestartRestarts Office Software Protection Platform service./osppsvcautoSets Office Software Protection Platform service startup type to automatic. This is recommended for WindowsXP computers so that KMS reactivation attempts occur even if Office is not running.Scenarios that use ospp.vbs
The following scenarios assume that you are running ospp.vbs in an elevated command prompt.
Note:
Any changes that you make affect only the Office 2010 client products. You need to configure the Windows client separately by using the slmgr.vbs script. For more information about how to use slmgr.vbs, see HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
To change the product key to a MAK key on a remote computer
1. If the remote computer is named contoso1, run the following command to enter the product key. This assumes that you have administrator credentials on the remote computer. If your credentials on the remote computer differ from your logon name and password, you must type your logon name and password at the command line, and then press ENTER:
cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx contoso1
2. To activate the remote computer, type the following command, and then press ENTER:
cscript ospp.vbs /act contoso1To diagnose KMS activation errors
1. If the computer has the KMS client key installed, check the licensing status. To do this, type the following command, and then press ENTER:
cscript ospp.vbs /dstatusall
2. To check the KMS activation history, type the following command, and then press ENTER:
cscript ospp.vbs /dhistorykms
3. To trigger activation, type the following command, and then press ENTER:
cscript ospp.vbs /act
4. Check the error message for error code 0xC004F042. If you see an error code in the notification dialog boxes shown to the users, you can also use that code to check the error message. To do this, type the following command, and then press ENTER:
cscript ospp.vbs /ddescr:0xC004F042
To set test KMS host name, and then set to auto-discovery
1. If you are testing a KMS host named kmstest.contoso.com, and you want to specify it in the KMS client, type the following command, and then press ENTER:
cscript ospp.vbs /sethst:kmstest.contoso.com
Note:
If you change the default port on the KMS host, you must run ospp.vbs with the /setprt parameter.
2. To trigger activation, type the following command, and then press ENTER:
cscript ospp.vbs /act
3. To check the KMS activation history to see whether the host was successfully contacted, type the following command, and then press ENTER:
cscript ospp.vbs /dhistorykms
4. Now you want this KMS client to use Domain Name System (DNS) for auto-discovery of the production KMS host. To remove the KMS host name, type the following command, and then press ENTER:
cscript ospp.vbs /remhstGenerally, you do not have to configure Office KMS clients if the Office KMS host was correctly set up and configured. The KMS client automatically searches for the KMS host by using DNS and attempts activation. The KMS service uses service (SRV) resource records (RR) in DNS to store and communicate the locations of KMS hosts.
By default, KMS hosts automatically publish the information that KMS clients need to find and connect to them by using DNS dynamic update protocol. By default, KMS clients query the DNS server for KMS service information.
You can manually configure KMS hosts and clients, depending on the network configuration and security requirements. For example, if the network environment does not use SRV records, you can manually configure a KMS client to use a specific KMS host. For more information about how to configure the KMS client, see HYPERLINK \l "z713"The ospp.vbs script earlier in this article and HYPERLINK \l "z61"Prepare and configure the Office 2010 client in HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010. For more information about how to configure the KMS host, see HYPERLINK \l "z62"Prepare and configure the KMS host in HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
VAMT 2.0
The Volume Activation Management Tool (VAMT) 2.0 gives you a graphical user interface to manage volume activation. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183042"Volume Activation Management Tool (VAMT) 2.0 (http://go.microsoft.com/fwlink/?LinkId=183042) and the Help file that is included with VAMT 2.0.
See Also
HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010
HYPERLINK "http://technet.microsoft.com/library/976fc06b-faed-4682-b41f-4a19d8eb3302(Office.14).aspx"Troubleshoot volume activation for Office 2010 (http://technet.microsoft.com/library/976fc06b-faed-4682-b41f-4a19d8eb3302(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/22fefb4f-4317-4f3c-8122-f86bde77f3f0(Office.14).aspx"Plan KMS activation of Office 2010 (http://technet.microsoft.com/library/22fefb4f-4317-4f3c-8122-f86bde77f3f0(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/61bb4ce1-1d5f-4596-bd7d-21f2b867b376(Office.14).aspx"Plan MAK independent activation of Office 2010 (http://technet.microsoft.com/library/61bb4ce1-1d5f-4596-bd7d-21f2b867b376(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/9194ac1f-7285-4db3-b801-0d0166d6f998(Office.14).aspx"Plan MAK proxy activation of Office 2010 (http://technet.microsoft.com/library/9194ac1f-7285-4db3-b801-0d0166d6f998(Office.14).aspx)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=180346"Office 2010 Volume Activation forum (http://go.microsoft.com/fwlink/?LinkId=180346)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=180345"Office 2010 forums (http://go.microsoft.com/fwlink/?LinkId=180345)
Volume activation quick start guide for Office 2010
This article is a quick start guide for activating Volume License editions of Microsoft Office 2010. The intended audience is IT administrators who are familiar with Windows volume activation and want to know which steps are required for volume activation of Office client products. If you are not familiar with volume activation, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183040"Windows Volume Activation Planning Guide (http://go.microsoft.com/fwlink/?LinkId=183040), HYPERLINK "http://technet.microsoft.com/library/b41f7bc2-b7fa-43a3-963a-cf1c1ef8f331(Office.14).aspx"Plan for volume activation of Office 2010 (http://technet.microsoft.com/library/b41f7bc2-b7fa-43a3-963a-cf1c1ef8f331(Office.14).aspx), and HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
Volume License editions of Office 2010 require activation. The activation technology is based on the Windows Software Protection Platform. If you are familiar with Windows Key Management Service (KMS) or Multiple Activation Key ( M A K ) a c t i v a t i o n , t h e n y o u w i l l b e f a m i l i a r w i t h r e q u i r e m e n t s f o r O f f i c e 2 0 1 0 a c t i v a t i o n . T h e m a i n f o c u s o f t h i s a r t i c l e i s o n t h e d i f f e r e n c e s b e t w e e n W i n d o w s a n d O f f i c e , i n a d d i t i o n t o t h e s t e p s r e q u i r e d t o a c t i v a t e O f f i c e 2 0 1 0 .
I n t h i s a r t i c l e :
H Y P E R L I N K \ l " z 8 1 5 " D i f f e r e n c e s b e t w e e n W i n d o w s a n d O f f i c e a c t i v a t i o n
H Y P E R L I N K \ l " z 8 1 6 " S c e n a r i o s f o r O f f i c e 2 0 1 0 v o l u m e a c t i v a t i o n
H Y P E R L I N K \ l " z 8 1 7 " O f f i c e 2 0 1 0 v o l u m e a c t i v a t i o n m e t h o d s
H Y P E R L I N K \ l " z 8 1 8 " I n s t a l l a n d c o n f i g u r e t h e K M S h o s t
H Y P E R L I N K \ l " z 8 1 9 " C o - h o s t i n g a n O f f i c e K M S h o s t w i t h a W i n d o w s K M S h o s t
D i f f e r e n c e s b e t w e e n W i n d o w s a n d O f f i c e a c t i v a t i o n
D i f f e r e n c e s b e t w e e n W i n d o w s a c t i v a t i o n a n d O f f i c e a c t i v a t i o n w i t h r e g a r d t o b o t h K M S a n d M A K a r e a s f o l l o w s :
T h e a c t i v a t i o n t h r e s h o l d f o r t h e K M S h o s t i s f i v e c l i e n t c o m p u t e r s . F i v e p h y s i c a l o r v i r t u a l c o m p u t e r s t h a t h a v e O f f i c e i n s t a l l e d m u s t r e q u e s t a c t i v a t i o n b e f o r e K M S c l i e n t s b e c o m e a c t i v a t e d .
O n l y o n e K M S h o s t k e y m u s t b e i n s t a l l e d a n d a c t i v a t e d o n t h e O f f i c e K M S h o s t . T h i s K M S h o s t c a n t h e n a c t i v a t e a l l O f f i c e 2 0 1 0 p r o d u c t s w i t h t h e K M S c l i e n t k e y i n s t a l l e d .
W h e n u s i n g s l m g r . v b s c o m m a n d s o n t h e K M S h o s t , y o u m u s t e n t e r t h e O f f i c e 2 0 1 0 a c t i v a t i o n I D ( b f e 7 a 1 9 5 - 4 f 8 f - 4 f 0 b - a 6 2 2 - c f 1 3 c 7 d 1 6 8 6 4 ) . F o r m o r e i n f o r m a t i o n a b o u t t h e s l m g r . v b s s c r i p t , s e e H Y P E R L I N K \ l " z b 4 1 8 5 0 1 a e b 8 3 4 9 9 1 8 e a 9 b 1 8 e 7 3 0 9 e 0 6 0 " D e p l o y v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0 .
T o e n s u r e t h a t t h e O f f i c e 2 0 1 0 K M S h o s t k e y i s r e c o g n i z e d , y o u m u s t r u n K e y M a n a g e m e n t S e r v i c e H o s t . e x e t o i n s t a l l t h e O f f i c e l i c e n s e f i l e s .
N o te:
Each Office suite or product has its own MAK key. In addition, here are separate MAK keys for Microsoft Project 2010 and Microsoft Visio. For example, with a single MAK key you can activate all applications in the Microsoft Office Professional Plus 2010 suite, but you must enter separate MAK keys for Project 2010, Visio, or any of the Office Professional Plus 2010 suite products, such as Microsoft Word 2010 or Microsoft Excel 2010.
Scenarios for Office 2010 volume activation
Scenarios help users determine what best fits their current or proposed environment and to provide step-by-step guidance for activating the Volume License editions of Office 2010 software. The detailed steps for activation listed the scenarios apply to all Volume License editions of Office 2010 client products (Office Professional Plus 2010, Visio 2010, and Project 2010).
The scenarios are located in the following articles:
HYPERLINK "http://technet.microsoft.com/library/22fefb4f-4317-4f3c-8122-f86bde77f3f0(Office.14).aspx"Plan KMS activation of Office 2010 (http://technet.microsoft.com/library/22fefb4f-4317-4f3c-8122-f86bde77f3f0(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/61bb4ce1-1d5f-4596-bd7d-21f2b867b376(Office.14).aspx"Plan MAK independent activation of Office 2010 (http://technet.microsoft.com/library/61bb4ce1-1d5f-4596-bd7d-21f2b867b376(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/9194ac1f-7285-4db3-b801-0d0166d6f998(Office.14).aspx"Plan MAK proxy activation of Office 2010 (http://technet.microsoft.com/library/9194ac1f-7285-4db3-b801-0d0166d6f998(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/48981ae0-6ae9-4710-ae35-e8746150ffa3(Office.14).aspx"Scenario: Core network - KMS activation of Office 2010 (http://technet.microsoft.com/library/48981ae0-6ae9-4710-ae35-e8746150ffa3(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/faf4df6f-91a3-4ba3-b09e-811c179a7e62(Office.14).aspx"Scenario: Secure network - KMS or MAK activation of Office 2010 (http://technet.microsoft.com/library/faf4df6f-91a3-4ba3-b09e-811c179a7e62(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/2daa4365-c65d-4b40-a948-0f4da2a1e674(Office.14).aspx"Scenario: Roaming or disconnected computers - KMS or MAK activation of Office 2010 (http://technet.microsoft.com/library/2daa4365-c65d-4b40-a948-0f4da2a1e674(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/0be3bb58-d0a3-4ab3-9efc-21d5d1bba229(Office.14).aspx"Scenario: Test or development lab - KMS or MAK activation of Office 2010 (http://technet.microsoft.com/library/0be3bb58-d0a3-4ab3-9efc-21d5d1bba229(Office.14).aspx)
Office 2010 volume activation methods
There are two methods for activating Volume License editions of Office 2010: Key Management Service (KMS) and Multiple Activation Key (MAK).
KMS activation
KMS enables clients to activate on the local network. To do this, administrators must first set up a KMS host (see HYPERLINK \l "z818"Install and configure the KMS host). Office 2010 clients are preinstalled with a KMS client key. A user who is usually connected to the network can activate Office 2010 by connecting to the KMS host on the intranet. The activation process is invisible to the user and requires no user interaction. The computer that is running Office 2010 (the KMS client) can be configured for variable lengths of re-activation and renewal periods. If a KMS client fails to activate, the user will see notification messages 25 days after installation of Office 2010. If KMS clients are absent from the network for longer than 180 days after successful activation, users will see unlicensed notifications when they start Office 2010. However, there will be no functionality loss even if the licenses for KMS clients cannot be renewed. Upon successful activation, users no longer receive notifications.
MAK activation
If a KMS host is not available, the user can activate against Microsoft hosted activation servers, as long as the computer that is running Office 2010 uses a valid MAK key instead of the KMS client key. Administrators can change the product key from the KMS client key to the MAK key through the Office 2010 user interface (UI) or by using a script that calls OSPP WMI providers.
Install and configure the KMS host
Only the following operating systems can serve as the KMS host:
W i n d o w s S e r v e r 2 0 0 3 o r l a t e r v e r s i o n s
V o l u m e L i c e n s e e d i t i o n s o f W i n d o w s 7
W i n d o w s S e r v e r 2 0 0 8 R 2
I m p o r t a n t :
T h e K M S h o s t k e y f o r O f f i c e 2 0 1 0 i s n o t s p e c i f i c t o a p a r t i c u l a r o p e r a t i n g s y s t e m . I t i s d e s i g n e d t o b e u s e d o n a n y o f t h e o p e r a t i n g s y s t e m s t h a t w e r e m e n t i o n e d e a r l i e r , i n c l u d i n g b o t h 3 2 - b i t a n d 6 4 - b i t e d i t i o n s .
T h e f o l l o w i n g o p e r a t i n g s y s t e m s a r e n o t s u p p o r t e d a s t h e K M S h o s t :
W i n d o w s V i s t a o r a l a t e r v e r s i o n
W i n d o w s S e r v e r 2 0 0 8 i n c l u d i n g s e r v i c e p a c k s
F o r m o r e i n f o r m a t i o n , s e e H Y P E R L I NK "http://go.microsoft.com/fwlink/?LinkId=151726"Volume Activation 2.0 for Windows Vista and Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=151726).
Co-hosting an Office KMS host with a Windows KMS host
If currently you have a Windows KMS host running on an operating system that supports an Office KMS host, we recommend that you use the same computer for your Office KMS host. You still must perform the following steps to install and activate an Office 2010 KMS host key. For more information, see HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx).
To activate an Office KMS host on Windows Server 2003
1. If you do not have Key Management Service (KMS) 1.2 installed on Windows Server 2003, follow the instructions specified in Microsoft Knowledge Base article HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=183046"968915: An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=183046).
2. Download and run KeyManagementServiceHost.exe at HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=169244"Microsoft Office 2010 KMS Host License Pack (http://go.microsoft.com/fwlink/?LinkID=169244) Web site.
3. When prompted, enter your KMS host key.
4. When prompted, continue the activation process. If your KMS host does not have an Internet connection, see HYPERLINK \l "z69"To activate a KMS host by telephone in HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010 for instructions about how to activate the KMS host by telephone.
5. If you have a firewall enabled, open TCP port 1688. This is the default port number.
To activate an Office KMS host on Windows 7 or Windows Server 2008 R2
1. Download and run KeyManagementServiceHost.exe at HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=169244"Microsoft Office 2010 KMS Host License Pack (http://go.microsoft.com/fwlink/?LinkID=169244) Web site.
2. When prompted, enter your KMS host key.
3. When prompted, continue the activation process. If your KMS host does not have an Internet connection, see HYPERLINK \l "z69"To activate a KMS host by telephone in HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010 for instructions about how to activate the KMS host by telephone.
4. If you have a firewall enabled, perform the following steps to enable KMS through the firewall:
a. In Control Panel, open Windows Firewall.
b. Click Allow a program or feature through Windows Firewall.
c. Click Change Settings.
d. Select the Key Management Service check box, and then click OK.See Also
HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010
HYPERLINK \l "z1825df767e23459ba6c1224dd6eab81e"Tools to configure client computers in Office 2010
HYPERLINK "http://technet.microsoft.com/library/976fc06b-faed-4682-b41f-4a19d8eb3302(Office.14).aspx"Troubleshoot volume activation for Office 2010 (http://technet.microsoft.com/library/976fc06b-faed-4682-b41f-4a19d8eb3302(Office.14).aspx)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=180346"Office 2010 Volume Activation forum (http://go.microsoft.com/fwlink/?LinkId=180346)
HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=180345"Office 2010 forums (http://go.microsoft.com/fwlink/?LinkId=180345)
Prepare the infrastructure for Office 2010
This section provides information about how to create a network installation point by using the Microsoft Office 2010 source files.
In this section:
ArticleDescriptionHYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010Provides information and procedures to create, replicate, and secure a network installation point for the deployment of Office 2010.
Create a network installation point for Office 2010
This article describes how to create, replicate, and secure a network installation point for the deployment of Microsoft Office 2010. Typically, this is the first step in a corporate deployment of Office 2010. To do this, you copy all the source files from the Office installation CD to a shared location on the network. Users run Setup from the network installation point, or you use the installation point as a starting place to create a hard-disk image or a custom CD or to distribute Office by using a software deployment tool, such as Microsoft Syst e m C e n t e r C o n f i g u r a t i o n M a n a g e r 2 0 1 0 .
I n t h i s a r t i c l e :
H Y P E R L I N K \ l " z 1 0 2 0 " C r e a t e t h e n e t w o r k i n s t a l l a t i o n p o i n t
H Y P E R L I N K \ l " z 1 0 2 1 " R e p l i c a t e t h e n e t w o r k i n s t a l l a t i o n p o i n t
H Y P E R L I N K \ l " z 1 0 2 2 " S e c u r e t h e n e t w o r k i n s t a l l a t i o n p o i n t
C r e a t e t he network installation point
Use the following procedure to create a network installation point.
To create a network installation point
1. Create a folder for the Office source files at a location that can be easily accessed on the server. For example:
\\server\share\Office14
Note:
Do not create the network installation point at the root of the server.
2. Insert the Office CD into your CD drive.
3. In Windows Explorer, select all the files and folders on the CD. Copy the CD contents to the folder on the network. This location becomes the network installation point.
4. If you deploy multiple language versions of Office 2010, copy each language pack that you want from the source media to the installation point. When you are prompted to overwrite duplicate Setup files, click No.
Note:
In Office 2010, core Setup files are shared among all Office products and language packs. Because these core Setup files are identical, there is no reason to overwrite the files if you add language packs, for example. Additionally, by not overwriting Setup files, the network installation point remains online and available to users while you add files.
5. If you deploy multiple Office 2010 products, copy those files from the CD to the installation point. When you are prompted to overwrite duplicate Setup files, click No.
6. If you create a Setup customization file (.msp file) for the installation, store the file in the Updates folder at the root of the installation point.
Or, you can enter the /adminfile option at the command prompt to specify a Setup customization file.
7. If users are installing Office 2010 after product updates are released, store those .msp files in the Updates folder.The amount of space that is required on the network installation point varies by product and by language. The following table shows approximate space requirements for English versions of Office 2010 suites that are typically installed in enterprise organizations. These figures account for both the installed product and the installation files that are stored in the local installation source.
ProductApproximate space requiredMicrosoft Office Professional 2010Approximately 3 gigabytes (GB)Microsoft Office Professional Plus 2010Approximately 3 GB
The installation point contains only one copy of the language-neutral core product. Each language that you add requires additional space only for the language-specific components.
Note:
Unlike in versions of Microsoft Office products earlier than the 2007 Microsoft Office system, in Office 2010 (and in the 2007 Office system) you do not create an administrative installation point by running Setup with the /a command-line option to extract compressed source files. In Office 2010 and in the 2007 Office system, all installations occur from the compressed source.
Replicate the network installation point
In many enterprise organizations, the network installation point is the location from which users first install Office. After Office 2010 is installed, users do not typically have to rely on the network source for tasks such as updating, modifying, or reinstalling Office. Setup automatically creates a local installation source on each user's computer. However, if the local source is corrupted or deleted, Setup returns to the original network source to re-create the local source on the user's computer.
We recommend that you replicate the network source to multiple locations for the following reasons:
A v a i l a b i l i t y I f y o u c r e a t e m u l t i p l e n e t w o r k i n s t a l l a t i o n p o i n t s ( w h i c h c a n b e i n t h e s a m e p h y s i c a l l o c a t i o n ) , y o u h e l p e n s u r e t h a t u s e r s a l w a y s h a v e a c c e s s t o a n e t w o r k s o u r c e . I d e a l l y , t h e d u p l i c a t e n e t w o r k i n s t a l l a t i o n p o i n t s a r e m a n a g e d b y D i s t r i b u t e d F i l e S y s t e m ( D F S ) t e c h n o l o g i e s a n d a r e t r a n s p a r e n t t o u s e r s .
P r o x i m i t y t o u s e r s M a n y c o m p a n i e s h a v e h i g h - s p e e d L A N n e t w o r k s t h a t a r e c o n n e c t e d t o o t h e r s u b s i d i a r i e s o r b r a n c h o f f i c e s b y m u c h s l o w e r W A N c o n n e c t i o n s . I f y o u s e t u p a d u p l i c a t e n e t w o r k i n s t a l l a t i o n p o i n t a t t h e r e m o t e l o c a t i o n s , O f f i c e s o u r c e f i l e s t r a v e l o v e r t h e s l o w n e t w o r k c o n n e c t i o n o n l y o n e t i m e , a n d a f t e r t h a t , u s e r s h a v e a c c e s s t o a c l o s e r n e t w o r k s o u r c e .
C o n s i s t e n c y I f y o u c r e a t e o n e n e t w o r k i n s t a l l a t i o n p o i n t w i t h a l l t h e c u s t o m i z a t i o n s t h a t y o u w a n t a n d t h e n d u p l i c a t e t h a t i n s t a l l a t i o n p o i n t a s n e e d e d , y o u h e l p e n s u r e t h a t t h e s a m e c o n f i g u r a t i o n i s d e p l o y e d t h r o u g h o u t y o u r o r g a n i z a t i o n .
F l e x i b i l i t y I f t h e p r i m a r y n e t w o r k i n s t a l l a t i o n p o i n t i n s t a l l s a s t a n d a r d c o r p o r a t e configuration of Office 2010, regional offices can apply additional customizations to the replicated network installation points and can customize Office 2010 for their unique region-specific requirements.
To specify additional network sources
1. Start the Office Customization Tool (OCT) by running Setup with the /admin command-line option.
2. In the Setup section, click Additional Network Sources, and then click Add. In the Add Network Server Entry dialog box, enter the path of the location where you plan to copy the network installation point, and then click OK.
You can add as many additional source locations as you want.
3. Save the Setup customization file (.msp file) that is generated by the OCT in the Updates folder at the root of the network installation point.
4. Copy the complete folder structure of the network installation point to the locations that you specified in the Setup customization file.
Users who install Office 2010 from any of these network installation points have access to the backup n e t w o r k s o u r c e s . S e t u p c h e c k s t h e s e s o u r c e s a u t o m a t i c a l l y w h e n a n a l t e r n a t i v e s o u r c e i s r e q u i r e d . S e c u r e t h e n e t w o r k i n s t a l l a t i o n p o i n t
T o h e l p m a k e t h e n e t w o r k i n s t a l l a t i o n p o i n t f o r O f f i c e m o r e s e c u r e , f o l l o w t h e s e r e c o m m e n d e d b e s t p r a c t i c e s :
M a k e s u r e t h a t a c c e s s t o s o u r c e f i l e s i s r e a d - o n l y . ( T h e S e t u p . x m l a n d P a c k a g e . x m l f i l e s , s u c h a s P r o P l u s W W . x m l f o r M i c r o s o f t O f f i c e P r o f e s s i o n a l 2 0 1 0 , a r e d i g i t a l l y s i g n e d a n d c a n n o t b e m o d i f i e d . )
S a v e a l l c u s t o m i z a t i o n f i l e s t h a t y o u c r e a t e a s r e a d - o n l y . T h e s e i n c l u d e S e t u p c u s t o m i z a t i o n f i l e s a n d c u s t o m C o n f i g . x m l f i l e s .
I f y o u a r e c e n t r a l i z i n g l o g f i l e s o n t h e n e t w o r k , m a k e s u r e t h a t u s e r s h a v e r e a d / w r i t e p e r m i s s i o n t o t h a t l o c a t i o n .
M a k e s u r e t h a t a l l u s e r s h a v e a d m i n i s t r a t i v e p e r m i s s i o n s b e f o r e t h e u s e rs install Office 2010. You can do this by using your existing software deployment infrastructure.
As with any deployment of Office, test all the customizations and deployment in a non-production environment as part of the deployment pilot tests before you deploy Office 2010 to users in the organization.
See Also
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
Customize the installation for Office 2010
This section provides information about the customization process and links to resources to help you customize a client installation of Microsoft Office 2010.
In this section:
ArticleDescriptionHYPERLINK \l "z72a93ebf389a491a94c8d7da02642139"Customization overview for Office 2010Provides a summary of the customization tools and methods for Office 2010.HYPERLINK \l "z267f8f4c26094d75ba65f45ac680222e"Customize setup for Office 2010Provides information and procedures to help you customize the installation of Office 2010.HYPERLINK \l "zfefaca0beffe43f1b5403c7619dc2d60"Customize specific features in Office 2010Provides information and procedures to help you customize language setup and settings in Office 2010.HYPERLINK \l "z14675abea72c4d01aa41ebd35ffc9165"Configure security for Office 2010Provides information and procedures to configure security settings for Office 2010 by using the Office Customization Tool (OCT) and Group Policy.HYPERLINK \l "z27c8417987fd483ea34d806c4646ce9d"Configure Information Rights Management in Office 2010Provides information and procedures to restrict permission to content documents and e-mail messages in Office 2010 by using Information Rights Management (IRM).HYPERLINK \l "z64b99cc702434cceb4ec1e65b6127281"Configure Outlook 2010Provides information and procedures to configure Microsoft Outlook 2010. This includes how to configure and use Outlook Anywhere, Cached Exchange Mode, and Microsoft Exchange Server send/receive settings.HYPERLINK \l "zefbf78f3cc46426dbf925bdc4d77c093"Configure SharePoint Workspace 2010Provides information and procedures to configure and customize Microsoft SharePoint Workspace 2010. This includes how to test SharePoint Workspace connections.
Customization overview for Office 2010
This article provides a summary of customization tools and methods for Microsoft Office 2010. To customize an installation of Office 2010, administrators can use the following tools: the Office Customization Tool (OCT), the Config.xml file, or the Setup command-line options.
To configure user and computer settings, administrators use either the OCT or Group Policy, depending on their business requirements. Administrators can use the OCT to provide initial default values. However, users can change the settings after Office is installed. To enforce settings, administrators must use Group Policy. For more information, see HYPERLINK \l "z1223"Configure user and compu t e r s e t t i n g s .
I n t h i s a r t i c l e :
H Y P E R L I N K \ l " z 1 2 2 4 " S u m m a r y o f c u s t o m i z a t i o n m e t h o d s
H Y P E R L I N K \ l " z 1 2 2 5 " O f f i c e C u s t o m i z a t i o n T o o l
H Y P E R L I N K \ l " z 1 2 2 6 " C o n f i g . x m l f i l e
H Y P E R L I N K \ l " z 1 2 2 7 " S e t u p c o m m a n d - l i n e o p t i o n s
H Y P E R L I N K \ l " z 1 2 2 3 " C o n f i g u r e u s e r a n d c o m p u t e r s e t t i n g s
H Y P E R L I N K \ l " z 1 2 2 8 " O f f i c e 2 0 1 0 l i c e n s i n g a n d a c t i v a t i o n
H Y P E R L I N K \ l " z 1 2 2 9 " S u m m a r y o f c l i e n t c u s t o m i z a t i o n t a s k s
S u m m a r y o f c u s t o m i z a t i o n m e t h o d s
T h e f o l l o w i n g t a b l e s u m m a r i z e s t h e c u s t o m i z a t i o n m e t h o d s for Office 2010 clients and describes the recommended scenarios for each method.
Tool or methodScenarioResultsUse the Office Customization Tool (OCT) to create a Setup customization (.msp) fileThe OCT is the recommended tool for most customizations. This includes the following:
E n t e r i n g a v o l u m e l i c e n s e k e y a n d a c c e p t i n g t h e M i c r o s o f t S o f t w a r e L i c e n s e T e r m s .
C o n f i g u r i n g t h e d i s p l a y l e v e l o f t h e u s e r i n t e r f a c e .
C u s t o m i z i n g f e a t u r e s a n d u s e r s e t t i n g s .
C u s t o m i z i n g t h e d e f a u l t M i c r o s o f t O u t l o o k 2 0 1 0 p r o f i l e a n d O u t l o o k 2 0 1 0 a nd Microsoft Exchange Server 2010 options.
For more information, see HYPERLINK \l "z1225"Office Customization Tool.Setup installs a default configuration on all computers to which the customization .msp file is applied. Users can modify most of the settings after the installation.Edit the Config.xml fileThe Config.xml file is used to configure most of the same options that you can configure by using the OCT, including some options that are not available in the OCT. The following options can only be co n f i g u r e d i n t h e C o n f i g . x m l f i l e :
S p e c i f y i n g t h e p a t h o f t h e n e t w o r k i n s t a l l a t i o n p o i n t .
S e l e c t i n g w h i c h p r o d u c t t o i n s t a l l .
C o n f i g u r i n g l o g g i n g o p t i o n s .
S p e c i f y i n g t h e l o c a t i o n o f t h e S e t u p c u s t o m i z a t i o n . m s p f i l e a n d s o f t w a r e u p d a t e s .
S p e c i f y i n g l a n g u a g e s t o i n s t a l l o r r e m o v e .
S p e c i f y i n g i n s t a l l a t i o n i n f o r m a t i o n , s u c h a s u s e r n a m e .
C o p y i n g t h e l o c a l i n s t a l l a t i o n s o u r c e t o t h e u s e r ' s c o m p u t e r w i t h o u t i n s t a l l i n g O f f i c e 2 0 1 0 .
F o r m o r e i n f o r m a t i o n , s e e H Y P E R L I N K \ l " z 1 2 2 6 " C o n f i g . x m l f i l e . S e t up installs the specified products and languages on all computers installed by using this Config.xml file. Settings that are specified in the Config.xml file take precedence over duplicate settings in a Setup customization .msp file.Use Setup command-line optionsSetup command-line options are available only for the following customizations:
R u n n i n g t h e O C T t o c r e a t e a S e t u p c u s t o m i z a t i o n . m s p f i l e .
S p e c i f y i n g t h e p a t h o f a s p e c i f i c S e t u p c u s t o m i z a t i o n f i l e o r t o t h e f o l d e r w h e r e y o u s t o r e O f f i c e 2 0 1 0 c u s t o m i z a t i o n f i l e s .
S p e c i f y i n g t h e C o n f i g . x m l f i l e t h a t S e t u p u s e s d u r i n g t h e i n s t a l l a t i o n .
M o d i f y i n g a n e x i s t i n g i n s t a l l a t i o n .
R e p a i r i n g a p r o d u c t .
U n i n s t a l l i n g a p r o d u c t .
F o r m o r e i n f o r m a t i o n , s e e H Y P E R L I N K \ l " z 1 2 2 7 " S e t u p c o m m a n d - l i n e o p t i o n s . S e t u p a p p l i e s t h e c u s t o m i z a t i o n s w h e n i t f i r s t i n s t a l l s O f f i c e 2 0 1 0 o r w h e n i t r u n s i n maintenance mode.
You cannot set Windows Installer properties on the command line.Use the Group Policy Object Editor Microsoft Management Console (MMC) snap-in to specify policy settingsUsed to configure highly restricted or lightly managed configurations that you want to enforce for user and computer settings.
For more information, see HYPERLINK \l "z1230"Configuring user and computer settings by using Group Policy.Administrators use Group Policy to define configurations one time, and then they rely on the operating system to enforce that state.
Group Policy for computers is applied at computer startup and Group Policy for users is applied when users log on. Group Policy is also applied subsequently in the background periodically.
Office Customization Tool
The Office Customization Tool (OCT) is part of the Setup program and is the primary tool for most customizations. The OCT saves customizations in a Setup customization (.msp) file, which is applied at either Setup time or during a maintenance mode operation. After you create a network installation point and before you install Office 2010, use the OCT to customize the installation. To start the OCT, click Start, click Run, browse to the root of the network installation point that contains the Office 2010 source files, and type the following at the command prompt: setup.exe /admin. For example: \\server\share\Office14ProPlus\setup.exe /admin.
In Office 2010, two architecture-specific versions of the OCT are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Administrators use the OCT to customize the following areas:
S e t u p U s e d t o s p e c i f y d e f a u l t i n s t a l l a t i o n l o c a t i o n a n d d e f a u l t o r g a n i z a t i o n n a m e , a d d i t i o n a l n e t w o r k i n s t a l l a t i o n s o u r c e s , t h e p r o d u c t k e y , e n d - u s e r l i c e n s e a g r e e m e n t , d i s p l a y l e v e l , e a r l i e r v e r s i o n s o f O f f i c e t o r e m o v e , c u s t o m p r o g r a m s t o r u n d u r i n g i n s t a l l a t i o n , s e c u r i t y s e t t i n g s , a n d S e t u p p r o p e r t i e s .
F e a t u r e s U s e d t o c o n f i g u r e u s e r s e t t i n g s a n d t o c u s t o m i z e h o w O f f i c e f e a t u r e s a r e i n s t a l l e d .
A d d i t i o n a l c o n t e n t U s e d t o a d d o r r e m o v e f i l e s , a d d o r r e m o v e r e g i s t r y e n t r i e s , a n d c o n f i g u r e s h o r t c u t s .
O u t l o o k U s e d t o c u s t o m i z e a u s e r ' s d e f a u l t O u t l o o k p r o f i l e , s p e c i f y E x c h a n g e s e t t i n g s , a d d a c c o u n t s , r e m o v e a c c o u n t s a n d e x p o r t s e t t i n g s , a n d s p e c i f y S e n d \ R e c e i v e g r o u p s .
F o r m o r e i n f o r m a t i o n a b o u t h o w t o u s e t h e O C T , s e e t h e f o l l o w i n g r e s o u r c e s :
H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 8 f a a e 8 a 0 - a 1 2 c - 4 f 7 b - 8 3 9 c - 2 4 a 6 6 a 5 3 1 b b 5 ( O f f i c e . 1 4 ) . a s p x " O f f i c e C u s t o m i z a t i o n T o o l i n O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 8 f a a e 8 a 0 - a 1 2 c - 4 f 7 b - 8 3 9 c - 2 4 a 6 6 a 5 3 1 b b 5 ( O f f i c e . 1 4 ) . a s p x )
H Y P E R L I N K \ l " z a 3 3 e 6 4 b 0 4 6 a 5 4 5 e 5 b 7 6 f 3 a d d 5 9 5 a f 8 d e " C u s t o m i z e O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 9 c 1 4 d b 6 0 b 5 9 1 4 1 f 9 a 9 4 b 5 0 6 2 7 d 2 d a a 8 1 " C u s t o m i z e S e t u p b e f o r e i n s t a l l i n g O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 2 9 c d d e 9 7 d 1 a 7 4 6 8 3 9 c 3 4 b d 0 b d 7 8 c 4 1 c c " C o n f i g u r e u s e r s e t t i n g s f o r O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 5 e 3 7 7 a f e 3 c 0 9 4 4 7 d 8 2 b 9 0 6 4 0 0 f b f 1 1 3 8 " C o n f i g u r e f e a t u r e i n s t a l l a t i o n s t a t e s f o r O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 6 4 b 9 9 c c 7 0 2 4 3 4 c c e b 4 e c 1 e 6 5 b 6 1 2 7 2 8 1 " C o n f i g u r e O u t l o o k 2 0 1 0
H Y P E R L I N K \ l " z 6 b d 8 8 3 4 2 4 f 3 a 4 5 3 5 a 5 7 0 4 7 5 d 2 5 1 e f 9 d a " I m p o r t a n O f f i c e 2 0 1 0 S e t u p customization file
Administrators can also configure some installation options by using the Config.xml file.
Config.xml file
The Config.xml file is used to specify installation options, and it runs only during setup. You can use the Config.xml file to configure most of the same options that you can configure with the OCT, including a few additional options that are not available in the OCT. The Config.xml is not installed or cached on users computers. The Config.xml file that is stored in the core product folders (core_product_folder_name.WW folder such as ProPlus.WW for Microsoft Office Professional Plus 2010) directs Setup to install that product. If the network installation point contains multiple Office 2010 products, you can use the /config command-line option when you run Setup.exe to specify the path of the Office 2010 product that you want to install; if you do this, it will prevent Setup from prompting you about which product to install. For more information about Setup commands, see HYPERLINK "http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx"Setup command-line options for Office 2010 (http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx).
If you use both an OCT Setup customization (.msp) file and the Config.xml to customize the installation, the settings that you specify in Config.xml take precedence over those in the Setup customization file. The HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx) article provides detailed information about the installation options and indicates if a setting has a corresponding OCT setting.
You can also use the Config.xml file for maintenance operations such as adding or removing features, and repairs and uninstalls. To do this, you must run Setup again from the original source.
The following customizations can on l y b e m a d e b y u s i n g t h e C o n f i g . x m l f i l e :
S p e c i f y i n g t h e p a t h o f t h e n e t w o r k i n s t a l l a t i o n p o i n t .
S e l e c t i n g t h e p r o d u c t s t o i n s t a l l .
C u s t o m i z i n g S e t u p o p t i o n s , i n c l u d i n g l o g g i n g , a n d t h e l o c a t i o n o f t h e S e t u p c u s t o m i z a t i o n f i l e a n d s o f t w a r e u p d a t e s .
S p e c i f y i n g i n s t a l l a t i o n o p t i o n s , s u c h a s u s e r n a m e .
C o p y i n g t h e l o c a l i n s t a l l a t i o n s o u r c e ( L I S ) t o t h e u s e r ' s c o m p u t e r w i t h o u t i n s t a l l i n g O f f i c e .
A d d i n g o r r e m o v i n g l a n g u a g e s f r o m t h e i n s t a l l a t i o n .
S e t u p c o m m a n d - l i n e o p t i o n s
A d m i n i s t r a t o r s c a n a l s o u s e S e t u p . e x e c o m m a n d - l i n e o p t i o n s t o p e r f o r m t h e f o l l o w i n g t a s k s :
R u n t h e O C T t o c r e a t e a S e t u p c u s t o m i z a t i o n ( . m s p ) f i l e .
S p e c i f y a p a t h o f a s p e c i f i c S e t u p c u s t o m i z a t i o n f i l e o r t o t h e f o l d e r w h e r e y o u s t o r e O f f i c e 2 0 1 0 c u s t o m i z a t i o n f i l e s .
S p e c i f y t h e C o n f i g . x m l f i l e t h a t S e t u p u s e s d u r i n g t h e i n s t a l l a t i o n .
R u n S e t u p i n m a i n t e n a n c e m o d e a n d m a k e c h a n g e s t o a n e x i s t i n g O f f i c e i n s t a l l a t i o n .
R u n S e t u p t o r e p a i r t h e s p e c i f i e d p r o d u c t f r o m t h e u s e r ' s c o m p u t e r .
R u n S e t u p t o r e m o v e t h e s p e c i f i e d p r o d u ct from the user's computer.
The following table lists the commands that Setup supports.
CommandDescription/adminRuns the OCT to create or modify a Setup customization file (.msp file)./adminfile [path]Applies the specified Setup customization file to the installation and can be used only for initial installations. You can specify a path of a specific customization file (.msp file) or to the folder where you store customization files./config [path]Specifies the Config.xml file that Setup uses during the installation. By default, the Config.xml file that is stored in the core product folder directs Setup to install that product. For example, the Config.xml file in the ProPlus.WW folder installs Office Professional Plus 2010./modify [ProductID]Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation. For example, you can use the /modify option to add or remove features. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify. /repair [ProductID]Runs Setup to repair the specified product from the users computer. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify./uninstall [ProductID]Runs Setup to remove the specified product from the users computer. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify.
For more detailed information about Setup commands, see HYPERLINK "http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx"Setup command-line options for Office 2010 (http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx).
Configure user and computer settings
As mentioned previously, depending on whether administrators must enforce user settings or whether they want to allow users to modify the settings after the installation, administrators use either Group Policy or the OCT. The majority of the Group Policy and OCT settings for Office a r e u s e r s e t t i n g s . M o s t o f t h e O f f i c e p o l i c y s e t t i n g s h a v e a c o r r e s p o n d i n g O C T s e t t i n g .
G r o u p P o l i c y a n d t h e O C T c a n b e u s e d t o c o n f i g u r e u s e r a n d c o m p u t e r s e t t i n g s f o r t h e f o l l o w i n g O f f i c e a p p l i c a t i o n s :
M i c r o s o f t A c c e s s 2 0 1 0
M i c r o s o f t E x c e l 2 0 1 0
M i c r o s o f t I n f o P a t h 2 0 1 0
M i c r o s o f t O f f i c e 2 0 1 0 S y s t e m
M i c r o s o f t O n e N o t e 2 0 1 0
M i c r o s o f t O u t l o o k 2 0 1 0
M i c r o s o f t P o w e r P o i n t 2 0 1 0
M i c r o s o f t P r o j e c t 2 0 1 0
M i c r o s o f t P u b l i s h e r 2 0 1 0
M i c r o s o f t S h a r e P o i n t D e s i g n e r 2 0 1 0
M i c r o s o f t S h a r e P o i n t W o r k s p a c e 2 0 1 0
M i c r o s o f t V i s i o 2 0 1 0
M i c r o s o f t W o r d 2 0 1 0
C o n f i g u r i n g u s e r a n d c o m p u t e r s e t t i n g s b y u s i n g G r o u p P o l i c y
G r o u p P o l i c y i s a n i n f r a s t r u c t u r e t h a t a d m i n i s t r a t o r s c a n u s e t o i m p l e m e n t s p e c i f i c c o m p u t i n g c o n f i g u r a t i o n s f o r u s e r s a n d c o m p u t e r s . P o l i c y s e t t i ngs can also be applied to member servers and domain controllers within the scope of an Active Directory forest. Administrators use Group Policy to define configurations once and then rely on the operating system to enforce that state.
Group Policy settings are contained in Group Policy objects (GPOs), which are linked to selected Active Directory Domain Services (ADDS) containers sites, domains, or organizational units (OUs). The settings within GPOs are evaluated by the affected targets using the ADDS hierarchical container structure.
The Group Policy infrastructure consists of a Group Policy engine and several individual extensions. These extensions are used to configure Group Policy settings, either by modifying the registry through the Administrative Templates extension, or by configuring Group Policy settings for security settings, software installation, folder redirection, Internet Explorer Maintenance, wireless network settings, and other areas. The Office policy settings are contained in Administrative Template (.adm or .admx and .adml) files.
To mandate Office settings configurations for users and computers, the administrator uses Group Policy, and the operating system enforces those policy settings. For example, use Group Policy to mandate security settings to help counter attacks that target e-mail and desktop documents. In an Active Directory-based environment, administrators apply policy settings to groups of users and computers in a site, domain, or OU to which a GPO is linked. True policy settings are written to the approved registry key locations for policy, and these settings have access control list (ACL) restrictions that prevent non-administrator users from changing them. Administrators use Group Policy to create highly restricted or lightly managed desktop configurations, depending on their specific business and security requirements. Group Policy settings have precedence over OCT settings.
The following table lists the approved registry key locations for Group Policy settings. Users cannot change or disable these settings.
For computer policy settingsFor user policy settingsHKLM\Software\Policies (the preferred location)HKCU\Software\Policies (the preferred location)HKLM\Software\Microsoft\Windows\CurrentVersion\PoliciesHKCU\Software\Microsoft\Windows\CurrentVersion\Policies
For Office 2010, user-specific policy settings are stored in the HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0 subkey. Computer-specific policies are stored in the HKEY_LOCAL_MACHINE\Software\Poli c i e s \ M i c r o s o f t \ O f f i c e \ 1 4 . 0 s u b k e y . B y d e f a u l t , b o t h p o l i c y s u b k e y s a r e l o c k e d t o p r e v e n t u s e r s f r o m m o d i f y i n g t h e m .
G r o u p P o l i c y s e t t i n g s c a n b e s e t t o o n e o f t h r e e s t a t e s :
N o t c o n f i g u r e d T h e p o l i c y s e t t i n g i s n o t e n f o r c e d .
E n a b l e d T h e p o l i c y s e t t i n g i s a c t i v a t e d . A d d i t i o n a l s e t t i n g s a p p e a r i n t h e P r o p e r t i e s p a g e f o r s o m e p o l i c y s e t t i n g s . T h e s e s e t t i n g s d e t e r m i n e w h a t h a p p e n s w h e n t h e p o l i c y s e t t i n g i s e n f o r c e d .
D i s a b l e d F o r m o s t p o l i c y s e t t i n g s , t h e D i s a b l e d s t a t e e n f o r c e s t h e o p p o s i t e b e h a v i o r to that of the Enabled state. For example, if Enabled forces a feature's state to Off, Disabled forces the feature's state to On.
For more information about using Group Policy, see HYPERLINK \l "z873a53921b1a47a1a8631f29ef116d0e"Enforce settings by using Group Policy in Office 2010.
Configuring user and computer settings by using the Office Customization Tool
To specify initial default values of Office application settings for users and computers, administrators use the OCT to specify settings in a Setup customization .msp file. Users can modify most of the settings after the installation. This is because the OCT configures settings in publicly available portions of the registry, such as HKEY_CURRENT_USER\Software\Microsoft\Office\14.0 for user settings and HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0 for computer settings.
OCT settings can be set to one of the following states:
N o t C o n f i g u r e d T h e s e t t i n g r e m a i n s a s i t i s .
E n a b l e d T h e s e t t i n g i s m o d i f i e d b a s e d o n y o u r c h o i c e s i n t h e P r o p e r t i e s p a g e f o r t h e s e t t i n g .
D i s a b l e d T h e s e t t i n g i s d i s a b l e d . D i s a b l i n g a n o p t i o n m i g h t b e d i f f e r e n t f r o m n o t c o n f i g u r i n g t h e o p t i o n . See the description of the specific option for more information.
Office 2010 licensing and activation
Microsoft policy requires the activation of all editions of Office 2010 client software, including those obtained through a Volume Licensing program. This requirement applies to Office 2010 running on both physical computers and virtual computers. Activation is not required for any Office 2010 server products: Microsoft SharePoint Server 2010 and Microsoft Project Server 2010, or any version of Microsoft Exchange Server. In Office 2010, the activation method uses Office Activation Technologies, based on the Software Protection Platform introduced in Windows Vista and Windows Server 2008 families.
You can use the following methods to activate Office 2010 by using Office Activation Technologies, which are the same methods that are used for WindowsVista and later versions of Windows:
K e y M a n a g e m e n t S e r v i c e ( K M S ) . K M S u s e s a K M S h o s t k e y t o a c t i v a t e a K M S h o s t c o m p u t e r a n d e s t a b l i s h a l o c a l a c t i v a t i o n s e r v i c e i n y o u r e n v i r o n m e n t . O f f i c e 2 0 1 0 c o n n e c t s t o t h e l o c a l K M S h o s t f o r a c t i v a t i o n . O f f i c e 2 0 1 0 e n t e r p r i s e d e p l o y m e n t s t h a t a r e u s i ng Key Management Service (KMS) activation do not require a product key entry because all Volume License editions of Office 2010 have a KMS client key pre-installed. However, administrators must configure a KMS host computer with a KMS host key to be activated and to establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. KMS is the default option for Volume Licensed clients.
M u l t i p l e A c t i v a t i o n K e y ( M A K ) . W i t h a M A K , c l i e n t s a c t i v a t e O f f i c e 2 0 1 0 o n l i n e w i t h t h e M i c r o s o f t h o s t e d a c t i v a t i o n s e r v e r s o r b y t e l e p h o n e . M A K i s a p p r o p r i a t e f o r o r g a n i z a t i o n s w i t h c o m p u t e r s t h a t a r e n o t c o n n e c t e d t o t h e c o r p o r a t e n e t w o r k f o r l o n g p e r i ods of time, such as portable computers. If you use the MAK method, Office 2010 must be installed with a MAK key instead of the default KMS client key used in Volume License editions of Office 2010. MAK activation by telephone will be supported later when the product releases (RTM).
A c o m b i n a t i o n o f K M S a n d M A K .
F o r d e t a i l e d i n f o r m a t i o n a b o u t l i c e n s i n g a n d a c t i v a t i o n o f O f f i c e 2 0 1 0 c l i e n t s , w e r e c o m m e n d t h a t y o u r e a d t h e f o l l o w i n g a r t i c l e s b e f o r e y o u c u s t o m i z e t h e i n s t a l l a t i o n : H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 0 7 3 5 c 1 f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx), HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx), HYPERLINK \l "zdbff777c3a2d4d8ea7be6c45900c73c2"Volume activation quick start guide for Office 2010, HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010, HYPERLINK \l "z1825df767e23459ba6c1224dd6eab81e"Tools to configure client computers in Office 2010.
Summary of client customization tasks
The following illustration summarizes the tasks to perform to customize an Office 2010 client installation. As with any software deployment, your Office 2010 client deployment plans must include testing in a non-production environment and conducting pilot tests with s m a l l g r o u p s o f u s e r s b e f o r e y o u d e p l o y t o a l l u s e r s i n t h e o r g a n i z a t i o n .
T h e f o l l o w i n g r e s o u r c e s p r o v i d e i n f o r m a t i o n a b o u t p l a n n i n g a n d a b o u t c u s t o m i z a t i o n t a s k s f o r O f f i c e 2 0 1 0 c l i e n t i n s t a l l a t i o n s :
H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / b 4 1 f 7 b c 2 - b 7 f a - 4 3 a 3 - 9 6 3 a - c f 1 c 1 e f 8 f 3 3 1 ( O f f i c e . 1 4 ) . a s p x " P l a n f o r v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / b 4 1 f 7 b c 2 - b 7 f a - 4 3 a 3 - 9 6 3 a - c f 1 c 1 e f 8 f 3 3 1 ( O f f i c e . 1 4 ) . a s p x )
H Y P E R L I N K \ l " z 0 3 2 7 f 6 9 a b 9 0 8 4 a 7 2 b b c 2 9 b e 1 3 e 3 5 9 1 1 5 " C o n f i g u r e a n d d e p l o y v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 4 6 d 2 6 f 2 e 4 e b a 4 d 4 1 9 d 6 6 a 7 f 3 f d 3 8 3 5 0 1 " P r e p a r e t h e i n f r a s t r u c t u r e f o r O f f i c e 2 0 1 0
H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / f 4 5 8 a 0 c b - a 3 a 5 - 4 d 4 a - 9 f 9 8 - a 4 a 8 1 a 1 7 e e 3 a ( O f f i c e . 1 4 ) . a s p x " P l a n f o r m u l t i l a n g u a g e d e p l o y m e n t o f O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / f 4 5 8 a 0 c b - a 3 a 5 - 4 d 4 a - 9 f 9 8 - a 4 a 8 1 a 1 7 e e 3 a ( O f f i c e . 1 4 ) . a s p x )
H Y P E R L I N K \ l " z 2 6 7 f 8 f 4 c 2 6 0 9 4 d 7 5 b a 6 5 f 4 5 a c 6 8 0 2 2 2 e " C u s t o m i z e s e t u p f o r O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 1 c 4 2 3 9 7 5 1 8 4 8 4 0 6 0 9 9 9 c c a f c a d f 3 0 4 7 d " C u s t o m i z e l a n g u a g e s e t u p a n d s e t t i n g s f o r O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 6 4 b 9 9 c c 7 0 2 4 3 4 c c e b 4 e c 1 e 6 5 b 6 1 2 7 2 8 1 " C o n f i g u r e O u t l o o k 2 0 1 0
H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / e 6 8 b d 7 d 9 - a f a 2 - 4 5 a b - 8 7 8 8 - f c 7 c 6 8 e 6 e f b 5 ( O f f i c e . 1 4 ) . a s p x " C h o o s e a n o p t ion for deploying Office 2010 (http://technet.microsoft.com/library/e68bd7d9-afa2-45ab-8788-fc7c68e6efb5(Office.14).aspx)
See Also
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx"Setup command-line options for Office 2010 (http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx)
HYPERLINK \l "z873a53921b1a47a1a8631f29ef116d0e"Enforce settings by using Group Policy in Office 2010
HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010
Customize setup for Office 2010
This section provides information to help you customize an installation Microsoft Office 2010.
In this section:
ArticleDescriptionHYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010Provides information and procedures to customize an installation of Office 2010.HYPERLINK \l "z9c14db60b59141f9a94b50627d2daa81"Customize Setup before installing Office 2010Provides information and procedures to customize Setup before installing Office 2010.HYPERLINK \l "z5e377afe3c09447d82b906400fbf1138"Configure feature installation states for Office 2010Provides information and procedures to customize Setup to configure feature installation states.HYPERLINK \l "z29cdde97d1a746839c34bd0bd78c41cc"Configure user settings for Office 2010Provides information and procedures to configure Office 2010 user settings by using the Office Customization Tool (OCT).HYPERLINK \l "z0797376771cb4c32910bcfbd2268fc52"Create different configurations of Office 2010 for different groups of usersProvides information and procedures to create unique configurations of Office 2010 for each group.HYPERLINK \l "z6bd883424f3a4535a570475d251ef9da"Import an Office 2010 Setup customization fileProvides information and procedures to import an OCT Setup customization file (.msp file) in Office 2010.HYPERLINK \l "ze5f2412428864a86b475f232d0e04199"Configure a silent installation of Office 2010 by using Config.xmlProvides information and procedures for configuring a silent installation by using the Config.xml file.HYPERLINK \l "ze65362450f424904b2e09168fd6b81d4"Run arbitrary commands with installations of Office 2010Provides information and procedures to customize Setup to run an arbitrary command or a lightweight executable to install an Office 2010 product.HYPERLINK \l "z11c3ecc98e4d4a8f898bd0cbfd808b82"Create custom configurations of Office 2010Describes how to deploy an initial customized installation of Office 2010 to users in an organization.HYPERLINK \l "z4e9de57759534aaf8af0a7e910716a66"View XML content from Office Customization Tool customization filesProvides a sample Microsoft Visual Basic script that administrators can use to view the settings that are stored in Setup customization .msp files.
Customize Office 2010
This article provides information and procedures to customize an installation of Microsoft Office 2010. After you create a network installation point, but before you install Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file to configure the installation for users. You can use the OCT to alter the way that Setup performs the installation and to configure Office applications on the user's computer.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Note:
Office 2010 does not support side-by-side installations of 64-bit and 32-bit Office, including across applications. For example, there is no support for side-by-side installations of the 2007 Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit. You cannot use the Office 2010 customization tools to configure side-by-side installations or customizations of 64-bit and 32-bit Office. For example, you cannot create a custom side-by-side installation with 64-bit Microsoft Office Professional 2010 and 32-bit Microsoft Visio 2010 single image. For more information about 64-bit Office, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Customize Office
To customize Office by using the OCT
1. From the root of the network installation point, run the following command line to start the Office Customization Tool: \\server\share\setup.exe /admin.
2. In the Select Product dialog box, select a single product that you want to customize, and then click OK.
3. In the left pane, select an area of customization and customize the options available in the right pane. For example, to configure Setup to run quietly, select Licensing and user interface in the left pane, and then select None for Display level in the right pane.
4. When you finish making your customizations, select Save As in the File menu.
5. Specify a unique name for the file and save the file in the Updates folder of the network installation point.
6. Click Save.When you run Setup.exe from the network installation point, Setup looks in the Updates folder for Setup customization files for the product that you are installing. Setup then applies your customizations to the installation.
The following articles provide more information about how to customize specific aspects of the installation:
T o c u s t o m i z e t h e d e f a u l t b e h a v i o r o f S e t u p d u r i n g i n s t a l l a t i o n , s e e H Y P E R L I N K \ l " z 9 c 1 4 d b 6 0 b 5 9 1 4 1 f 9 a 9 4 b 5 0 6 2 7 d 2 d a a 8 1 " C u s t o m i z e S e t u p b e f o r e i n s t a l l i n g O f f i c e 2 0 1 0 .
T o c u s t o m i z e w h i c h O f f i c e f e a t u r e s a r e i n s t a l l e d o n t h e u s e r ' s c o m p u t e r , s e e H Y P E R L I N K \ l " z 5 e 3 7 7 a f e 3 c 0 9 4 4 7 d 8 2 b 9 0 6 4 0 0 f b f 1 1 3 8 " C o n f i g u r e f e a t u r e i n s t a l l a t i o n s t a t e s f o r O f f i c e 2 0 1 0 .
T o c u s t o m i z e t h e u s e r ' s d e f a u l t e n v i r o n m e n t d u r i n g i n s t a l l a t i o n , s e e H Y P E R L I N K \ l " z 2 9 c d d e 9 7 d 1 a 7 4 6 8 3 9 c 3 4 b d 0 b d 7 8 c 4 1 c c " C o n f i g u r e u s e r s e t t i n g s f o r O f f i c e 2 0 1 0 .
T o c o n f i g u r e O u t l o o k o p t i o n s , s e e t h e H Y P E R L I N K \ l " z 6 4 b 9 9 c c 7 0 2 4 3 4 c c e b 4 e c 1 e 6 5 b 6 1 2 7 2 8 1 " C o n f i g u r e O u t l o o k 2 0 1 0 a r t i c l e s .
F o r c o m p l e t e i n f o r m a t i o n a b o u t t h e O C T , s e e H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 8 f a a e 8 a 0 - a 1 2 c - 4 f 7 b - 8 3 9 c - 2 4 a 6 6 a 5 3 1 b b 5 ( O f f i c e . 1 4 ) . a s p x " O f f i c e C u s t o m i z a t i o n T o o l i n O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 8 f a a e 8 a 0 - a 1 2 c - 4 f 7 b - 8 3 9 c - 2 4 a 6 6 a 5 3 1 b b 5 ( O f f i c e . 1 4 ) . a s p x ) .
T h e f o l l o w i n g c u s t o m i z a t i o n s c a n o n l y b e m a d e u s i n g t h e C o n f i g . x m l f i l e :
S p e c i f y i n g t h e p a t h o f t h e n e t w o r k i n s t a l l a t i o n p o i n t .
S e l e c t i n g w h i c h p r o d u c t t o i n s t a l l .
C u s t o m i z i n g S e t u p o p t i o n s s u c h a s l o g g i n g a n d t h e l o c a t i o n o f t h e S e t u p c u s t o m i z a t i o n f i l e a n d s o f t w a r e u p d a t e s .
S e t t i n g i n s t a l l a t i o n o p t i o n s s u c h a s u s e r a n d c o m p a n y n a m e .
C o p y i n g t h e l o c a l i n s t a l l a t i o n s o u r c e ( L I S ) t o t h e u s e r ' s c o m p u t e r w i t h o u t i n s t a l l i n g O f f i c e .
A d d i n g o r r e m o v i n g l a n g u a g e s f r o m t h e i n s t a l l a t i o n .
F o r m o r e i n f o r m a t i o n a b o u t h o w t o u s e t h e C o n f i g . x m l f i l e , s e e H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / e 1 6 a f 7 1 c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
See Also
HYPERLINK "http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx"Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
HYPERLINK \l "zdbff777c3a2d4d8ea7be6c45900c73c2"Volume activation quick start guide for Office 2010
HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010
HYPERLINK \l "z72a93ebf389a491a94c8d7da02642139"Customization overview for Office 2010
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx)
HYPERLINK \l "z6bd883424f3a4535a570475d251ef9da"Import an Office 2010 Setup customization file
Customize Setup before installing Office 2010
This article provides required information and procedures to customize Setup before installing Microsoft Office 2010. In Office 2010 (as in the 2007 Microsoft Office system), Setup controls the complete installation. This includes processes that Windows Installer handled in Office versions earlier than the 2007 Office system. Customizing the default behavior of Setup lets you control the process for example, to run the installation without user interaction, to handle the product key and the Microsoft Software License Terms on behalf of users, and to specify an organization name or a different installation location.
We recommend that you read the HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx), HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.micros o f t . c o m / l i b r a r y / c 6 5 4 5 5 7 9 - 4 c c a - 4 a d 1 - 8 2 9 d - c f e c b b 9 1 7 d c 4 ( O f f i c e . 1 4 ) . a s p x ) , a n d H Y P E R L I N K \ l " z 0 3 2 7 f 6 9 a b 9 0 8 4 a 7 2 b b c 2 9 b e 1 3 e 3 5 9 1 1 5 " C o n f i g u r e a n d d e p l o y v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0 a r t i c l e s b e f o r e c u s t o m i z i n g S e t u p .
I n t h i s a r t i c l e :
H Y P E R L I N K \ l " z 1 5 3 1 " C u s t o m i z e S e t u p
H Y P E R L I N K \ l " z 1 5 3 2 " I n s t a l l O f f i c e s i l e n t l y
C u s t o m i z e S e t u p
T o c u s t o m i z e h o w S e t u p m a n a g e s t h e i n s t a l l a t i o n p r o c e s s , u s e t h e O f f i c e C u s t o m i z a t i o n T o o l ( O C T ) t o c r e a t e a S e t u p c u s t o m i z a t i o n ( . m s p ) f i l e . S e t u p a p p l i e s t h i s f i l e w h e n u s ers install Office on their computers.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
To customize Office Setup
1. Create a network installation point by copying all the files and folders from the Office CD to a folder on the network. For more information, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.
2. From the root of the network installation point, run the following command line to start the Office Customization Tool:
setup.exe /admin
3. Select the product that you want to configure, and then click OK.
4. In the left pane, click Installation location and organization name.
5. In the Default installation path box, enter the path of a default installation location on users' computers. You can enter a relative path that includes the folder keyword [ProgramFilesFolder].
6. In the Organization name box, enter a default organization name for all users who install Office with this customization file.
7. In the left pane, click Additional network sources, and then click Add.
8. In the Network server box, enter the path of any backup sources that you have created on the network. If neither the user's local installation source nor the original network installation point is available, Setup uses one of these replicated installation points for operations that require the source. You can add as many sources as you need.
9. In the left pane, click Licensing and user interface. The following options are available:
U s e K M S c l i e n t k e y A p r o d u c t k e y e n t r y i s n o t r e q u i r e d f o r e n t e r p r i s e d e p l o y m e n t s t h a t a r e u s i n g K e y M a n a g e m e n t S e r v i c e ( K M S ) a c t i v a t i o n b e c a u s e a l l V o l u m e L i c e n s e e d i t i o n s o f O f f i c e 2 0 1 0 h a v e a K M S c l i e n t k e y p r e - i n s t a l l e d . K M S i s o n e o f t h e m e t h o d s t hat are provided by Office Activation Technologies for activating products licensed under Microsoft Volume Licensing programs. Only a KMS host computer needs a KMS host key to be activated and to establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. By default, the Use KMS client key option is selected.
For more information about the licensing options for Office 2010, see HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx). For information about how to configure the KMS host, see HYPERLINK \l "z62"Prepare and configure the KMS host in HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
E n t e r a n o t h e r p r o d u c t k e y Y o u c a n e n t e r a v a l i d M u l t i p l e A c t i v a t i o n K e y ( M A K ) k e y i n t h e O C T b y u s i n g t h e E n t e r a n o t h e r p r o d u c t k e y e n t r y . A M A K k e y i s a n o t h e r m e t h o d t h a t O f f i c e A c t i v a t i o n T e c h n o l o g i e s p r o v i d e f o r a c t i v a t i n g p r o d u c t s l i c e n s e d u n d e r M i crosoft Volume Licensing programs. With a MAK, clients activate Office 2010 online by using the Microsoft hosted activation servers or by telephone.
To use a MAK key, in the Enter another product key text box, enter the MAK key (twenty-five numbers or characters) without spaces. For more information about using a MAK key, see HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
10. Select the I accept the terms in the License Agreement check box. When you provide this information in a Setup customization file, users are not prompted for a product key or Microsoft Software License Terms during the installation or the first time that they start an Office application.
11. In the right pane, set the Display Level to Basic or None to install Office quietly (without user interaction). More information about display settings is provided later in this article.
Note
In enterprise deployments, we recommend that you set Display level to None to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used. Setting Display Level to none assumes that the Suppress modal and Completion notice options are silenced and that the Microsoft Software License Terms is accepted. Administrators must also make sure that no Office applications are running during an installation of Office 2010.
If you set Display level to Basic and select the Suppress modal option, users may be prompted if any Office files are being used. Setting Display level to None prevents prompting users in these cases. The Suppress modal option does not prevent files-in-use messages from displaying; only Display level set to None prevents their display.
12. Make any additional customizations. Click Save on the File menu, and then click save the Setup customization file in the Updates folder at the root of the network installation point.Your customizations apply to any language version of the specified product that is available on the network installation point. Most customizations apply to the language-neutral core product. However, the feature tree in the tool also includes a subset of language-specific features. Customizations to language-specific features are applied when a user installs that language; otherwise, they are ignored.
Note:
Typically, you do not need to customize logging options. By default, Setup creates a standard log file and saves it as a text file in the %Temp% folder on the user's computer. If an installation fails, Setup creates a verbose log file, starting with the package that caused the failure, in the same location. To change logging options, open the Config.xml file in Notepad and modify the element. For more information, see HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
Install Office silently
When you deploy Office throughout an organization, you determine how much of the Setup user interface is displayed to users. By default, Setup runs interactively and gives users choices during the installation. If you are distributing a customized configuration, we recommend that you limit how much users interact with Setup. The installation continues with fewer interruptions, and your customizations are set by default for all users. For more information about display options, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Licensing_and_user_interface"Licensing and user interface (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Licensing_and_user_interface) in HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
If you are using a deployment tool such as Microsoft System Center Configuration Manager 2010 or Microsoft Systems Management Server (SMS) to deploy Office while users are not logged on to the network, set the display level to None, which installs Office without displaying any Setup user interface.
Note:
When you install Office silently, you must provide a valid product key. If the product key is missing, Setup logs an error and exits. As mentioned previously, if you are using KMS activation, a product key entry is not required because all Volume License editions of Office 2010 have a KMS client key pre-installed; however, if you are using MAK, you must enter the MAK key. If you do not accept the license terms on behalf of users, Setup does complete the installation. However, by installing Office silently, you have implicitly accepted the license terms.
The Windows Installer properties DISPLAY and PIDKEY do not work in Office 2010 (or in the 2007 Office system). Instead, in Office 2010 you customize Setup directly by specifying a display setting and specifying a product key in the OCT either by accepting the default option, Use KMS client key if you are using KMS validation, or by entering a MAK key in the Enter another product key textbox if you are using KMS, as described in HYPERLINK \l "z1531"Customize Setup.
Because Setup plays a more significant role in controlling the installation, many Windows Installer properties are no longer required. In fact, some Windows Installer properties are blocked and generate an error if you try to set them using the Office Customization Tool. For a complete list of the Setup properties that you can use with the Office 2010, and also a list of blocked or unsupported properties and their corresponding new mechanisms, see HYPERLINK "http://technet.microsoft.com/library/41f07f9b-f0d0-489d-a185-d7b96f21f561(Office.14).aspx"Setup properties in Office 2010 (http://technet.microsoft.com/library/41f07f9b-f0d0-489d-a185-d7b96f21f561(Office.14).aspx).
See Also
HYPERLINK "http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx"Volume activation overview for Office 2010 (http://technet.microsoft.com/library/0735c1f5-f874-41f1-b9a9-dbea158524b2(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx"Plan volume activation of Office 2010 (http://technet.microsoft.com/library/c6545579-4cca-4ad1-829d-cfecbb917dc4(Office.14).aspx)
HYPERLINK \l "z0327f69ab9084a72bbc29be13e359115"Configure and deploy volume activation of Office 2010
HYPERLINK \l "z1825df767e23459ba6c1224dd6eab81e"Tools to configure client computers in Office 2010
HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010
HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/41f07f9b-f0d0-489d-a185-d7b96f21f561(Office.14).aspx"Setup properties in Office 2010 (http://technet.microsoft.com/library/41f07f9b-f0d0-489d-a185-d7b96f21f561(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx"Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx)
Configure feature installation states for Office 2010
After you create a network installation point but before you install Microsoft Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file (.msp file) to configure the installation for users. You can use the OCT to change the default way that Office features are installed. You can set some features to be installed on the user's computer, some features to be installed only on first use, and some features not to be installed. You can even hide or lock features so that a user who runs Setup interactively cannot change what you have configured. For information about the network installation point, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Configure installation states
Use the following procedure to configure feature installation states.
To configure Office feature installation states
1. To start the OCT, from the root of the network installation point, type the following at the command prompt: setup.exe /admin.
2. In the Select Product dialog box, select the product that you want to configure, and then click OK.
3. In the left navigation pane, locate Features, and then click Set feature installation states.
4. In the right navigation pane, expand the tree and select the feature that you want to customize. For example, if you opt not to install the Equation Editor, expand Microsoft Office and Office Tools, right-click Equation Editor, and then select the installation options Not Available, Hidden, and Locked. Setup does not install the Equation Editor and, if Setup is run interactively, this feature is not visible and the user cannot install it.
5. On the File menu, click Save As.
6. In the Save As dialog box, specify a path and file name for the Setup customization file, and then click Save.
7. On the File menu, click Exit.
8. Copy the Setup customization file to the Updates folder in the network installation point.When you run Setup to install Office, Setup uses the customization file that it finds in the Updates folder and configures Office features according to your customizations.
The following table describes the available installation options.
OptionDescriptionRun from My ComputerSetup copies files and writes registry entries and shortcuts that are associated with the feature to the user's hard disk, and the feature (or application) runs on the user's computer.Run all from My ComputerThis option is the same as Run from My Computer, except that all child features that belong to the feature are also set to this state.Installed on First UseSetup leaves components for the feature and all of its child features in the local installation source until the user first attempts to use the feature, at which time the components are copied to the Office program folder on the user's local hard disk. Some features do not support Installed on First Use; this option is not available for these features in the OCT.Not AvailableThe components for the feature, and all of the child features that belong to that feature, are not installed on the user's computer. HiddenThe feature and all of its child features do not appear in the feature tree when Setup runs interactively. Setup uses the default installation state, or the state specified in the customization file, to determine how to install the feature.
Note
I f y o u s e t t h e H i d d e n o p t i o n f o r a s p e c i f i c f e a t u r e b y u s i n g t h e O C T o r t h e C o n f i g . x m l f i l e d u r i n g a n i n i t i a l i n s t a l l a t i o n o f O f f i c e 2 0 1 0 , y o u c a n n o t u n h i d e t h a t f e a t u r e i n t h e f e a t u r e t r e e b y u s i n g a n o t h e r C o n f i g . x m l f i l e o r b y a p p l y i n g a s e c o n d . m s p file after the initial installation. If you selected the Hidden option, the feature is not displayed in the feature tree during installation. The feature remains hidden. The feature will not be displayed in Add or Remove Programs (Change or Remove Programs in Windows XP or under the Programs and Features option in Windows Vista) in Control Panel if you opt to change your Office 2010 installation; it will not be displayed in the Office Setup feature installation tree under the Add or Remove Features option fo r O f f i c e 2 0 1 0 . H o w e v e r , y o u c a n u n l o c k t h e f e a t u r e t o i n s t a l l a n d r u n i t l o c a l l y l a t e r b y u s i n g a n . m s p f i l e o r a C o n f i g . x m l f i l e .
I f y o u s e t t h e L o c k e d o p t i o n f o r a f e a t u r e b y u s i n g t h e O C T o r t h e C o n f i g . x m l f i l e d u r i n g i n i t i a l i n s t a l l a t i o n , t h a t f e a t u r e c a n b e u n l o c k e d a n d i n s t a l l e d l o c a l l y b y u s i n g a n . m s p f i l e o r a C o n f i g . x m l f i l e .
F o r i n s t a n c e , y o u c a n e d i t t h e C o n f i g . x m l f i l e t o m o d i f y t h e O p t i o n S t a t e e l e m e n t a s s h o w n i n t h e f o l l o w i n g e x a m p l e . T h i s a d d s t h e O p t i o n S t a t e e l e m e n t l i n e t o u n i n s t a l l t h e f e a t u r e ( i n t h i s c a s e , M i c r o s o f t A c c e s s ) o n a u s e r ' s c o m p u t e r , a n d t o s e t c h i l d f e a t u r e s o f t h e f e a t u r e t o t h e s p e c i f i e d s t a t e .
F o r m o r e i n f o r m a t i o n a b o u t t h e C o n f i g . x m l f i l e , s e e H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / e 1 6 a f 7 1 c - f e d 4 - 4 0 d a - a 8 8 6 - 9 5 e 5 9 6 c 3 9 9 9 e ( O f f i c e . 1 4 ) . a s p x " C o n f i g . x m l f i l e i n O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / e 1 6 a f 7 1 c - f e d 4 - 4 0 d a - a 8 8 6 - 9 5 e 5 9 6 c 3 9 9 9 e ( O f f i c e . 1 4 ) . a s p x ) .
Y o u c a n a l s o u s e t h e O C T t o c r e a t e a n . m s p f i l e t o i n s t a l l t h e f e a t u r e l a t e r . T o d o t h i s , c l i c k Set feature installation states. In the right navigation pane, right-click a feature, and then set the feature installation state to Run all from My Computer.LockedThe feature cannot be changed by the user during interactive Setup or maintenance mode.
Note
T h e f o l l o w i n g s u b c o m p o n e n t s o f M i c r o s o f t P u b l i s h e r 2 0 1 0 a r e n o t v i s i b l e i n t h e S e t u p f e a t u r e i n s t a l l a t i o n s t a t e t r e e i n O f f i c e 2 0 1 0 :
W h e n y o u c h a n g e t h e i n s t a l l a t i o n s t a t e o f a f e a t u r e , S e t u p m i g h t c h a n g e t h e i n s t a l l a t i o n s t a t e o f a p a r e n t o r c h i l d f e a t u re to match. For more information, see the HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Set_feature_installation_states"Set feature installation states (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Set_feature_installation_states) section in HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
As with any deployment of Office, make sure that you test customizations and deployment in a non-production environment before you deploy Office 2010 to users in the organization.
See Also
HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010
HYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010
HYPERLINK "http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx"Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx)
Configure user settings for Office 2010
After you create a network installation point but before you install the Microsoft Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file (.msp file). Many user settings can be configured in the OCT to customize the user's environment. For example, you can use the OCT to configure the default settings for several AutoCorrect options in Microsoft Word 2010. When you configure a user setting, that setting is in place when the user first runs an Office application.
Note:
Configuring a user setting in this manner is not necessarily permanent; it merely establishes the initial default value for the setting. The user can modify most settings after Office is installed. If you have to enforce user settings and prevent users from changing the settings, use Group Policy.
In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Configure user settings
Use the following procedure to configure user settings for Office 2010.
To configure user settings
1. To start the OCT, from the root of the network installation point, type the following at the command prompt: setup.exe /admin.
2. In the Select Product dialog box, select the product that you want to configure, and then click OK.
3. In the left navigation pane, locate Features, and then click Modify user settings.
4. In the right navigation pane, expand the tree, and then click the product for which you want to configure settings.
5. In the Settings column, double-click the user setting that y o u w a n t t o c o n f i g u r e . A P r o p e r t i e s d i a l o g b o x a p p e a r s .
6 . S e l e c t o n e o f t h e f o l l o w i n g o p t i o n s , a n d t h e n c l i c k O K .
N o t C o n f i g u r e d T h e s e t t i n g r e m a i n s a s i t i s .
E n a b l e d T h e s e t t i n g i s m o d i f i e d b a s e d o n y o u r c h o i c e s i n t h e P r o p e r t i e s d i a l o g b o x . I f v a l u e s a r e a v a i l a b l e f o r t h e s e t t i n g , s e l e c t t h e v a l u e t h a t y o u w a n t t o u s e .
D i s a b l e d T h e s e t t i n g i s d i s a b l e d . N o t e t h a t d i s a b l i n g a n o p t i o n m a y b e d i f f e r e n t f r o m n o t c o n f i g u r i n g t h e o p t i o n . S e e t h e d e s c r i p t i o n o f t h e s p e c i f i c o p t i o n f o r m o r e i n f o r m a t ion.
Note:
If you click Enabled to view the options for a setting and then click OK, Previous Setting, or Next Setting, the status changes to configured, even if you do not change the setting. Inadvertently configuring the setting with an empty hyperlink, path, or file name can cause errors. If you clicked Enabled and want to ignore your changes or avoid configuring the setting, click Cancel in the Properties dialog box for the setting. You can also return a setting to the Not Configured state by double-clicking the setting, selecting Not Configured, and clicking OK.
For example, to specify the default format in which you want users to save Word 2010 files, in the navigation pane expand Microsoft Word 2010, expand Word Options, and then click Save. In the list pane, in the Setting column, double-click Default file format. The Default file format Properties dialog box appears. Select Enabled, click the drop-down list arrow, click the file format that you want to specify, and then click OK.
7. If you want to preserve user settings from previous versions of Office, select the Migrate user settings check box.
Note:
If you modify user settings and also select the Migrate user settings check box, Setup first applies the modified settings and then migrates the user's existing custom settings, overwriting any conflicting settings.
8. On the File menu, click Save As.
9. Specify a path and file name for the Setup customization file, and then click Save.
10. On the File menu, click Exit.
11. Copy the Setup customization file to the Updates folder in the network installation point.When you run Setup to install Office 2010, Setup uses the Setup customization file (.msp file) in the Updates folder and configures user settings.
See Also
HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010
HYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010
HYPERLINK "http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx"Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
Create different configurations of Office 2010 for different groups of users
This article provides required information and procedures to create different configurations of Microsoft Office 2010 for groups of users that have different requirements. You can create unique configurations of Office 2010 customized for each group by using one of the methods described in this article.
The first method uses the Office Customization Tool (OCT) to create a Setup customization .msp file for each group. You then use the command line to run Setup and specify the customization .msp file. The second method uses the Config.xml file and a Setup customization .msp file to customize the installation, and uses a separate installation folder that contains the Setup program and all the customization files for the installation. You then run Setup from that separate installation folder.
In Office 2010, two architecture-specific versions of the OCT are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Typically, the first step in a corporate deployment of Office 2010 is to create a network installation point. You do this by copying all the source files from your Office CD to a shared location on the network. Users run Setup from the network installation point, or you use the installation point as a starting place to create a hard-disk image or a custom CD or to distribute Office by using a deployment management tool such as Microsoft System Center Configuration Manager. For more information, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.
In this article:
H Y P E R L I N K \ l " z 1 8 3 3 " C r e a t e c u s t o m c o n f i g u r a t i o n s f o r a g r o u p o f u s e r s
H Y P E R L I N K \ l " z 1 8 3 4 " C r e a t e a c u s t o m c o n f i g u r a t i o n f o r a g r o u p o f u s e r s b y u s i n g a s e p a r a t e i n s t a l l a t i o n f o l d e r
C r e a t e c u s t o m c o n f i g u r a t i o n s f o r a g r o u p o f u s e r s
T h e m e t h o d d e s c ribed in this section uses the OCT to create a unique Setup customization file (.msp file) for each group. Then you install Office for the users by specifying the customization file on the Setup command line.
To configure customizations for a group of users
1. Create a network installation point for Office. For more information, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.
2. In the root of the network installation point, create a folder for your Setup customization files.
Note:
Do not put your customization files in the Updates folder. Setup automatically applies customization files that it finds in this folder during installation. Instead, you direct Setup to use only the customization file that you specify on the command line, as described in step 5.
3. Start the OCT by running Setup from the network installation point. Specify the /admin command-line option; for example, \\server\share\setup.exe /admin. For more information, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
4. Make the customizations that you want to use for the first group of users.
a. On the File menu, click Save.
b. Specify a unique name for the Setup customization file. Save the file in the folder that you created.
c. Repeat the process to create a unique Setup customization file for each group of users.
5. Run Setup for the users within each group. Specify the appropriate Setup customization file by using the /adminfile command-line option. For example, to install Office for users in the Accounting department, run \\server\share\setup.exe /adminfile \\server\share\custom\accounting.msp. For more information, see HYPERLINK \l "z8e6eac3fa30b4afe8eb71ab775a2c0fb"Run Setup from a network installation point.Create a custom configuration for a group of users by using a separate installation folder
The method described in this section uses the Config.xml file and a Setup customization .msp file to create customizations for each group of users. It also uses a separate installation folder from the primary network installation point to store Setup.exe, Config.xml, Osetup.dll, and the Setup customization .msp files. The remaining necessary installation files will be contained in the primary network installation folder for Office 2010. You run (or have users run) Setup from that separate installation folder.
The primary difference between the method described in this section and the preceding one is the use of the separate installation folder. The benefit of a separate installation folder for a group of users is that you (or the users in that group) can run Setup from that separate installation location and receive the customized configuration of the group without having to use complex commands and network paths with Setup.exe.
To create and install a custom configuration for a group of users by using a separate installation folder
1. Create a folder that is separate from the primary network installation folder for Office 2010. For example, GroupCustomOfficeInstallFolder.
2. Create a copy of Setup.exe, Config.xml, and Osetup.dll in the new folder. These files are in the primary network installation folder.
Setup.exe is located at the root of the folder. The Config.xml file and Osetup.dll are stored in the core product folder: core_product_folder_name.WW folder; for example, ProPlus.WW.
3. Usi n g a t e x t e d i t o r , o p e n C o n f i g . x m l a n d d o t h e f o l l o w i n g :
E d i t t h e L o c a t i o n a t t r i b u t e i n t h e D i s t r i b u t i o n P o i n t e l e m e n t t o g e t t h e O f f i c e 2 0 1 0 i n s t a l l a t i o n f i l e s f r o m t h e p r i m a r y n e t w o r k i n s t a l l a t i o n f o l d e r , a s s h o w n i n t h e f o l l o w i n g e x a m p l e . F o r i n f o r m a t i on about Config.xml, see HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
I f y o u u s e d t h e O C T t o c r e a t e o n e o r m o r e S e t u p c u s t o m i z a t i o n f i l e s ( . m s p f i l e s ) , e d i t t h e C h e c k F o r S U p d a t e s a n d S U p d a t e L o c a t i o n a t t r i b u t e s i n t h e S e t u p U p d a t e s e l e m e n t i n C o n f i g . x m l a s s h o w n i n t h e f o l l o w i n g e x a m p l e t o e n a b l e S e t u p t o f i n d S e t u p c u s t o m i z a tion files in the new folder. (By default, Setup looks for Setup customization files in the Updates folder, and then runs them in alphabetical order if there is more than one.)
Important
4. Run Setup.exe from the new GroupCustomOfficeInstallFolder folder. You can map a drive for users or run Setup from the command line, as shown in the following example.
\\share\GroupCustomOfficeInstallFol d e r \ s e t u p . e x e Y o u c a n u s e t h e C o n f i g . x m l f i l e t o c o n f i g u r e t h e f o l l o w i n g a r e a s :
S p e c i f y t h e p a t h o f t h e n e t w o r k i n s t a l l a t i o n p o i n t .
S e l e c t w h i c h p r o d u c t t o i n s t a l l .
C u s t o m i z e S e t u p o p t i o n s , s u c h a s l o g g i n g a n d t h e l o c a t i o n o f t h e S e t u p c u s t o m i z a t i o n f i l e a n d s o f t w a r e u p d a t e s .
A d d o r r e m o v e l a n g u a g e s f r o m t h e i n s t a l l a t i o n .
S e t i n s t a l l a t i o n o p t i o n s , s u c h a s u s e r n a m e a n d c o m p a n y n a m e .
C o p y t h e l o c a l i n s t a l l a t i o n s o u r c e ( L I S ) t o u s e r s c o m p u t e r s w i t h o u t i n s t a l l i n g O f f i c e .
F o r m o r e i n f o r m a t i o n , s e e HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
As with any Office deployment, test customizations and deployment in a nonproduction environment before you deploy Office to users in the organization.
See Also
HYPERLINK "http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx"Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010
HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx)
Import an Office 2010 Setup customization file
This article provides required information and procedures to import an Office Customization Too l ( O C T ) S e t u p c u s t o m i z a t i o n f i l e ( . m s p f i l e ) i n M i c r o s o f t O f f i c e 2 0 1 0 .
I n t h i s a r t i c l e :
H Y P E R L I N K \ l " z 1 9 3 5 " O v e r v i e w
H Y P E R L I N K \ l " z 1 9 3 6 " I m p o r t a S e t u p c u s t o m i z a t i o n f i l e
H Y P E R L I N K \ l " z 1 9 3 7 " I m p o r t l a n g u a g e s t o a n e x i s t i n g i n s t a l l a t i o n
O v e r view
In Office 2010, two architecture-specific versions of the Office Customization Tool are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version.
You start the OCT by running the setup.exe /admin command at the command prompt from the root of the network installation point that contains the Office 2010 source files. (For more information, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.) For example, run the following command line to start the OCT: \\server\share\Office14\setup.exe /admin. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To r u n t h e 6 4 - b i t O C T , r u n t h e s e t u p . e x e / a d m i n c o m m a n d l i n e f r o m t h e x 6 4 ( 6 4 - b i t ) f o l d e r .
T h e O C T s u p p o r t s t h e i m p o r t i n g o f S e t u p c u s t o m i z a t i o n f i l e s ( . m s p f i l e s ) :
3 2 - b i t . m s p f i l e s c a n b e i m p o r t e d i n t o t h e 6 4 - b i t O C T , a n d t h e n t h e y c a n b e u s e d t o c u s t o m i z e 6 4 - b i t O f f i c e 2 0 1 0 p r o d u c t s .
6 4 - b i t . m s p f i l e s c a n b e i m p o r t e d i n t o t h e 3 2 - b i t O C T , a n d t h e n t h e y c a n b e u s e d t o c u s t o m i z e 3 2 - b i t O f f i c e 2 0 1 0 p r o d u c t s .
N o t e
I m p o r t i n g c u s t o m i z a t i o n . m s p f i l e s i s i n t e n d e d f o r e q u i v a l e n t c r o s s - a r c h i t e c t u r e p r o d u c t s o nly. You can import a 32-bit Microsoft Office Professional Plus 2010 customization .msp file into the 64-bit version of the OCT for a 64-bit Office Professional Plus 2010 .msp file. However, you cannot import a 32-bit Microsoft Word 2010 stand-alone customization .msp file into the 64-bit OCT for a 64-bit Office Professional Plus 2010 .msp file; doing so is prevented and displays an error message. For information about how to use the OCT to create a Setup customization file and about all the areas that you can configure with the OCT, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
Y o u c a n n o t i m p o r t 2 0 0 7 M i c r o s o f t O f f i c e s y s t e m S e t u p c u s t o m i z a t i o n f i l e s ( . m s p f i l e s ) i n t o t h e O f f i c e 2 0 1 0 O C T .
T h e I m p o r t f e a t u r e c a n a l s o b e u s e d w h e n y o u h a v e c r e a t e d a n i n i t i a l S e t u p c u s t o m i z a t i o n f i l e ( . m s p f i l e ) f o r a n O f f i c e 2 0 1 0 p r o d u c t ( f o r e x a m ple, Microsoft Office Professional Plus 2010) and you later want to modify the installation to add language packs. In such cases, you first add the language packs to the network installation point that contains the Office product source files. Then, you run the OCT from the root of the network installation point and create a new Setup customization file for the same product, and import the original customization .msp file that you created previously for Microsoft Office Professional Plus 2010. For more information, see HYPERLINK \l "z1939"To import a customization .msp file to add languages to an existing installation.
Import a Setup customization file
Use the following procedure to import a Setup customization file (.msp file).
To import a Setup customization file
1. Start the OCT by typing setup.exe /admin at the command prompt from the root of the network installation point that contains the Office 2010 source files. For example:
\\server\share\Office14\setup.exe /admin
2. To import a customization .msp file, in the OCT, on the File menu, click Import.
3. In the Open dialog box, select the .msp file that you want to convert, and then click Open to start the conversion.
4. On the File menu, click Save As. Specify a unique name for the file and save the file in the Updates folder of the network installation point for the platform for which you imported the customization .msp file (either 32-bit or 64-bit). For example, if you imported a 32-bit customization .msp file for customizing a 64-bit installation of Office 2010, you would save the file in the Updates folder of the network installation point for 64-bit Office 2010.
5. Click Save.Import languages to an existing installation
If you create a Setup customization file (.msp file) to customize the Office 2010 installation and later decide to add languages, you can use the Import option in the OCT to apply the language changes. Use the following procedure to import languages to an existing installation. This procedure uses Office Professional Plus 2010 as an example.
To import a customization .msp file to add languages to an existing installation
1. Add the language packs that you want to use to the network installation point that contains the Office Professional Plus 2010 source files. For more information, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.
2. Run the OCT by typing setup.exe /admin at the command-line prompt from the root of the network installation point that contains the Office Professional Plus 2010 source files. For example:
\\server\share\Office14\setup.exe /admin
3. In the Select Product dialog box, click Create a new Setup customization file for the following product and then choose the same product for which you previously customized installation options, Microsoft Office Professional Plus 2010 in this example.
4. To import the original customization .msp file that you created previously for Microsoft Office Professional Plus 2010, on the File menu, click Import.
5. In the Open dialog box, select the .msp file that you want to update.
6. On the File menu, click Save As. Specify a unique name for the .msp file, and then click Save.
Note:
The Updates folder supports only one Setup customization .msp file. Therefore, if you import a Setup customization .msp file to add languages to an existing installation, we recommend that you replace your previous customization .msp file (the original .msp file) with the new customization .msp file that contains the language packs information.
7. Deploy and apply the updated Setup customization file .msp to users' computers.
To apply the Setup customization (.msp) file to existing installations, you must apply the .msp file directly to the user's computer. Users can apply the Setup customization .msp file by double-clicking the .msp file, or by running the msiexec command with the /p option as shown in the following example (using custom.msp): msiexec.exe /p \\server\share\custom.msp.
For more information about Windows Installer commands, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=162945"Windows Installer Command-Line Options (http://go.microsoft.com/fwlink/?LinkID=162945).
You can also use a deployment management program, such as Microsoft System Center Configuration Manager 2007, to deploy Setup customization files.See Also
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010
HYPERLINK \l "za33e64b046a545e5b76f3add595af8de"Customize Office 2010
HYPERLINK \l "z9c14db60b59141f9a94b50627d2daa81"Customize Setup before installing Office 2010
HYPERLINK "http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx"Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-996d-09e671a41e9c(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx)
Configure a silent installation of Office 2010 by using Config.xml
This article provides required information and procedures to configure a silent installation of Microsoft Office 2010 by using the Config.xml file. The Config.xml file is used to configure installation tasks and is used only when you run 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) directs Setup to install that product. For example, the Config.xml file in the Pro.WW folder installs Microsoft Office Professional 2010.
Modify the Config.xml file to configure a silent installation
To configure a silent installation (unattended installation) of an Office 2010 product that requires no user interaction, modify the Config.xml file for the product that you are installing and set the Display element's Level attribute to "none" (Display Level="none"), and then save the Config.xml file, as shown in the following procedure. The Display element specifies the level of user interface that Setup displays to users.
To specify silent installation options in Config.xml
1. Open the Config.xml file for the Office product (such as Office Professional Plus 2010) that you are installing by using a text editor tool, such as Notepad.
2. Locate the line that contains the Display element, as shown in the following example:
3. Modify the Display element entry with the silent options that you want to use. Make sure that you remove the comment delimiters, "". For example, use the following syntax:
These options will direct Setup to run silently, prevent prompting users to enter information, and prevent the installation from waiting for any user interaction. For more information about the syntax and Config.xml, see Display element in HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
4. Save the Config.xml file.Make sure that no Office applications are running when you install Office 2010. For example, to install Office Professional Plus 2010 after you modify the Config.xml file to specify silent installation options, use the following command:
\\server\share\setup.exe /config \\server\share\ProPlus.WW\config.xml
Where:
\\server\share is the path of the Office Professional Plus 2010 source files.
/config is a Setup command-line option that specifies the location of the Config.xml file. See HYPERLINK "http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx"Setup command-line options for Office 2010 (http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx).
\\server\share\ProPlus.WW\config.xml is the location of your modified Config.xml file for Office Professional Plus 2010.
Note
I f y o u u s e t h e C o n f i g . x m l f i l e t o s e t s i l e n t i n s t a l l a t i o n o p t i o n s a s i n t h e p r e v i o u s e x a m p l e , y o u w i l l a l s o w a n t t o u s e t h e O f f i c e C u s t o m i z a t i o n T o o l ( O C T ) t o c r e a t e a S e t u p c u s t o m i z a t i o n f i l e ( . m s p f i l e ) t o c o n f i g u r e a d d i t i o n a l i n s t a l l a t i o n c u s t o m i z a t i o ns. For example, you can use the OCT to specify previous versions of Microsoft Office applications to keep or remove. You can also set feature installation states by using the OCT to change the default way in which Office features are installed. For a complete description of the areas that you can configure by using the OCT, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx). The OCT is available with Volume Licensing editions of Office 2010 (and the 2007 Office system). To determine whether your Office 2010 installation is a Volume Licensing edition, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a Volume Licensing edition. If the Admin folder does not exist, the disk is a retail edition.
Y o u c a n a l s o s e t s i l e n t i n s t a l l a t i o n o p t i o n s b y u s i n g t h e O C T . F o r m o r e i n f o r m a t i o n , s e e t h e H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 8 f a a e 8 a 0 - a 1 2 c - 4 f 7 b - 8 3 9 c - 2 4 a 6 6 a 5 3 1 b b 5 . a s p x # L i c e n s i n g _ a n d _ u s e r _ i n t e r f a c e " L i c e n s i n g a n d u s e r i n t e r f a c e ( h t t p : / / t e chnet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Licensing_and_user_interface) section in HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx). (The Level attribute of the Display element in the Config.xml file is equivalent to the Display Level option in the OCT). In enterprise deployments, we recommend that you set the Display Level to None if using the OCT to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used. Setting the Display Level to None assumes that the Suppress modal and Completion notice options are silenced and that the I accept the terms in the License Agreement check box is selected. As noted previously, administrators must also make sure that no Office applications are running during an installation of Office 2010.
Run arbitrary commands with installations of Office 2010
By default, the Setup program for Microsoft Office 2010 installs one Office product at a time. You can use the chaining feature to customize Setup to run an arbitrary command or a lightweight executable that you want to run when this product is installed. To add an arbitrary command or a lightweight executable, you can use the Add installations and run programs feature in the Office Customization Tool (OCT) or the Command element in the Config.xml file. We recommend that you limit the use of Add installations and run programs and the Command element to running only lightweight executables or arbitrary commands that will not make changes to the computer or that do not require user input. For example, you can run a utility to copy logs or a command to launch a Welcome page at the end of installation.
The Add installations and run programs option in the OCT (command lines entered in the Add Program Entry and Modify Program Entry dialog boxes) and the Command element in the Config.xml file are intended to be used only for initial product installations and uninstallations. The commands are processed only during initial installations and uninstallations.
Important:
Chaining is not as reliable as installing each product separately. For example, if you chain two installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation might not finish successfully. Therefore, we do not recommend using the chaining approach. The recommended method for installing multiple products together is to use a deployment management program, such as Microsoft Systems Management Server or Microsoft System Center Configuration Manager 2007, or a third-party tool, instead of chaining.
In the following example, the OCT is used to add an arbitrary program to the installation.
To customize the primary installation to run a command
1. Create a network installation point that includes the product that you will install. For more information, see HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010.
2. Run the OCT by running Setup.exe from the root of the network installation point with the /admin command-line option. For example, run: \\server\share\Office14\setup.exe /admin.
3. In the Select Product dialog box, select the product that is the primary installation.
4. In the left pane of the OCT, select Licensing and user interface. In the right pane, set Display level to None, enter the Product key, and select I accept the terms in the License Agreement.
For more information about HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Licensing_and_user_interface"Licensing and user interface (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Licensing_and_user_interface) and Display level options, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
5. In the left pane, select Add installations and run programs. In the right pane, click Add.
6. In the Add Program Entry dialog box, perform the following steps for the executable that is chained.
F o r T a r g e t , e n t e r t h e f u l l y q u a l i f i e d p a t h o f t h e e x e c u t a b l e f i l e t h a t y o u w a n t t o r u n a f t e r t h e p r i m a r y i n s t a l l a t i o n . F o r e x a m p l e , e n t e r \ \ s e r v e r \ s h a r e \ O f f i c e 1 4 \ c o p y l o g s . b a t .
F o r A r g u m e n t s , e n t e r t h e s t r i n g o f a r g u m e n t s t o b e p a s s e d t o t h e e x e c u t a b l e . For example, enter: QuietArg="/q" Wait="30000".
For information about the Command element and supported attributes, see HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e.aspx#ElementCommand"Command element (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e.aspx#ElementCommand) in HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
Note:
As mentioned previously, command lines entered in the Add Program Entry and Modify Program Entry dialog boxes are intended to be used only for initial installs and uninstalls. Command lines are processed only during initial installs and uninstalls.
S e l e c t t h e R u n t h i s p r o g r a m a f t e r t h e O f f i c e p r o d u c t h a s b e e n i n s t a l l e d o p t i o n t o r u n t h e p r o g r a m l i s t e d i n t h e T a r g e t b o x a f t e r t h e O f f i c e i n s t a l l a t i o n i s c o m p l e t e d . T h i s i s t h e r e c o m m e n d e d o p t i o n .
Y o u c a n a l s o s e l e c t t h e R u n t h i s p r o g r a m b e f o r e t h e O f f ice product has been installed option if you want the program listed in the Target box to run before the Office installation starts. However, if the program does not terminate correctly, or if it restarts the computer, Office is not installed, and programs further down the list do not run.
C l i c k O K .
7 . M a k e o t h e r c u s t o m i z a t i o n s i n t h e O C T a s n e e d e d .
8 . S a v e t h e S e t u p c u s t o m i z a t i o n f i l e ( . m s p f i l e ) w i t h a u n i q u e n a m e i n t h e U p d a t e s f o l d e r o f t h e n e t w o r k i n s t a l l a t i o n p o i n t .
9 . E x i t t h e O C T . T o i n s t a l l t h e p r o d u c t
1 . R u n S e t u p f r o m t h e r o o t of the network installation point. For example, if the primary product is Microsoft Office Professional Plus 2010, enter \\server\share\setup.exe
-or-
If you also used the Config.xml file to configure installation options in addition to the OCT setup customization .msp file customizations, run Setup from the root of the network installation point and specify the Config.xml file that you customized for the primary product. For example, if the primary product is Office Professional Plus 2010, enter:
\\server\share\setup.exe /config \\server\share\ProPlus.WW\config.xml
2. In the Select Product dialog box, select the primary product.After Setup installs the primary product, it runs the arbitrary command or lightweight executable that you specified in the OCT.
Tip:
You can put the customization files that you created in a location other than the Updates folder. Just add the /adminfile option to the Setup command lines in the procedures earlier in this section to specify the customization files to use. For more information about how to use Setup command-line options, see HYPERLINK "http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx"Setup command-line options for Office 2010 (http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-3a2a2da8f731(Office.14).aspx).
How it works
The Setup program for the primary product follows the typical installation process. After that installation is complete, Setup runs the additional lightweight executable or arbitrary command that you specified in the OCT. Setup waits until each program is finished before it runs the next program.
It is important to run the primary Setup quietly. A chained Setup program cannot run if the primary Setup program is running interactively. You must run the primary Setup program with Display level set to None. We recommend that chained installations also be run with Display level set to None. And because you are running Setup quietly, you must enter the product key for each product in the OCT.
See Also
HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx)
HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx)
HYPERLINK \l "z8e6eac3fa30b4afe8eb71ab775a2c0fb"Run Setup from a network installation point
Create custom configurations of Office 2010
This article describes how to deploy an initial customized installation of Microsoft Office 2010 to users in your organization. This article also includes an example of a Config.xml file.
In this article:
H Y P E R L I N K \ l " z 2 2 4 3 " O f f i c e C u s t o m i z a t i o n T o o l c h a n g e s i n O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 2 2 4 4 " C r e a t i n g a c u s t o m c o n f i g u r a t i o n
H Y P E R L I N K \ l " z 2 2 4 5 " C o n f i g . x m l e x a m p l e
W e r e c o m m e n d t h a t y o u r e a d t h e f o l l o w i n g a r t i c l e s b e f o r e y o u c u s t o m i z e t h e i n s t a l l a t i o n :
H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 0 7 3 5 c 1 f 5 - f 8 7 4 - 4 1 f 1 - b 9 a 9 - d b e a 1 5 8 5 2 4 b 2 ( O f f i c e . 1 4 ) . a s p x " V o l u m e a c t i v a t i o n o v e r v i e w f o r O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / 0 7 3 5 c 1 f 5 - f 8 7 4 - 4 1 f 1 - b 9 a 9 - d b e a 1 5 8 5 2 4 b 2 ( O f f i c e . 1 4 ) . a s p x )
H Y P E R L I N K " h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / c 6 5 4 5 5 7 9 - 4 c c a - 4 a d 1 - 8 2 9 d - c f e c b b 9 1 7 d c 4 ( O f f i c e . 1 4 ) . a s p x " P l a n v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0 ( h t t p : / / t e c h n e t . m i c r o s o f t . c o m / l i b r a r y / c 6 5 4 5 5 7 9 - 4 c c a - 4 a d 1 - 8 2 9 d - c f e c b b 9 1 7 d c 4 ( O f f i c e . 1 4 ) . a s p x )
H Y P E R L I N K \ l " z b 4 1 8 5 0 1 a e b 8 3 4 9 9 1 8 e a 9 b 1 8 e 7 3 0 9 e 0 6 0 " D e p l o y v o l u m e a c t i v a t i o n o f O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 1 8 2 5 d f 7 6 7 e 2 3 4 5 9 b a 6 c 1 2 2 4 d d 6 e a b 8 1 e " T o o l s t o c o n f i g u r e c l i e n t c o m p u t e r s i n O f f i c e 2 0 1 0
H Y P E R L I N K \ l " z 7 2 a 9 3 e b f 3 8 9 a 4 9 1 a 9 4 c 8 d 7 d a 0 2 6 4 2 1 3 9 " C u s t o m i z a t i o n o v e r v i e w f o r O f f i c e 2010
Office Customization Tool changes in Office 2010
The Office Customization Tool (OCT), part of the Setup program, is the primary tool that is used to customize an Office 2010 client installation. It is included in Volume License versions of Office 2010 such as Microsoft Office Professional Plus 2010. Before you begin your customizations, you should be aware of the following changes in the Office 2010 OCT.
In Office 2010, two architecture-specific versions of the Office Customization Tool are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version.
The Office 2010 OCT supports the import of setup customization .msp files:
3 2 - b i t O f f i c e 2 0 1 0 . m s p f i l e s c a n b e i m p o r t e d i n t o t h e 6 4 - b i t O C T , a n d t h e n t h e y c a n b e u s e d t o c u s t o m i z e 6 4 - b i t O f f i c e 2 0 1 0 p r o d u c t s .
6 4 - b i t O f f i c e 2 0 1 0 . m s p f i l e s c a n b e i m p o r t e d i n t o t h e 3 2 - b i t O C T , a n d t h e n t h e y c a n b e u s e d t o c u s t o m i z e 3 2 - b i t O f f ice 2010 products.
Note:
You can import a setup customization .msp file for equivalent cross-architecture products only. For example, you can import a 32-bit Microsoft Office Professional Plus 2010 customization .msp file into the 64-bit version of the OCT for a 64-bit Office Professional Plus 2010 .msp file. However, you cannot import a 32-bit Microsoft Word 2010 stand-alone customization .msp file into the 64-bit OCT for a 64-bit Microsoft Office Professional Plus 2010 .msp file; doing so is prevented and displays an error message. You cannot import 2007 Microsoft Office system Setup customization files (.msp files) into the Office 2010 OCT.
For more information about the OCT, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx). For more information about the import feature, see HYPERLINK \l "z6bd883424f3a4535a570475d251ef9da"Import an Office 2010 Setup customization file. For information about 64-bit Office 2010, see HYPERLINK "http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx"64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-24f6939548d1(Office.14).aspx).
Creating a custom configuration
The following table highlights the process of how to deploy a custom configuration.
StepsReferencesCopy all the files and folders from the Office 2010 CD to a folder on the network or on your computer. For example, copy the files to \\server\share\Office14.
Copy all the language packs and additional Office products that you want to deploy to the same network installation point. When you are prompted to overwrite duplicate Setup files, click No.HYPERLINK \l "z72c9ae031342452482421524fbd068a5"Create a network installation point for Office 2010Use the Office Customization Tool (OCT) to customize Setup, and configure additional customizations and installation options. This creates a Setup customization file (.msp file). For a complete description of the areas that you can configure by using the OCT, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx). A new Setup customization .msp file is created in the following example.
1. From the root of the network installation point that you created previously, run the following command-line option to start the OCT: setup.exe /admin. For example, use the following: \\server\share\Office14\setup.exe /admin.
2. In the Select Product dialog, select Create a new Setup customization file for the following product to create a new customization file (for example, for Office Professional Plus 2010 (32-bit)). Click OK.
The OCT user interface is displayed, and you can then configure settings in the following areas: Setup, Features, Additional content, and Outlook.
3. Customize Setup to specify how you want Setup to manage the installation. The Setup section of the OCT is used to configure options such as the default installation location, default organization name, additional network locations that contain the Office 2010 sources, product key, Microsoft Software License Terms, level of user interface to display, previous versions of Office to remove, and so on.
The product key option depends on the Office 2010 licensing method that you use. The following options are available in Licensing and user interface:
a. Use KMS client keyA product key entry is not required for enterprise deployments that are using Key Management Service (KMS) activation because all Volume License editions of Office 2010 have a KMS client key pre-installed. KMS is one of the methods that are provided by Office Activation Technologies for activating products licensed under Microsoft Volume Licensing programs. Only a KMS host computer needs a KMS host key to be activated and to establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. Use KMS client key is the default. For information about how to configure the KMS host, see HYPERLINK \l "z62"Prepare and configure the KMS host in HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
b. Enter another product keyYou can enter a valid Multiple Activation Key (MAK) key in the OCT by using the Enter another product key entry. A MAK key is another method that Office Activation Technologies provide for activating products licensed under Microsoft Volume Licensing programs. With a MAK, clients activate Office 2010 online by using the Microsoft hosted activation servers or by telephone. To use a MAK key, in the Enter another product key text box, enter the MAK key (twenty-five numbers or characters) without spaces. For more information about how to use a MAK key, see HYPERLINK \l "zb418501aeb8349918ea9b18e7309e060"Deploy volume activation of Office 2010.
Expand the Display level menu to set the behavior of the user interface during installation. In enterprise deployments, we recommend that you set Display level to None to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used. Setting Display Level to None assumes that the Suppress modal and Completion notice options are silenced and that the Microsoft Software License Terms is accepted. You can also configure display level options by using the Config.xml file; see HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e.aspx#ElementDisplay"Display element (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e.aspx#ElementDisplay) in HYPERLINK "http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx"Config.xml file in Office 2010 (http://technet.microsoft.com/library/e16af71c-fed4-40da-a886-95e596c3999e(Office.14).aspx).
You can also configure Office security settings if you want to provide an initial default configuration of security settings. For information, see HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Office_security_settings"Office security settings (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5.aspx#Office_security_settings) in HYPERLINK "http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx"Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
Important:
Although you can use the OCT to specify initial default security settings in a Setup customization file (.msp file), users can change the settings after installation. To enforce security settings, you must use Group Policy. For detailed information about how to plan for security settings, see HYPERLINK "http://technet.microsoft.com/library/67869078-71c6-45f5-aab0-0823c83aed54(Office.14).aspx"Security overview for Office 2010 (http://technet.microsoft.com/library/67869078-71c6-45f5-aab0-0823c83aed54(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/c38e3e75-ce78-450f-96a9-4bf43637c456(Office.14).aspx"Plan security for Office 2010 (http://technet.microsoft.com/library/c38e3e75-ce78-450f-96a9-4bf43637c456(Office.14).aspx).
For more detailed information, see HYPERLINK \l "z9c14db60b59141f9a94b50627d2daa81"Customize Setup before installing Office 2010.
4. Use the Features section to configure feature installation states. For information, see HYPERLINK \l "z5e377afe3c09447d82b906400fbf1138"Configure feature installation states for Office 2010.
For each application that you want to add to the installation, set its installation option to Run all from My Computer or Installed on First Use in the right pane. For example, to install Microsoft Outlook 2010, expand Microsoft Office and change the installation option for Microsoft Office Outlook to Run all from My Computer.
For applications that you do not want to install, set the installation option to Not Available in the right pane. The application name is set to bold to show that you have changed its installation option.
To prevent users from installing this application themselves, select the Hidden and Locked options. The symbols [H] and [L] are added to the application name to indicate that these options are set.
Important
I f y o u s e t t h e H i d d e n o p t i o n f o r a s p e c i f i c f e a t u r e b y u s i n g t h e O C T o r t h e C o n f i g . x m l f i l e d u r i n g a n i n i t i a l i n s t a l l a t i o n o f t h e 2 0 0 7 O f f i c e s y s t e m , y o u c a n n o t u n h i d e t h a t f e a t u r e i n t h e f e a t u r e t r e e b y u s i n g a n o t h e r C o n f i g . x m l f i l e o r a p p l y i n g a s e c o n d .msp customization file after the initial installation. This means that the feature is not displayed in the feature tree during installation. The feature remains hidden and you cannot reverse this. The feature will not be displayed in Add or Remove Programs (Change or Remove Programs) in Control Panel under the Add or Remove Features option for Microsoft Office 2010 (or under the Programs and Features option in Windows Vista). However, you can unlock the feature to install and run locally later by using an . m s p c u s t o m i z a t i o n f i l e o r a C o n f i g . x m l f i l e .
I f y o u s e t t h e L o c k e d o p t i o n f o r a f e a t u r e b y u s i n g t h e O C T o r t h e C o n f i g . x m l d u r i n g i n i t i a l i n s t a l l a t i o n , t h a t f e a t u r e c a n b e u n l o c k e d a n d i n s t a l l e d l o c a l l y b y u s i n g a n . m s p c u s t o m i z a t i o n f i l e o r a C o n f i g . x m l f i l e .
F o r e x a m p l e , y o u c a n c u s t o m i z e t h e C o n f i g . x m l f i l e t o m o d i f y t h e O p t i o n S t a t e e l e m e n t a n d a d d t h e f o l l o w i n g l i n e t o u n i n s t a l l t h e f e a t u r e ( M i c r o s o f t A c c e s s i n t h i s c a s e ) o n t h e u s e r ' s c o m p u t e r a n d s e t c h i l d f e a t u r e s o f t h e f e a t u r e t o t h e s p e c i f i e d s t a t e :
<