Windows: Creating a Custom Package for Windows Computers Using the Download Manager

You can use the Download Manager to create a custom package with the agents and options required for your Windows computers.

Custom packages are commonly created from the installation package that is generated when you download software from the Download Manager. Creating a custom package directly from the Download Manager removes the prerequisite to download the software.

Before You Begin

Obtain the latest Download Manager from the Cloud Services website or the Maintenance Advantage website. The application is supported on 32-bit and 64-bit Windows computers.

For more information, see Downloading Installation Media.
Collect the information required during the custom package creation.

For more information, see Planning for the Custom Package Creation on Windows Computers document. This is the same planning document used during thee custom package creation from the installation package.

Procedure

Start the Download Manager application, select where to extract the installation files, and then click Extract.

The installation wizard opens.
On the welcome page, select the I Agree check box and then proceed to the next page.
On the Choose the Installation Type page, click Download packages to install on a different computer and then proceed to the next page.
On the Select Operating System Type page, select the type of Windows processor that your computers support, and then proceed to the next page.
On the Custom Package Install Type page, select one of the following options and then proceed to the next page:

Option	Description
New Installations	Use this option in the following scenarios: You plan to install the Commvault software on new clients. You plan to perform a hardware refresh. The Download Manager downloads all the required installation files and feature release updates. For Commvault packages that need the SQL Server software, the Download Manager will retrieve Microsoft SQL Server 2019 Standard Edition. Note If you are using Download Manager to download Commvault media with MS SQL Server 2016 onto a computer with an internet connection, and that media needs to be installed on a CommServe computer running Windows Server 2012 or Windows Server 2012 R2 computer, you must download Microsoft SQL Server 2016, which is compatible with those operating systems (MS SQL Server 2019 is not compatible with Windows Server 2012 or Windows Server 2012 R2). You can use the bDownloadSQL2016 registry key on the downloading computer to download Commvault media with MS SQL Server 2016, instead of Commvault media with MS SQL Server 2019. For more information, see the Troubleshooting article "Download Microsoft SQL Server 2016 Instead of Microsoft SQL Server 2019 Using Download Manager".
Upgrade from V9 or V10	Use this option if you plan to upgrade clients from previous Commvault versions. For example, upgrades from Version 10 to Version 11. For Commvault packages that use the SQL Server software, the Download Manager will retrieve Microsoft SQL Server 2012 Enterprise. This SQL version is needed to upgrade clients that have SQL Server 2008 Enterprise (or earlier versions).
Feature Release Upgrade	Use this option if you plan to install feature release updates or additional agents on an existing client. Note If you plan to install Commvault packages that need the Microsoft SQL Server (such as the CommServe), select New Installations.

Option

Description

New Installations

Use this option in the following scenarios:

You plan to install the Commvault software on new clients.
You plan to perform a hardware refresh.

The Download Manager downloads all the required installation files and feature release updates. For Commvault packages that need the SQL Server software, the Download Manager will retrieve Microsoft SQL Server 2019 Standard Edition.

Note

If you are using Download Manager to download Commvault media with MS SQL Server 2016 onto a computer with an internet connection, and that media needs to be installed on a CommServe computer running Windows Server 2012 or Windows Server 2012 R2 computer, you must download Microsoft SQL Server 2016, which is compatible with those operating systems (MS SQL Server 2019 is not compatible with Windows Server 2012 or Windows Server 2012 R2).

You can use the bDownloadSQL2016 registry key on the downloading computer to download Commvault media with MS SQL Server 2016, instead of Commvault media with MS SQL Server 2019.

For more information, see the Troubleshooting article "Download Microsoft SQL Server 2016 Instead of Microsoft SQL Server 2019 Using Download Manager".

Upgrade from V9 or V10

Use this option if you plan to upgrade clients from previous Commvault versions. For example, upgrades from Version 10 to Version 11.

For Commvault packages that use the SQL Server software, the Download Manager will retrieve Microsoft SQL Server 2012 Enterprise. This SQL version is needed to upgrade clients that have SQL Server 2008 Enterprise (or earlier versions).

Feature Release Upgrade

Use this option if you plan to install feature release updates or additional agents on an existing client.

Note

If you plan to install Commvault packages that need the Microsoft SQL Server (such as the CommServe), select New Installations.

On the Custom Media Options page, select one of the following options, and then proceed to the next page:

Note

To view roles and packages, see Installation Roles and Packages.
- Media kit - Create a new CommCell Group: Select this option if you plan to install the CommServe, install feature release updates, or install additional agents on an existing CommServe computer.
- Media kit - Join an existing CommCell Group: Select this option if you plan to install a new client, install feature release updates, or install additional agents on an existing client.
- Full media kit
  - Install MS SQL Server for upgrades from v9 to v10: Select this option to upgrade clients from previous Commvault versions (for example, upgrade from Version 10 to Version 11).
  - Install MS SQL Server for new installations: Select this option to install Commvault on new clients, perform a hardware refresh, or install Commvault packages that need the Microsoft SQL Server (such as the CommServe).
  The Download Manager downloads all of the required installation files and feature release updates. For Commvault packages that need MS SQL Server software, the Download Manager downloads Microsoft SQL Server 2014 Standard.
- Advanced – For package based selection
On the Download Location page, specify the directory where you want to create the custom package, and then proceed to the next page.
On the Server Information page of the installation wizard, enter the CommServe hostname port using one of the following formats:
- If the client connects to the CommServe server directly, use the following: Hostname:PORT
- If the client connects to the CommServe server using a network gateway, use the following: Gateway_Hostname:PORT
  
  Note
  
  If you want to use multiple network gateways, you can enter multiple hostname ports separated by a semi-colon (;).
  
  For example: Gateway_Hostname1:PORT1;Gateway_Hostname2:PORT2
On the Custom Package Options page, select the options required by your custom package and then proceed to the next page.
Note

If you decide to save your selections during the package creation, consider the following guidelines:
- If Commvault is not installed on your computer, the Base Client software is installed to establish communications with the CommServe computer. You must provide the CommServe host name as well as your computer details.
- If you want to create an interactive custom package, configure the package to display the necessary options to the user, and record the option names so that you can notify users to better prepare them for the installation.
On the Install Status page, click Finish.

What to Do Next

Distribute the custom package by using one of the following methods:

Copy the package to a network share that is accessible by users.
Upload the package to the Download Center.

For more information, see Adding a Package to the Download Center.