Planning for the Application Seed Package Creation on Windows Computers

Before you run the installation wizard, you must collect the information that is required during the application seed package creation.

Use the following checklist before creating the application seed package. Record the information so you can refer to it during the package creation.

Note

You can make certain options available to users during the package installation. The options that can be made available have the Display to User note shown below. To install the package with minimal user interaction, provide all the necessary information during the package creation.

Determine the Type of Windows Processor

On the computers where you plan to install the application seed package, determine whether the computers use a 32-bit or 64-bit processor. You can configure the application seed package to support 32-bit and 64-bit binaries.

Select the Commvault Instance

Determine which instance that the application seed package should use during installation. You can configure the package to use an existing instance or to create a new one.

If you select an existing instance, the instance must exist on the computers where you plan to install the package.

Note

During the package installation, if the selected instance is not detected, the package creates the instance and then installs the software on the new instance.
If you create a new instance, the package installs the software on a new instance, irrespective of the existence of other instances on the computers.

Display to User: Users can select the instance during the application seed package installation.

Determine the Application Seed Package Directory

By default, the application seed package is created in C:\CustomPackageLocation.

You can change the location where the folder resides. If the folder you plan to use does not exist, it is automatically created during the package creation.

Decide Which Agents to Include in the Application Seed Package

Select only the Windows > File System Core package.

Decide Which Custom Package Options to Set

The installation wizard provides a set of advanced options to configure the custom package. The following table provides information about each option.

Note

Notify users about the type of configurations that you plan to use for the package. For example, if you configure the package for decoupled installation, the client must be registered with the CommServe after the installation.

Option	Description	Notes
Include ThirdParty packages	Adds third party packages to the application seed package.	Only deselect this option if you know the third-party packages required by the features that were selected in the previous screen.
Include .NET Framework 4.0 Installer	If any of the agents that you selected requires .NET Framework 4.0, the installation wizard automatically adds the .NET software to the custom package.	The computers where you plan to install the custom package do not have .NET Framework 4.0 installed.
Create self-extracting executable	Creates the custom package as a self-extracting executable file, which automatically starts the installation when the file is run.	You can use this option in the following scenarios: To simplify the installation for end-users, as they only need to run the executable file to start the installation. To easily upload the executable file to a site for the end-user to retrieve. You can also run the executable file in silent mode.
Save user answers in the custom package	Creates an answer file, which stores the selections that you make during the custom package creation. If you choose not to save your selections, the package uses the default installation settings for all CommCell and agent specific options. Also, you can configure the package to display the options to users during the installation.	You can use this option in the following scenarios: You want to customize the package with specific options that satisfy your environment requirements. You want to enable users to make their own selections during the package installation. To accomplish this, you must display the options that you want users to answer. You want to perform unattended installations by using the answer file. To accomplish this, you must provide the answers for all the options, and must not display options to users. Tip As a security measure, if the CommCell is configured to authenticate client installations, do not provide your user account during the custom package creation. The account information will be recorded in the answer file. Instead, create a separate CommCell user with the required permissions so that it can be used during the package creation.

If you choose to save user answers in the custom package, the following options become available:

Option	Description	Notes
Create answer file (without packages)	Creates the application seed package with only the answer file, which stores the selections that you make during the custom package creation. No other files are included in the package, such as binaries, updates and executables.	You can use this option in the following scenarios: You want to create a sample answer file which you can later edit with your preferences. You already created an application seed package, and you want to generate a new answer file with different selections. Remember to install the software using the answer file, you must have an installation package or a separate application seed package with the software you selected.
Create a de-coupled installation package	Configures the application seed package to skip the client registration with the CommServe computer. During the installation, the client will not establish any connections with the CommServe computer. Remember: The client must be registered after the installation.	Do not use this option.
Launch RegisterMe at the end of install	Opens the Register Me application automatically at the end of the application seed package installation. This application helps you register the client, on which you installed the package, with the CommServe computer.	You want to register the client immediately after the package installation. This option is automatically selected when you select Create a de-coupled installation package. If you plan to register the client at a later time, do not use this option.
Cleanup existing instance	Repairs existing installations of the Commvault software. Requirements: The software that you include in the application seed package must match the software that is installed on the client to be fixed. The CommServe name that you specify in the application seed package must match the CommServe name configured in the client to be fixed.	You can use this option to solve the following issues on client computers: Registry corruption The application seed package recreates missing or deleted Commvault registries while preserving the existing ones. Service corruption The application seed package reconfigures Commvault services that were deleted or that were not configured properly. Installation file corruption The application seed package recreates missing or corrupt installation files.
Launch Roles Manager at the end of install	Allows the user to select roles to install.	For more information, see Packages that are Supported by Roles Manager to Install.

Gather Installation Data for CommCell Options

This information is applicable only if you plan to save your answers (or selections) during the application seed package creation.

During package creation, the installation wizard requests information related to the CommCell environment, which includes the following items:

CommServe name

Note

If you configure the custom package to install the software in decoupled mode, the package will not communicate with the CommServe computer during the installation.
Client groups
Configure for laptop backup (applicable if only the File System Core is selected).

Note

Do not select this option.
Destination folder for the software installation
Firewall services

Important

To configure firewall settings during the application seed package creation, the computer where you create the package must have a Commvault instance installed with direct communication or proper firewall settings to communicate with the CommServe computer.
Subclient and storage policy
Windows Firewall for Computer Profiles

For more information on the above items, see the Gather Installation Data section in Preinstallation Checklist for the Windows File System Agent.

Display to User: Users can select CommCell options during the custom package installation.