Manually import client packages into Endpoint Protection Manager

book

Article ID: 152096

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

Note: This article is no longer being updated. The following article replaces it. Update your links or bookmarks to:
Importing client installation packages into Symantec Endpoint Protection Manager


You want to add client installation packages to a Symantec Endpoint Protection Manager (SEPM).

Resolution

To import a Symantec Endpoint Protection (SEP) client package into the manager:

  1. Log into the SEPM Console
  2. Select the Admin tab.
  3. Select Install Packages.
  4. Click Add Client Install Package from the Tasks menu.
  5. On the Add Client Install Package dialog:
    1. Provide a descriptive name for the installation package in the Specify a name for this package text box (i.e. Symantec Endpoint Protection 12.1 RU5 Mac Client)
    2. Click Browse.
    3. Navigate to the installation package folder (i.e. SEPM\Packages\ from the Part 1 installation media)
    4. Select the .info file associated with the installation package (i.e. SAV32.info, SAV64.info, SEP_MAC.info)
    5. Click Select.
    6. Optionally, provide a description of the package in the Description field.
    7. Click OK to start the import process.
  6. After a successful import, a status window will be displayed.
  7. Click Close to exit the Creating Package dialog.

After a successful import, a "Package is created" event will be logged into the System/Administrative logs.  Details will describe this new package with text similar to "Successfully imported the SEP 12.1 RU5 32-bit package via Symantec Endpoint Protection Manager. This package is now available for deployment."

Notes:

  • This process will not work with the SEPM web console. It can only import packages that were exported in the .ZIP file format. It will not import a .INFO file format package, it's not supported for web console. The web console can only import or export a single file.
  • It is possible to import an executable package (i.e. .EXE or .ZIP file packages) directly, but this is not recommended. The .INFO file contains extra information that describes the package and ensures proper migration to future builds of the SEP client via delta updates.