Working with Software Blade Packages for Export

You can deploy an exported Software Blade Package to endpoint clients with third-party deployment software. When you create an Software Blade Package for export, the Initial Client is usually included in the package, and not installed first.

The procedure for creating a Software Blade package is almost the same as for defining a Deployment Rule. You select different sets of Software Blades for Desktop computers and laptops in a package. The package installation program automatically detects the computer type and installs the applicable Software Blades.

To create or change a Software Blade package for export:

1. In the Deployment tab, select Packages for Export.
2. To add a new package, click Add Package.

   The new package shows at the bottom of the list.

3. Double-click the Name cell in the applicable package and enter a package name.
4. Optional: Double-click the Version cell and select a different Endpoint Client version from the list.

   You can select Manage Client Versions, to add more package versions to the repository.

5. Click the Desktop Blades and Laptop Blades cells and then select the Software Blades to include in each package.
6. Optional: In the Settings column select a Virtual Group or create a new one. Users who install this package will automatically be put in this Virtual Group.
7. Optional: In the Settings column, if you defined a Remote Access VPN Software Blade, right-click the VPN setting and do one of these actions:
   • Select a predefined VPN site from the list.
   • Use a local VPN settings file
   • Add a new VPN site
8. If you are upgrading legacy Endpoint Security release, in the Settings column:
   • Double-click the legacy upgrade option and select Support client pre-install upgrade.
   • Select Silent mode active or Silent mode not active.
   • Select the Legacy Secure Access option and click Configure Upgrade Password to enter and confirm the password.
   • Select the Legacy Full Disk Encryption EW option and click Configure Upgrade Password to enter and confirm the applicable passwords.
9. In the Software Deployment Rules window, click Save.

To delete an existing package definition, select the package Name and click Remove.

Defining the Default VPN Site

When you use an exported package, you can configure each Software Blade package to connect to a default VPN site. You do this by changing the VPN site definition in the Settings cell.

You cannot configure a default VPN site with automatic Deployment. To distribute a defined VPN site with Deployment, you can:

• Use Deployment to distribute an Software Blade Package without Remote Access VPN.
• Create a package for export that includes only Remote Access VPN and distribute it manually.

By default, a new package uses the No VPN site defined setting.

To define the default VPN site:

1. Select a package. Make sure it includes Remote Access VPN in the Actions column > Selected blades.
2. Select Advanced Package Settings > VPN Client Settings from the navigation tree.
3. Click New to create a new site or Edit to change the details of a site. Enter:
   • Display name - The name users see when they connect to the VPN.
   • Site address - The IP address of the site.
   • Authentication method - How users authenticate to the VPN. Make sure that users have all required information and hardware, if required.

   This line can contain the No VPN site defined item or a predefined VPN site.

4. In the Deployment Rules window, click Save.

Exporting Packages

On Windows 8.1 and higher clients, you must install an exported package with Run as administrator selected. You cannot install it with a double-click.

1. In the Packages for Export window, select a package.
2. Click Download Package.
3. In the Export Package window:
   1. Select the platform versions (32/64 bit) to export for laptops and desktops.
   2. Click Download.
4. Click OK.
5. Select a location to save the files.

   The package EPS.msi and/or PreUpgrade.exe files are downloaded to the specified path. A different folder is automatically created for each option selected in step 3a.

6. Send the EPS.msi and PreUpgrade.exe files to endpoint users. Endpoint users manually install the packages. They must use Administrator privileges.

   You can also use third party deployment software, a shared network path, email, or some other method.