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 specified in 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 the Alternate Method in Enabling 32-Bit Installations on 64-Bit Windows Computers.
- 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 /s /install /silent
Tip: 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.
If the client was not registered during the installation, use the RegisterMe tab in the Process Manager application to register the client. For instructions, see Registering the Client Using the Process Manager.
If the RegisterMe tab is unavailable, 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.