Deployment guide for Microsoft Office 2013 Preview Microsoft Corporation Published: July 2012 Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com) Abstract This book supports a preliminary release of Microsoft Office 2013 Preview and provides deployment instructions for Office 2013 Preview. The audiences for this book include application specialists, line-ofbusiness application specialists, and IT administrators who are ready to deploy Office 2013 Preview.
This document is provided “as-is.” Information and views expressed in this document, including URL and other Internet website 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.
Contents Getting help............................................................................................................................................... ix Volume activation of Office 2013 Preview ................................................................................................. 1 Articles about volume activation for Office 2013 Preview ................................................................... 1 Plan volume activation of Office 2013 Preview ..............................
Create a network installation point ....................................................................................................... 16 Customize Setup .................................................................................................................................. 17 Install Office silently .............................................................................................................................. 20 Office Customization Tool (OCT) in Office 2013 Preview ..........
Remove registry entries .................................................................................................................... 45 Delete/Modify Registry Entry dialog box ........................................................................................... 45 Delete/Modify Registry Entry dialog box options .............................................................................. 45 Configure shortcuts ...................................................................................
Attributes ........................................................................................................................................... 63 AddLanguage attributes .................................................................................................................... 63 Example ............................................................................................................................................ 65 ARP element ...................................................
RemoveLanguage attributes ............................................................................................................. 80 Example ............................................................................................................................................ 80 Setting element ................................................................................................................................. 80 Attributes .............................................................
Setup process .................................................................................................................................... 102 Setup sequence of events .............................................................................................................. 102 Run Setup ....................................................................................................................................... 102 Check prerequisites ...................................................
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 email message to the Microsoft Office System and Servers content team at: itspdocs@microsoft.
Volume activation of Office 2013 Preview Audience: IT Professionals Microsoft policy requires the activation of all editions of Office 2013 Preview client software, including Volume License editions. For Office 2013 Preview, volume activation occurs through Office Activation Technologies, which are based on the Software Protection Platform (SPP) that is used in Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012.
Plan volume activation of Office 2013 Preview Audience: IT Professionals You can plan the deployment of Office Activation Technologies for volume activation of Office 2013 Preview in several steps. Before you read this article, we recommend that you read Volume activation overview for Office 2010. We also highly recommend that you read the Windows Volume Activation Planning Guide. Important: This information applies to volume-licensed editions of Office 2013 Preview.
You do not have to enter a product key for Office 2013 Preview KMS clients. You only have to enter a KMS host key on your KMS host computer. If you decide to use MAK, enter the product key either through the Office Customization Tool (OCT) or the Config.xml file. After Office 2013 Preview installation, you can change the product key by using the Volume Activation Management Tool (VAMT) or the Office Software Protection Platform script (ospp.vbs). For more information about ospp.
connect to the KMS host for activation by using anonymous remote procedure calls (RPCs) through TCP communications port 1688, which is the default port number when you enable the firewall on a KMS host. You can either use the default settings, which require little or no administrative action, or manually configure KMS hosts and clients based on network configuration and security requirements. To be licensed, the KMS client must be activated.
Windows Server 2008 R2 Publication of the KMS service The KMS service uses service (SRV) resource records (RRs) in DNS to store and communicate the locations of KMS hosts. KMS hosts use dynamic updates, if available, to publish the KMS SRV RRs. If dynamic updates are not available, or if the KMS host does not have permissions to publish the RRs, you must publish the DNS records manually or configure client computers to connect to specific KMS hosts.
organizations can deploy merely two KMS hosts for their whole infrastructure (one main KMS host and one backup host for redundancy). KMS activation renewal KMS activations are valid for 180 days. This is called the activation validity interval. To remain activated, KMS clients must renew their activation by connecting to the KMS host at least one time every 180 days. By default, KMS client computers attempt to renew their activation every seven days.
MAK Independent Activation MAK independent activation requires that each computer independently connect and be activated with Microsoft, either over the Internet or by telephone. MAK independent activation is best suited for computers in an organization that does not maintain a connection to the corporate network. MAK Proxy Activation by using VAMT This enables a centralized activation request on behalf of multiple computers that have one connection to Microsoft.
2008, Windows Server 2008 R2, Windows Server 2012, Office 2010, and Office 2013 Preview. In addition, VAMT 3.0 supports Active Directory-Based activation. The following features are either new, or updated, in VAMT 3.0: User interface. The updated user interface makes volume activation and license management an easy, one-console process. Data storage. Data storage in a SQL Server database provides greater scalability and speed. Licensing reports.
Important: KMS hosts that were set up by using the Office 2013 Preview release cannot be used to activate client computers that run the final release version of Office 2013 Preview. To activate these client computers, you can either run the release version of Microsoft Office 2013 KMS Host License Pack and enter the KMS host key on the same KMS host, or you can set up a new KMS server only for activating the final release version of Office 2013 Preview.
not have administrator permissions to activate with MAK by setting the appropriate registry key in the deployments or in the master image: HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform\UserOperations =1 This registry key can also be set through the ospp.vbs script. For more information about ospp.vbs, see Tools to configure client computers in Office 2010.
Volume activation methods in Office 2013 Preview Audience: IT Professionals Three volume activation (VA) methods are available for Office 2013 Preview: Key Management Service (KMS) Multiple Activation Key (MAK) Active Directory-Based activation KMS and MAK are supported on Windows 7 and Windows 8. Active Directory-Based activation is supported only on Windows 8 and Windows Server 2012.
If you install the Office 2013 Volume License Pack on Windows 7 The KMS host installer prompts you to install and activate the KMS host key. For more information, see Deploy volume activation of Office 2010. If you install the Office 2013 Volume License Pack on Windows Server 2012 The Microsoft Office 2013 Volume Activation Tools wizard starts when the Office 2013 Volume License Pack is installed.
Generic Volume License Keys (GVLKs) for Office 2013 Preview Product GVLK Office 2013 Professional Plus PGD67-JN23K-JGVWV-KTHP4-GXR9G Project 2013 Professional NFKVM-DVG7F-TYWYR-3RPHY-F872K Visio 2013 Professional B3C7Q-D6NH2-2VRFW-HHWDG-FVQB6 For more information about KMS and MAK, see Plan volume activation of Office 2010 and Deploy volume activation of Office 2010.
Volume Activation Management Tool (VAMT) 3.0 Volume Activation Management Tool (VAMT) 3.0 is the latest version. VAMT 3.0 is designed to manage volume activations for Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Office 2010, and Office 2013 Preview. In addition, VAMT 3.0 supports Active Directory-Based activation. For more information about VAMT 3.0, see Plan volume activation of Office 2013 Preview.
Customize installations of Office 2013 Preview Audience: IT Professionals The following table includes links to articles about the customization process and about how to customize specific installations of Office 2013 Preview. Articles about how to customize Office 2013 Preview Article Description Customize Setup before installing Office 2013 Provides information about how to use the Office Customization Tool (OCT) to customize a Windows Installer-based installation of Office 2013 Preview.
Customize Setup before installing Office 2013 Audience: IT Professionals To customize Setup for Windows Installer-based Office 2013 Preview, follow the procedures in this article before you begin the installation. In Office 2013 Preview (as in Office 2010 and Office 2007), Setup controls the complete installation. This includes processes that Windows Installer handled in Office versions earlier than Office 2007. Customizing the default behavior of Setup lets you specify how the installation runs.
deployment tool, such as Microsoft System Center 2012 Configuration Manager, or to create a harddisk image or a custom DVD. Make sure that access to Office 2013 Preview source files is read-only. The Setup.xml and Package.xml files, such as ProPlusWW.xml for Office Professional 2013 Preview, are digitally signed and cannot be changed. We recommend that you replicate the network installation point to multiple locations for the following reasons: Ensure that users always have access to a network source.
all Office 2013 Preview products and language packs. Because the core Setup files are identical, there is no reason to overwrite the files when you add language packs. If you deploy multiple Office 2013 Preview products, copy those files from the DVD to the installation point. When you are prompted to overwrite duplicate Setup files, choose No. 2. From the root of the network installation point, run the following command line to start the Office Customization Tool: \\server\share\Office2013\setup.
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 details pane, set the Display Level to Basic or None to install Office quietly (without user interaction).
caused the failure. To change logging options, open the Config.xml file in Notepad and modify the element. For more information, see Config.xml file in Office 2013 Preview. 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.
Office Customization Tool (OCT) in Office 2013 Preview Audience: IT Professionals To customize an installation of Office 2013 Preview, you can use the Office Customization Tool (OCT) to perform tasks such as the following: Specifying installation options Customizing how Office applications and features are installed Configuring default user settings Managing additional content: add or remove files, registry entries or shortcuts Configuring Outlook options: setting the default profile, add
If you use the OCT to change an existing .msp customization file, we recommend that you select the .msp file for the same product that you customize. For example, if you customize Office Professional Plus 2013 Preview, select an Office Professional Plus 2013 Preview customization .msp file. Note: The Office 2013 Preview release requires Windows Installer 4.0 on computers that are running the 64-bit version of the OCT or importing 64-bit customization .msp files. Windows Installer 3.
Modify existing installations You can also use a Setup customization file to change an existing installation. Because a Setup customization file is an expanded form of a Windows Installer .msp file, you apply the customization file to the user's computer exactly as you would a software update. The user's existing Office installation is updated with the customizations that you make.
Office Customization Tool options Section Page Setup Installation location and organization name Additional network sources Licensing and user interface Remove previous installations Add installations and run programs Office security settings Modify Setup properties Features Modify user settings Set feature installation states Additional content Add files Remove files Add registry entries Remove registry entries Configure shortcuts Outlook Outlook Profile Add Accounts Export Settings Specify Send/Receive
Architecture-specific versions of the Office Customization Tool The OCT provides two architecture-specific versions, one for 32-bit Office 2013 Preview and one for 64-bit Office 2013 Preview. The 64-bit version of the OCT supports 64-bit client editions of Office 2013 Preview, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. The OCT files are located in the Admin folder under the x86 (32-bit) and x64 (64-bit) folders, respectively.
mixed environments (32-bit and 64-bit) can do the Setup customizations one time and import the customizations as follows:. Import the 32-bit Setup customization .msp files into 64-bit OCT and then use them to customize 64-bit Office products. Import the 64-bit Setup customization .msp files into 32-bit OCT and can then use them to customize 32-bit Office products. A 32-bit Setup customization .msp file that is imported to 64-bit OCT is converted to 64-bit, and a 64-bit customization .
import feature" video. Right-click the link, and then choose Save Target As to download a copy. Choosing the link will open a .wmv file in the default video viewer for fullresolution viewing.
viewer for full-resolution viewing.
Note: The OCT verifies all server paths and connects to any available servers during the initial installation process to load balance the file copy process when it creates the Local Installation Source (LIS). However, be aware that specifying an unavailable source as an additional source does not cause the installation to fail. Add/Modify Network Server Entry dialog box In the Add Network Server Entry dialog box or Modify Network Server Entry dialog box, enter the path of a server and then choose OK.
Important: This information applies to volume-licensed editions of Office 2013 Preview. It does not apply to either Office Professional Plus for Office 365 or Office 365 ProPlus Preview, both of which are licensed through subscription. The Product key text box must not be used to set product keys for Office Professional Plus for Office 365. For information about Office Professional Plus for Office 365, see Overview of Office 365 ProPlus Preview.
None prevents prompting users in these cases. The Suppress modal option does not prevent files-in-use messages from being displayed; only Display level set to None prevents files-in-use messages from being displayed. Completion notice Select this check box if you want Setup to display a message to the user when installation is complete. Suppress modal Select this check box if you do not want Setup to display error messages and other dialog boxes that might interrupt the installation.
By default, Setup removes earlier versions of Office applications.
Note: Do not add a program that requires the computer to be restarted, unless it is the last program in the list. If a custom program restarts the computer, the Office installation will be complete. However, the custom programs that appear later in this list will not run. Command-lines that are entered in the Add Program Entry and Modify Program Entry dialog boxes or by using the Command element in the Config.xml file are intended to be used only for initial product installations or uninstallations.
Office security settings Customize the security settings for Office applications. Important: Security settings specified in a Setup customization (.msp) file provide only initial default settings on users' computers. Users can change the settings after installation. To help lock down and enforce security settings, you must use Group Policy. For more information, refer to the recommendations in the 2007 Microsoft Office Security Compliance Management Toolkit (http://go.microsoft.com/fwlink/p/?LinkId=158689).
Setting Description Remove all Trusted Locations written by OCT during installation Clears the Trusted Locations list on the user's computer. Use this check box to clear the Trusted Locations list on the user's computer without adding new locations. Default Security Settings Set default security levels for add-ins, templates, and Office applications.
Setting Description code in all documents can run) Unsafe ActiveX Initialization Add-ins and templates (Project 2013 Preview only) Trust all installed add-ins and templates Do not trust installed add-ins and templates Security level (Project 2013 Preview only) Very High – Only macros installed in trusted locations will be able to run.
Modify Setup properties Modify Setup properties that are applied during the Office installation. You can customize Setup properties only when you first install Office on a user's computer. Properties set in a customization file do not take effect if you apply the file to an existing installation. To add a property, choose Add. To change a property that you have added, select the property and then choose Modify. To remove a property that you have added, select the property and then choose Remove.
Microsoft OneNote 2013 Microsoft Outlook 2013 Microsoft PowerPoint 2013 Microsoft Project 2013 Microsoft Publisher 2013 Microsoft SharePoint Designer 2013 Microsoft SharePoint Workspace 2013 Microsoft Visio 2013 Microsoft Word 2013 Some applications also provide computer settings, including the following: Microsoft InfoPath 2013 (Machine), Microsoft Office 2013 (Machine), Microsoft PowerPoint 2013 (Machine), and Microsoft Visio 2013 (Machine).
configuring the setting, choose Cancel. You can also return a setting to the Not Configured state by double-clicking the setting, selecting Not Configured, and choosing OK. Set feature installation states Customize how Office features are installed on the user's computer. To change the installation state of a feature, choose Set feature installation states in the OCT. In the results pane, open the shortcut menu (or right-click the feature), and choose the installation state.
Note: The following subcomponents of Publisher 2013 Preview are not visible in the Setup feature installation state tree in the Office 2013 Preview release: Commercial Printing and the Enhanced RGB to CMYK Conversion subcomponent Font Schemes PaperDirect Previews Publisher Templates and the Business Publications and Other Publications subcomponents The following options are also available for each feature.
Tip: The best use of the Hide setting is to simplify the feature tree for users. For example, you might hide the Office Tools branch of the feature tree so that users do not have to decide which tools they need to install. Only the tools that you select are installed. Note: If you set the Hidden option for a feature by using the OCT or the Config.xml file during an initial installation of Office 2013 Preview, you cannot unhide that feature in the feature tree by using another Config.
To create a list of files to add to the user's computer during installation, choose Add, select the file that you want to add to the list, and choose Add again. To change the destination path of a file, select the file in the Add custom files list and choose Modify. To remove a file from the list, select the file and choose Remove. You can use the SHIFT and CTRL keys to select multiple files at the same time.
Remove files Remove files from users' computers when Office is installed. To create a list of files to remove from the user's computer during installation, choose Add. To modify the path or name of a file, select the file in the Remove files list and choose Modify. To remove a file from the list, select the file and choose Remove. You can use the SHIFT key and CTRL key to select multiple files at the same time.
To create a list of registry entries to add to users' computers, choose Add. To change an entry in the list, select the entry and choose Modify. To remove an entry from the list, select the entry and choose Remove. Choose Import to add a set of entries from a registry file (.reg file). If an entry in the .reg file duplicates an entry in the list, the OCT prompts you to decide whether to overwrite existing registry entries with entries in the .reg file.
Setting Description Key Enter the name of the subkey where the entry is stored. For example, Software\Microsoft\Office\15.0\Common. Create empty key Select this check box if the registry entry does not contain a value name or value data. Some settings are determined by the presence or absence of the registry entry. Value name Enter a name for the new registry entry. If you include Value data but leave this field blank, the value is assigned the name .
Configure shortcuts Add shortcuts to files that are installed with Office 2013 Preview or files that were already on the user's computer. You can configure shortcuts only when you first install Office on a user's computer. This option is ignored if you apply the Setup customization file to an existing installation. Choose Add to add a new shortcut. To change a shortcut in the list, select the shortcut and choose Modify. To remove a shortcut from the list, select the shortcut and choose Remove.
Setting Description menu. [DesktopFolder]: Windows Desktop folder. [INSTALLLOCATION]: The folder in which Office is installed. [FavoritesFolder]: The user's Favorites folder. [AppDataFolder]: The user's Application Data folder. [NetHoodFolder]: The user's My Network Places folder. Name Enter any string to specify a name for the shortcut. Start in Enter a path to specify the default starting folder for the application.
Virtual key names and hexadecimal key codes Virtual Key Name Key Code (Hex) Description VK_0 – VK_9 30-39 Keys 0-9 VK_A – VK_Z 41-5A Keys A-Z VK_NUMPAD0 – VK_NUMPAD9 60-69 Keys 0-9 on the numeric keypad VK_F1 ...
Virtual Key Name Key Code (Hex) Description VK_HELP 2F HELP key VK_MULTIPLY 6A Multiply key VK_ADD 6B Add key VK_SEPARATOR 6C Separator key VK_SUBTRACT 6D Subtract key VK_DECIMAL 6E Decimal key VK_DIVIDE 6F Divide key VK_NUMLOCK 90 NUM LOCK key VK_SCROLL 91 SCROLL LOCK key Outlook Use the Outlook section of the OCT to customize the default Outlook 2013 Preview profile and to set Outlook 2013 Preview and Exchange Server 2010 options.
Setting Description with the second option, Outlook creates a profile that is based on the options that you choose in the other Outlook sections of the OCT. Outlook uses the default profile name or uses the profile name that you specify. New profile Create a new profile on the user’s computer and make it the default profile. Existing profiles are not removed and remain available to users. You must enter a name in the Profile name text box.
have unique names. The following table shows how Outlook determines whether a new account of the same type as an existing account can be added to the Setup customization file. Adding additional accounts Account type More than one of this type allowed? Data used to determine whether conflict exists POP3 Yes Account name IMAP Yes Account name Exchange Yes Account name Outlook Data File (.pst) Yes File name and path of .
More Exchange Server Settings Choose the More Settings button in the Exchange Settings dialog box to configure Exchange Server offline use options and the Outlook Anywhere feature. Exchange Use the following options to configure user’s Outlook profiles for offline use and Outlook Anywhere. Outlook Anywhere options Option Description Configure Outlook Anywhere Connect to Exchange Mailbox using HTTP Select this option to enable Outlook Anywhere.
Cached Mode Use the following options to configure users' Outlook profiles to use a local copy of the Exchange mailbox. Cached Mode options Option Description Do not configure Cached Exchange Mode By default, Exchange mailboxes can be accessed from the Exchange Server computer, instead of being cached on users’ computers in an offline Outlook Data File (.ost). Configure Cached Exchange Mode Create an .ost file or use an existing .ost file. Users work with a local copy of their Exchange mailbox.
Choose the Export Profile Settings button to save the Outlook profile settings that you have defined in a .prf file. Tip: An efficient way to create an Outlook .prf file is to use the OCT to make selections and then export them to a .prf file, even if you are not using a Setup customization file when you deploy Office. You can edit the .prf file to make additional customizations that are not exposed in the OCT. For example, you can add an email provider that is not listed in the OCT.
Modify Group dialog box When you change a group, select from the following options in the Modify Group dialog box and then choose OK. Select the options shown in the following table under Select options for this Send/Receive group. Send/Receive settings for the selected group Option Description Send mail items Send mail items from the Outbox when you execute a Send/Receive for this group. Receive mail items Receive mail items when you execute a Send/Receive for this group.
Rename Exchange Group dialog box Enter the new name of the Exchange send/receive group in the New Group Name box and then choose OK. Send/Receive settings for the selected group Specify settings for the Send/Receive group that is selected in the list. The name of the selected group appears in the option label. You can specify different settings for the Send/Receive group when Outlook is either online or offline.
details are not included in the offline address book. This is a legacy option that is supported by Outlook Address book (OAB) versions 2.0 and 3.0. If Outlook connects to a server that supports OAB 4.0 or a later version, the full details are downloaded even if this option is selected. Downloading updated OCT files After the initial release of Office, you can download updates of the OCT and .opax settings files from the Microsoft Download Center.
Config.xml file in Office 2013 Preview Audience: IT Professionals Administrators use the Config.xml file to perform installation and maintenance tasks for Office 2013 Preview. The primary tool that administrators use to customize the installation of Windows Installer-based products in Office 2013 Preview is the Office Customization Tool (OCT). The customization tools and methods in Office 2013 Preview are the same as for Office 2010and Office 2007.
Config.xml element quick reference The following table lists the Config.xml elements. These elements can appear in any order, except for Configuration element, which must be first, and elements such as Command element, whose order in Config.xml affects how they are processed during installation. Config.
Element Description SetupUpdates element The search path for Setup to use to find Setup customization files USERINITIALS element The initials of the user on whose computer the product is being installed USERNAME element The name of the user on whose computer the product is being installed How Setup uses Config.xml Setup looks for a copy of Config.xml in the same folder as Setup.exe. If a copy is not found there, Setup uses the Config.
AcceptEula="yes" /> Tip: For long element definitions, put attributes on separate lines and use indentation to make the file easier to read. The Configuration element is a special case and is required. All other elements are contained in the Configuration element, and the element is closed with , as shown in the following example.
The Display options in the previous example direct Setup to run a silent installation, to prevent users from being prompted to enter information, and to prevent the installation from waiting for any user interaction. Config.xml element reference The following conventions are used in the descriptions in this reference.
Remarks The Product attribute identifies the product affected by this Config.xml file. The productID is defined in the Setup.xml file that is located in the core folder for the product, in the ID attribute of the Setup element. The Product attribute is optional, unless you set the Display element Level attribute to “basic” or “none”. In this case, the Product attribute is required.
Attribute Value Description AddLanguage element is specified, one (and only one) language must specify the ShellTransform element. Remarks The language must be available on the network installation point. You can have multiple elements for AddLanguage and RemoveLanguage element. If both the RemoveLanguage element and the AddLanguage element specify the same language, the AddLanguage element takes precedence and the language is installed.
In the previous example, Setup installs all the specified languages and the Shell UI matches the language of the user's locale. If more languages were available in the source image, the match value in the previous example might install an additional language if the match language does not resolve to one of the other four explicitly called-out languages.
Attribute Value Description No (default) Allows users to remove the product. ARPURLINFOABOUT URL URL for the product's home page. ARPURLUPDATEINFO URL URL for information about product updates. ARPHELPLINK URL URL of a website where users can receive technical support. ARPHELPTELEPHONE text Telephone numbers for technical support. Command element Specifies a command line to run. For more information, see Remarks later in this article.
Command attributes Attribute Value Description Path path Fully qualified path of the executable file. If the path value contains a space, you must use double quotation marks as shown in the following example: "\\server\share\Office 14\copylogs.bat" QuietArg string String of arguments to be appended to the command line if you configure a silent installation. For more information about when to use the QuietArg attribute, see the Remarks section that follows this table.
Attribute Value Description x86 platform. This command runs only if the computer on which the installation is run matches this platform requirement. x64 Specifies that this program requires a 64-bit processor that supports the x64 extensions to the x86 architecture. This command runs only if the computer on which the installation is run matches this platform requirement. Remarks The Command element in the Config.
Setting the Wait attribute to 0 milliseconds indicates no waiting after you run the program before you continue the installation. The command will execute and move on immediately. Return codes are only respected if the Wait value is nonzero. If you specify 0, Setup will not wait to continue the installation after it runs the specified program. Therefore,, there is no return code to report in that case.
Example Display element The level of UI that Setup displays to the user. Tip: The equivalent option in the OCT is the Display level and license agreement settings in “Licensing and user interface” in Office Customization Tool (OCT) in Office 2013 Preview.
Attribute Value Description the completion notice. SuppressModal NoCancel AcceptEULA No (default) Only applies if Level is set to "basic": Setup does not display the completion notice. Yes Only applies if Level is set to "basic": Setup does not display error messages and other dialog boxes that might interrupt the installation. No (default) Only applies if Level is set to ”basic”: Setup displays errors and other dialog boxes as needed.
Administrators must also make sure that no Office applications run during an installation of the Office 2013 Preview. If you set the Display Level value to “basic” and SuppressModal to “yes”, users might be prompted if any Office files are being used. Setting Display Level to “none” prevents prompting users in these cases. The SuppressModal attribute does not prevent files in use messages from being displayed. Only if Display Level is set to “none” are files in use messages prevented from being displayed.
Example INSTALLLOCATION element Specifies the fully qualified path of the folder on the user's computer where the product is installed. Tip: The equivalent option in the OCT is the Default installation path setting in Installation location and organization name. Syntax Attributes The following table describes INSTALLLOCATION element attributes and values.
/> Attributes The following table describes LIS element attributes and values. LIS attributes Attribute Value Description CACHEACTION CacheOnly Setup copies the LIS to the user's computer, but does not install the product. Note: Do not use Command elements in a Config.xml file that specifies the CacheOnly value because the specified commands will not run.
If you specify INSTALLLOCATION element, the drive designation in the path is used to determine on what drive the LIS is created. For example, if the INSTALLLOCATION element path is E:\office\files, the LIS is created on drive E. The sources listed by the SOURCELIST attribute are kept with the installed product and are used by Setup if the LIS on the user's computer is missing or corrupted.
Attribute Value Description that is specified already exists, log information is appended to the existing file. The .txt file name extension must be included. The default template is SetupExe(*).log. Remarks You can specify a * anywhere in the Template value. Setup inserts a string in that location that has the following format. YYYYMMDDHHMMSSxxx where: 1. YYYY = Year 2. MM = Month 3. DD = Day 4. HH = Hour 5. MM = Minute 6. SS = Seconds 7.
Important: In most situations, we recommend that you use the OCT to change the installation state of features. The equivalent option in the OCT is Set feature installation states. Syntax Attributes The following table describes OptionState element attributes and values. OptionState attributes Attribute Value Description Id optionID An item that the user can choose to install.
Publisher Templates and the Business Publications and Other Publications subcomponents Example PIDKEY element The 25-character volume license key. Note: The equivalent option in the OCT is the Product key setting in Licensing and user interface in Office Customization Tool (OCT) in Office 2013 Preview. For more information about volume licensing in Office Professional 2013 Preview, see Plan volume activation of Office 2013 Preview.
Attributes The following table describes PIDKEY element attributes and values. PIDKEY attributes Attribute Value Description Value 25-character-key The 25-character volume license key. Remarks When the PIDKEY value is set, users are not required to enter a product key when they install Office. To enter a MAK key in the Config.xml file, add the following line to the file. Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key.
RemoveLanguage attributes Attribute Value Description Id ll-cc The language identifier. Remarks If the language is not installed on the user's computer, the RemoveLanguage element is ignored. You can have multiple elements for AddLanguage element and RemoveLanguage. If both RemoveLanguage and AddLanguage element elements specify the same language, the AddLanguage element element takes precedence and the language is installed.
Remarks Not all Windows Installer properties can be specified in the Setting element. If a blocked property is specified, Setup ends the installation process. If a supported property is specified, Setup passes the property directly to Windows Installer. The Setting element supports the following Key Management System (KMS) properties: KMSSERVICENAME — Specifies the KMS host name. KMSSERVICEPORT — Specifies the KMS host port.
3. In the Value box, type 1, and then click OK. The Setting element supports the REMOVEPREVIOUS property. This property removes the specified application from the installation and uses the following syntax. where Option Id is the identifier value for the Office 2013 Preview application. To specify multiple applications, use a comma-separated list to indicate the appropriate Option Id values.
Attributes The following table describes SetupUpdates element attributes and values. SetupUpdates attributes Attribute Value Description CheckForSUpdates Yes (default) Setup uses the path list in SUpdateLocation to find Setup customization files. No Setup does not search for Setup customization files by using the path list in SUpdateLocation. path-list A list of fully qualified paths to folders, separated by semicolons.
Syntax Attributes The following table describes USERINITIALS element attributes and values. USERINITIALS attributes Attribute Value Description Value value The user's initials Example USERNAME element The name of the user on whose computer the product is being installed. Syntax Attributes The following table describes USERNAME element attributes and values.
If the user who is running Office is not the same user who installed Office, Office prompts the user to confirm his or her Username and Initials when Office first starts. This case is most popular in a corporate environment, where an administrator installs Office for the user. The value for the Username element shown to the user at first start time might be pre-populated with a default value from a previously installed version of Office or from the currently logged-on user.
Setup command-line options for Office 2013 Preview Audience: IT Professionals The Setup.exe command line is used for very few operations in Office 2013 Preview (just as in Office 2010 and Microsoft Office 2007). Setup recognizes the command-line options that are described in this article.
being installed and applies the file during the installation. The Updates folder can only be used to deploy software updates during an initial installation of Office 2013 Preview. If you store more than one customization file per product in the Updates folder, Setup applies all the files to the installation.
/repair [ProductID] Runs Setup to repair the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify. Example \\server\share\Office15\setup.exe /repair ProPlus where: Office15 is the root of the network installation point. ProPlus is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in \\server\share\Office15\ProPlus.WW\setup.xml), where ProPlus.
ProPlus is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in \\server\share\Office15\ProPlus.WW\setup.xml), where ProPlus.WW is the location of the Office Professional Plus 2013 Preview installation files. You can customize the /uninstall option by using it with /config and a modified Config.xml file. This is necessary if you want to run a “silent” uninstall.
Customize the Accessibility Checker for Office 2013 Preview The Accessibility Checker in Office 2013 Preview lets users create more accessible documents for people who have disabilities. The Accessibility Checker (like a spelling checker, but for accessibility issues) is a core feature of Excel 2013 Preview, PowerPoint 2013 Preview, and Word 2013 Preview.
Group Policy settings for Excel 2013 Preview Setting for Excel 2013 Preview Associated registry key Description Stop checking for alt text accessibility information AltText If enabled, the Accessibility Checker does not determine whether objects such as images and shapes contain alternative text. If disabled or not configured, objects are checked for alternative text and any issues that it finds will appear in the Accessibility Checker.
Setting for Excel 2013 Preview Associated registry key Description whether tables have merged cells. If disabled or not configured, worksheets are checked for merged cells and any issues that it finds will appear in the Accessibility Checker. Stop checking to ensure hyperlink text is meaningful MeaningfulHyperlinks If enabled, the Accessibility Checker does not check whether hyperlinks have meaningful text.
Group Policy settings for PowerPoint 2013 Preview Setting for PowerPoint 2013 Associated registry key Preview Description Stop checking for alt text accessibility information If enabled, the Accessibility Checker does not determine whether objects such as images and shapes contain alt text. AltText If disabled or not configured, objects are checked for alternative text and any issues that it finds will appear in the Accessibility Checker.
Setting for PowerPoint 2013 Associated registry key Preview Description configured, tables are checked for header rows and any issues that it finds will appear in the Accessibility Checker. Stop checking for blank table rows and columns BlankRowCol If enabled, the Accessibility Checker does not determine whether blank rows and blank columns were inserted into tables.
Setting for PowerPoint 2013 Associated registry key Preview Description sure that each slide has a unique title Accessibility Checker does not determine whether every slide has a unique title. If disabled or not configured, slide titles are checked for uniqueness and any issues that it finds will appear in the Accessibility Checker.
Group Policy settings for Word 2013 Preview Setting for Word 2013 Preview Associated registry key Description Stop checking for alt text accessibility information AltText If enabled, the Accessibility Checker does not determine whether objects such as images and shapes contain alt text. If disabled or not configured, objects are checked for alternative text and any issues that it finds will appear in the Accessibility Checker.
Setting for Word 2013 Preview Associated registry key Description Stop checking for merged and split cells 2DTableStructure If enabled, the Accessibility Checker does not determine whether tables have merged or split cells. If disabled or not configured, tables are checked for merged and split cells and any issues that it finds will appear in the Accessibility Checker.
Setting for Word 2013 Preview Associated registry key Description succinct. If disabled or not configured, document headings are checked for length and any issues that it finds will appear in the Accessibility Checker. Stop checking whether objects are floating FloatingObjects If enabled, the Accessibility Checker does not check whether a document has objects that are floating instead of inline.
Setting for Word 2013 Preview Associated registry key Description issues that it finds will appear in the Accessibility Checker. Stop checking for tables used for layout LayoutTablesReadingOrder If enabled, the Accessibility Checker does not flag layout tables (that is, tables that have no style applied). If disabled or not configured, tables that have no styles are flagged and violations appear in the Accessibility Checker.
Roll out Office 2013 Preview Audience: IT Professionals The following table lists and describes articles that will help you deploy Office 2013 Preview. Articles about rolling out Office 2013 Preview Article Description Setup architecture overview for Office 2013 Preview Provides information about the Windows Installerbased Office 2013 Preview Setup architecture.
Setup architecture overview for Office 2013 Preview Audience: IT Professionals The Setup architecture in Office 2013 Preview, introduced in Microsoft Office 2007, streamlines all aspects of installing, customizing, and maintaining Office. The Setup program unifies and manages the complete installation process. This includes customizing users' Office configuration, deploying multiple languages at the same time, and applying software updates to new installations.
Consolidated update process Setup process Typically, the first step in a corporate installation of Office is to create a network installation point, a task as easy as copying all files and folders from the Office product CD to a shared network location. At a minimum, the network installation point contains the language-neutral core package plus languagespecific folders for one language. This installation point serves as the initial source for all users who install Office.
You can circumvent the selection process and determine which Office product is installed by pointing Setup.exe to the Config.xml file in a core product folder. For example, if you want to install Office Professional Plus 2013 Preview, you can use the following command line: \\server\share\Office15ProPlus\setup.exe /config \\server\share \Office15ProPlus\Pro.WW\Config.xml where Office15ProPlus is the root of the network installation point. In versions of Office earlier than Office 2007, Setup.
Read XML data Setup collects information about each package on the installation point, collects default settings for the installation, and incorporates customizations that you specify. Setup collects all this information in the form of XML data from several sources: Setup.xml and Package.xml files for each package Each folder on the installation point — both the folder for the language-neutral core package and the folder for each language-specific package — contains a Setup.xml and a Package.
.msp file for Visio Professional 2013 Preview in the Updates folder. The customization .msp files that you place in the Updates folder will be deployed first. Therefore, they must include any Setup customizations that cannot be changed after the installation, for example, the installation location.
Users who apply software updates are less likely to be prompted for a network or CD source because an installation source is available locally. You can deploy the local installation source in advance and trigger the installation of Office on users' computers later to reduce the load on the network. In this scenario, you can even run Setup from the local installation source. This lets users complete the Office installation without using a network connection.
Note: When you precache the local installation source, Setup copies the Updates folder from the network installation point to the local installation source. In this manner, your customizations can be included in offline installation scenarios. This is the only circumstance in which Setup caches the customization file on the local computer before the installation. For more information, see Precache the local installation source for Office 2010. The information also applies to Office 2013 Preview.
Running Setup interactively You can choose to run the installation quietly so that users see little or none of the process. However, if you let users view the Setup user interface, the choices that you make affect several aspects of Setup behavior. For example: If more than one Office product is available on the installation point and a user runs Setup.exe without command-line options, Setup gives the user a choice of products to install.
Language versions of Office Every Office product must include at least one set of language-specific packages. You cannot deploy just the core package (MSI file) by itself. On the Office product CD and the network installation point, these language packages are contained in folders. Each folder name includes a language tag, in the form ll-cc (for example, en-us for English U.S.), that identifies the language. Each folder also contains a set of installation files.
not identical to the core version with a Japanese MUI pack. This design was simplified and improved in Office 2007 and is the same in Office 2013 Preview and Office 2010. Streamlined customization model In versions of Office earlier than Office 2007, several tools were required to customize Setup and to manage Office after installation. Office 2007 introduced a consistent, streamlined model.
Note: We recommend that enterprise customers first uninstall any earlier versions of Office before they install Windows Installer-based Volume License editions of Office 2013 Preview. Determine which Office features are installed. Specify the default values for many user options, including Outlook settings. Note: Office 2013 Preview does not support side-by-side installations of 64-bit and 32-bit Office, including across applications.
Making last-minute or one-off customizations that do not warrant running the OCT to create a new customization file. If you put the Config.xml file in the same folder as Setup.exe, Setup finds and uses the file. You can also specify the location of the file by using the /config Setup command-line option. Note: If you specify both a Setup customization file and the Config.xml file, the customizations that you define in Config.xml take precedence over the same customizations in the customization file.
Menu commands and their corresponding toolbar buttons Shortcut keys Most options in the Options dialog box Note: Most of the Office 2013 Preview policy settings are also available in the OCT (OPA settings). To configure initial default settings in a Setup customization .msp file, administrators can use the OCT. However, users can change most of the settings after the installation. Use Group Policy if you want to enforce specific configurations.
Creating a local installation source on users' computers When users install Office from a DVD or from a network installation point, Setup creates the local installation source by using a program called the Office Source Engine (Ose.exe) to copy required installation files to a hidden folder on the local computer. The default location is \MSOCache\All Users at the root of the drive on which Office is installed.
Setup from a specific folder installs that product. This method lets users install Office without relying on a network connection. For more information, see Install Office 2010 from local installation source.
Updating existing Office installations After Office is installed, you apply software updates directly to the client computer without returning to the network installation point. You do this through a deployment management program such as Microsoft Systems Management Server or System Center 2012 Configuration Manager, by using Windows Server Update Services, or by updating computers directly from the Internet by using Microsoft Update.
Language in Office 2013 Preview Audience: IT Professionals The following table lists and describes articles that will help you Configure Office 2013 Preview to work with multiple languages.
Security in Office 2013 Preview Audience: IT Professionals New security controls are available in Office 2013 to help you plan a robust defense against threats while maintaining information worker productivity. An organization's success often depends on the productivity of its information workers and the integrity and confidentiality of its intellectual property. Many IT departments find it difficult to satisfy these business needs because protection often comes at the expense of productivity.
Virtualize Office 2013 Preview Audience: IT Professionals You can deploy Office 2013 Preview by using virtualization technologies, such as Microsoft Application Virtualization (App-V) or Remote Desktop Services (formerly known as Terminal Services). App-V enables you to run Office 2013 Preview in a self-contained environment on an end-user computer.
Group Policy for Office 2013 Preview Audience: IT Professionals Group Policy is an infrastructure that is used to deliver and apply one or more desired configurations or policy settings to a set of targeted users and computers in an Active Directory directory service environment. When you have Office 2013 Preview installed, you can use Group Policy to: Control entry points to the Internet from Office 2013 Preview applications. Manage security in the Office 2013 Preview applications.
Outlook 2013 Preview Audience: IT Professionals To plan an Outlook deployment or configure Outlook Anywhere, Cached Exchange Mode, and security and protection features, or to customize Outlook profiles, follow the steps that are described in these articles.
