Installing a Windows Custom Package Configured as a Self-Extracting Executable File

If the custom package was configured as a self-extracting executable file, you can install the custom package by running the executable file interactively or silently.

Note

If the custom package is a folder with contents, and not a self-extracting executable file, see Installing the Custom Package on Windows Computers.

Before You Begin

Obtain the custom package from the location specified by the user who created it.

If the package is in the Download Center, see "Downloading a Software Package" in Download Center - Web Console.
Based on the agents that are included in the custom package, verify that the computer on which you want to install the package satisfies the minimum requirements. For more information, see System Requirements.
If you have a 64-bit Windows computer and you need to protect 32-bit applications, you must configure a registry key to enable 32-bit agent installations. For more information, see "Alternate Method" in Enabling 32-Bit Installations on 64-Bit Windows Computers.
If you want to use the authorization code during the silent installation, you must obtain it from the Command Center.

Procedure

Log on to the computer as an Administrator or as a member of the Administrator group on that computer.
Go to the location where you stored the custom package.

The custom package is an executable file (for example, CustomPackageName.exe).
Use one of the following installation methods:
- To install the package interactively, double-click the executable file to start the installation.
- To install the package silently, run the following command:
```
 
CustomPackageName.exe /silent /install /silent /authcode authcode
```
  Where authcode is the company authorization code, which is required if you did not enter the installation user's credentials when the package was created. To obtain the authorization code, go to Command Center Companies > Company name > General or CommCell > General.
  Note
  - If you want to use a custom answer file during the installation, add the argument /play install.xml to the above command, where install.xml is the name of the custom answer file in the custom package. For more information, see Customizing the Answer File of a Windows Custom Package.
  - If you are using the Command Center endpoint URL for installation, add the argument /endpoint URL <EndPointURL> to the above command, where <EndPointURL> is the URL of the Command Center.
- To wait for the installer process and get an exit code, add the following command to a batch file and then run the command:
```
 
Call CustomPackageName.exe /silent /wait /install /silent /authcode authcode
```
```
echo %errorlevel%
```
  Where authcode is the company authorization code, which is required if you did not enter the installation user's credentials when the package was created. To obtain the authorization code, go to Command Center Companies > Company name > General or CommCell > General.
  
  Note
  
  If you want to use a custom answer file during the installation, add the argument /play install.xml to the above command, where install.xml is the name of the custom answer file in the custom package. For more information, see Customizing the Answer File of a Windows Custom Package.

Note

If the package fails to extract the software and displays an error stating that the program "Could not read the source SFX", move the package to the root of C: drive and retry the installation. The software extraction could fail if the package was in a directory that had non-English characters.
For a list of installer error codes, see Installer Error Codes.

Postinstallation Tasks

If the client was not registered during the installation, use the Edge Monitor application to register the client. For instructions, see Interactive End-User Edge Monitor Activation.

If the registration using Edge Monitor is not available, the CommServe name was not defined during the custom package creation. In such a case, you can register the client by using the CommCell Console or through the command-line interface. If you do not have access to the console, a user with administrative rights in the CommCell must perform the registration for you.