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.xml file (for example, ProPlusWW.xml for Office Professional Plus 2013 Preview). Information in these files enables Setup to do the following:

Identify a product and the available languages for that product.

Match language-neutral and language-specific elements to create complete features.

Build a consolidated feature tree.

Collect the set of MSI files that are required for the installation.

Note:

The Setup.xml and Package.xml files are signed and cannot be changed. Altering these files causes Setup to fail.

Setup customization file Early in the installation process, Setup determines whether you have specified a Setup customization file (.msp file) for the product that is being installed. A Setup customization .msp file is created when administrators use the Office Customization Tool (OCT) to customize an installation of Office 2013 Preview. The OCT is part of the Setup program and is the recommended tool for most customizations. The customization file contains all the modifications that you specify for an installation. This includes customizations that control the installation process. The OCT is available in volume licensed versions of Office 2013 Preview, Office 2010, and Office 2007. To determine whether your Office 2013 Preview installation is a volume licensed version, check the Office 2013 Preview installation disk to see whether it contains a folder that is named Admin. If the Admin folder exists, the disk is a volume license edition; otherwise, the disk is a retail edition.

If no customization file is specified on the command line or in the Config.xml file, Setup searches the Updates folder on the installation point for a customization file that is specific to the product that is being installed. By default, the Updates folder is included on the installation point. In most cases, it is the recommended location in which to store both a Setup customization .msp file and software updates for all the Office products included on the installation point.

Important:

If you plan to deploy multiple Setup customization files (.msp files), you can place only one customization .msp file in the Updates folder for each Office 2013 Preview product that you are installing during the initial installation. Only one Setup customization .msp file (patch) for each Office 2013 Preview product that you are installing is supported in the Updates folder. You must deploy the rest of the customization .msp files for a product after the first Office installation is completed.

If you are deploying multiple Office 2013 Preview products, such as Office Professional Plus 2013 Preview and Visio Professional 2013 Preview, you can include one customization .msp file for Office Professional Plus 2013 Preview and one customization

104

Page 113
Image 113
Microsoft 79G-03775, T5D01575 manual Read XML data