Planning for the Custom Package Creation on Windows Computers

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

Use the following checklist before creating the custom 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. 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 custom package, determine whether the computers use a 32-bit or 64-bit processor. You can configure the custom package to support 32-bit and 64-bit binaries.

Select the Commvault instance

Determine which instance should the custom package 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 custom package installation.

Determine the custom package directory

By default, the custom package is created in C:\CustomInstallPackageName.

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 custom package

Determine the data that you want to protect in your organization. For example, if you want to protect Microsoft SQL databases, you need to include the SQL Server Agent in the custom package.

Display to User: Users can select the agents to install during the custom package installation. The agents displayed to the users will be based on the agents you selected. If you want the package to install the agents automatically, do not display the agents to users.

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	When to use the option
Include MS SQL Server	Adds the Microsoft SQL Server software to the custom package.	You included server packages to the custom package, such as the Web Server and Workflow Engine. Server packages use the SQL Server to create database instances, which coordinate the server operations within the CommCell environment.
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	When to use the option
Create answer file (without packages)	Creates the custom 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 a custom 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 custom package with the software you selected.
Create a de-coupled installation package	Configures the custom 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.	You can use this option in the following scenarios: You want to install the package on computers that do not have open connections with the CommServe computer. You want to preinstall the software as part of the computer's factory settings. This is useful if you want to ship the computers to users as a software appliance. The option is not supported in the following scenarios: If the computer where you want to install the package is in a clustered environment. If you included the CommServe, Web server, Web Console, or Search Engine in the custom package.
Launch Edge Monitor at the end of install	Opens the Edge Monitor application automatically at the end of the custom package installation. This application allows you to register the client, on which you installed the package, with the CommServe computer.	You want to register the client immediately after the package installation. If you plan to register the client at a later time, do not use this option.
Repair if existing instance found	Repairs existing installations of the Commvault software. Requirements: The software that you include in the custom package must match the software that is installed on the client to be fixed. The CommServe name that you specify in the custom 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 custom package recreates missing or deleted Commvault registries while preserving the existing ones. Service corruption The custom package reconfigures Commvault services that were deleted or that were not configured properly. Installation file corruption The custom package recreates missing or corrupt installation files.

Option

Description

When to use the option

Create answer file (without packages)

Creates the custom 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 a custom 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 custom package with the software you selected.

Create a de-coupled installation package

Configures the custom 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.

You can use this option in the following scenarios:

You want to install the package on computers that do not have open connections with the CommServe computer.
You want to preinstall the software as part of the computer's factory settings. This is useful if you want to ship the computers to users as a software appliance.

The option is not supported in the following scenarios:
If the computer where you want to install the package is in a clustered environment.
If you included the CommServe, Web server, Web Console, or Search Engine in the custom package.

Launch Edge Monitor at the end of install

Opens the Edge Monitor application automatically at the end of the custom package installation.

This application allows you to register the client, on which you installed the package, with the CommServe computer.

You want to register the client immediately after the package installation.

If you plan to register the client at a later time, do not use this option.

Repair if existing instance found

Repairs existing installations of the Commvault software.

Requirements:

The software that you include in the custom package must match the software that is installed on the client to be fixed.
The CommServe name that you specify in the custom 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 custom package recreates missing or deleted Commvault registries while preserving the existing ones.
Service corruption

The custom package reconfigures Commvault services that were deleted or that were not configured properly.
Installation file corruption

The custom package recreates missing or corrupt installation files.

Gather installation data for CommCell options

This information is applicable only if you plan to save your answers (or selections) during the custom 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)
Destination folder for the software installation
Firewall services

Important: To configure firewall settings during the custom 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.

Gather installation data for agent specific options

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

During package creation, the installation wizard requests additional information for some of the agents that you chose to include in the custom package.

To gather the data, go to the preinstallation checklist page for your agents. Then, on the preinstallation checklist page, read the Gather Installation Data section. If you only see information related to the package name and client computer details, then no additional information is required for the agent.

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