How OEM partners can develop Windows Live installation scenarios by taking advantage of the Windows Live Installer
On This PageSUMMARYThis document defines how Microsoft partners can create installation scenarios by taking advantage of the Windows Live Installer. This document covers the following scenarios:
MORE INFORMATIONDescription of each application
RequirementsDepending on the type of installation and components that you are installing, certain prerequisites may be required on the computer for the programs to function correctly. In the online installation process, the presence of these prerequisites is checked by the installer. Additionally, the prerequisites are downloaded if they are not present. This mechanism is bypassed in the offline installation process. Therefore, you must install the prerequisites.
Installation scenariosOEM package installation without a configuration fileYou can call the installer as follows:WLSetup.exe /silent In this scenario, without a configuration file all products EXCEPT Windows Live Family Safety will be installed on the computer.OEM package installation with a configuration fileYou can use the following command-line parameter to install specific Windows Live Products that are defined in the configuration file:WLSetup.exe /silent /configfile: config.txt To do this, use the example configuration .txt file (4.3).
Verbose or silent Installation without a configuration fileYou can set the Windows Live installer to install without a configuration file. In this scenario, regardless of whether you run the installation from the Web, a CD, or UNC share, the installation will run. All the selected products will be installed.Verbose By using the Windows Live Installer User Experience, you can take advantage of the Windows Live Installer User Experience. By default the Family Safety Settings will not be selected. However, you can add them in the “upsell” selection. For an example of this scenario, see the WLSetup.exe/configfile: config.txt configuration file. Note This scenario works on CD, from the Web, or from a local network (UNC) share. SilentYou can use your own User Experience to decide whether to create your own user experience for the installation. In this scenario, the Windows Live Installer can be programmatically run in “Silent” mode. The Windows Live Installer determines what to install based on what is “included” in the Windows Live Installer package. If all the MSIs are bundled in the OEM package, all the Windows Live products are installed on the computer, except FSS. For an example of this scenario, see WLSetup.exe /silent/configfile: config.txt configuration file. Notes This scenario will work on a CD, from the Web, or from a local network (UNC) share. For dependencies, you can rely on the Web connection to install dependencies, or you can include them and install them separately from the Windows Live Installer. Verbose or silent with configuration fileYou can configure the Windows Live Installer to install many different products by using a customizable configuration file. For more information, see 4.1. You can use this custom configuration file from the Web, from a CD, or from a local share (UNC). In the custom configuration file, you can specifically select the products that you want to install.Verbose You can select the specific products that you want to install by using the Windows Live Installer and configuration file, taking advantage of the Windows Live Installer’s User Experience with a configuration file. For an example of this scenario, see WLSetup.exe /configfile: config.txt configuration file. Silent Use your User Experience and a configuration file to take advantage of the Windows Live Installer and make it completely customizable. To do this, call the Windows Live Installer and include a configuration file. For an example of this scenario, see WLSetup.exe /silent /configfile: config.txt configuration file. Notes In the Web scenario where a configuration file is used, you must create a wrapper .exe file that contains the config file to start the installer with the correct set of command-line parameters. We will not support this scenario for Wave 2. However, you can perform this scenario if you have to.
In the Verbose scenario where a configuration file is used, the end-users running through the installation experience will see the Upsell text for any products that are not part of the configuration file. The only way for you to lock the list of products that you will install is in “/silent” mode. In the Silent scenario, you must provide your own User Experience. Command-line parametersThe following is a list of command-line parameters that can be used together with the OEM installation configuration file.
Product listThe product list is identified by “p=” and also includes “*0” or “*1” for the priority of each application (0>1). This product list is comma separated.Example: P=5A3D-4E68-82A1-3C166F03C379*0,88459F2D-0CF8-4558-B6AB-6E19B6AC34B0*0 Set MSN searchTo set MSN as the default search engine, set “s=1”. If you do not want MSN as the default search engine, set “s=0”. If you leave “s” out of the config file, you will be prompted to set Live Search as your default, unless you are running silently. In silent mode, there is no UI/no change to search.Set MSN homeTo set MSN as the home page, set “h=1”. If you do not want MSN as the default home page, set “h=0”.Enable CEIPTo enable the CEIP program, set “c=1”. To not enable CEIP set “c=0”.Note Some OEM developers can be contractually obligated to have this pre-selected. Market settings To set the market, include “m=<lang>-<market>.” For example, type m=EN-US. The market setting follows the standard <language> <market> format. Terms of Use (TOU)You can configure whether the installer displays the TOU during the verbose installation.
Product upgrade codes
Example of the Config.txt fileIn this example, you are performing the following tasks:
p=31BB3B1C-5A3D-4E68-82A1-3C166F03C379*0,88459F2D-0CF8-4558-B6AB-6E19B6AC34B0*0,A26D7C8B-875D-48E2-BED1-7168268D022A*0,F81F501C-236B-4B4A-8E92-0575EAAD06FA*0,5DC07600-AAF3-11DA-A746-0800200C9A66*0,BB05EE9A-31CE-44F7-B0B3-1A341A8DFFCD*0,C41BA0D7-8DCB-4789-8B6C-543EE4C37142*0&s=1&h=1&c=1&m=EN-US&t=0 Windows Live OEM installation packageThis is a multiple language link to the Windows Live OEM installation package. The download location will automatically redirect to the download location of the language of your browser. To change languages, select the appropriate language from the drop-down menu.To do this, visit the appropriate Web site.
Additional information1.1.1.1 INSTALL_SUCCESS
S_OK = 0 1.1.1.2 INSTALL_FAILURE
FAILED(hResult) == 1 1.1.1.3 ERROR_SUCCESS_REBOOT_REQUIRED
ERROR_SUCCESS_REBOOT_REQUIRED = 3010 APPLIES TO
| Article Translations
|
Back to the top
