Using the Export Package

Upload the package to the package repository

1. When you click the package repository icon, located in the toolbar of both the Export package and Software Deployment tabs, you are redirected to an internal Package Repository page.

2. When you click the "Upload Agent" button, a "Browse" modal opens. It prompts you to select the relevant file/s (ZIP, EXE) and folder(s) to upload.

   Notes: The administrator can abort an active package upload/download. Packages that are in use cannot be deleted.

3. When you click the package repository icon, located in the toolbar of both the Export package and Software Deployment tabs, you are redirected to an internal Package Repository page.

4. When you click the "Upload Agent" button, a "Browse" modal opens. It prompts you to select the relevant file/s (ZIP, EXE) and folder(s) to upload.

   Notes: The administrator can abort an active package upload/download. Packages that are in use cannot be deleted.

5. The administrator can abort an active package upload/download.

6. Packages that are in use cannot be deleted.

Create the package for export

1. Go to Policy > Export Package.

2. Do any of these:

   1. To export package for Endpoint Security, click Endpoint Client.

   2. To export package for Browser Security, click Browse Client and continue with Export the package or file.

3. Click the plus sign to create a new export package.

   The Create Export Package window opens.

4. Enter the Package Name and select the applicable Operating System.

5. Select an Operating System.

   • Windows

   • macOS

   • Linux

6. Select the Package version.

7. Select Capabilities.

   • For Linux, only the Anti-Malware blade is supported with the exported package.

     Note:

     If the Endpoint Security Anti-Malware capability is installed, the third-party Anti-Malware status in the Endpoint Security client is not displayed.

   • For general limitations on macOS, see sk110975.

8. To add a new VPN site to the package, see Adding a New VPN Site to an Exported Package.

9. Optional: Select a Virtual group or create a new one.

   Users who install this package will automatically be part of this virtual group.

   You can use the virtual group to apply a security policy to the entire group instead of to each object in the group separately.

10. Optional: Select a Software Signature.

    You can select a file signing method for MSI files that will be deployed using an external distribution system. By default, the client uses an internal signature to authenticate.

    Select one of these file signing methods:

    • None

    • Internal Certificate Authority

    • Custom - If you select Custom do these steps:

      1. Click Browse and get the certificate file (*.p12).

      2. Enter certificate password.

      3. Click Validate.

         The certificate is created on the Endpoint Security Management Server.

      4. Send the *.p12 file to client computers before you install the client package.

11. Select the settings for the Dynamic Package:

    Note - Dynamic package is not supported for macOS and Linux.

12. Optional: To download the package automatically after the system creates the package, select the Download package when saved checkbox.

13. Click Finish.

    The system starts to create the package. It can take several minutes depending on the package size. When the package is ready, the system shows Exported Package created message.

1. Go to Policy > Export Package.

2. Do any of these:

   1. To export package for Endpoint Security, click Endpoint Client.

   2. To export package for Browser Security, click Browse Client and continue with Export the package or file.

3. To export package for Endpoint Security, click Endpoint Client.

4. To export package for Browser Security, click Browse Client and continue with Export the package or file.