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).

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

First, obtain the version of SEP installation package you'd like to import by following these steps. 

*If you already have the .info and .dat files, skip this section.

1. Login to https://support.broadcom.com/, click on My Downloads.
2. Type Endpoint Protection in the upper right search bar, click Endpoint Protection.
3. Select Endpoint Protection to expand a list of versions.
4. Select the SEP version you'd like to import.
5. Locate the file named Symantec_Endpoint_Protection_<version>_SEPM_EN.exe and download it.
6. Once the download completes, right click on the file and extract it with your compression utility of choice.
7. Open the resulting Symantec_Endpoint_Protection_<version>_Refresh_SEPM_EN folder, then open the Packages folder.
   • The Packages folder will contain a .dat and .info file for each Windows 32/64 bit installation package.
8. Copy the Packages folder to the server hosting the SEPM.

Next, import the client packages into the SEPM.

1. Log into the SEPM, click the Admin tab.
2. Select Install Packages towards the bottom.
3. Under Tasks, click Add Client Install Package.
4. On the Add Client Install Package window:
   1. In the Specify a name for this package field (second text box), enter a descriptive name which includes the version (i.e. Symantec Endpoint Protection 14.3 RU5 64bit Windows)
   2. Click Browse and navigate to the Packages from the first set of steps above. (the Packages folder is found in the SEPM installation media).
   3. Select the .info file associated with the installation package (i.e. SAV32.info, SAV64.info, SEP_MAC.info) you'd like to import.
   4. Click Select.
   5. Optionally, provide a description of the package in the Description field.
   6. Click OK to start the import process.
5. After a successful import, a status window will be displayed.
6. 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.  

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.