These devices operate independently. They do not communicate with a SEPM server. Instead, they download virus definitions directly from Broadcom’s public LiveUpdate servers. Security policies and scan schedules must be configured locally on the machine or baked into the installation package during creation.
: Modern SEP for Linux (14.3 RU1 and later) generally cannot run as a fully unmanaged client in the traditional sense; it often requires a packager tool called seplpkg . Key Differences of Unmanaged Clients
Select and click Export Client Install Package . Choose your desired platform (Windows, macOS, Linux).
Symantec Endpoint Protection (SEP) provides enterprise-grade security for devices, whether they are part of a large corporate network or operating as standalone systems. An is a version of the software that does not communicate with a central Symantec Endpoint Protection Manager (SEPM) server. Instead, it is administered locally by the device user, who is responsible for managing its security policies and virus definition updates.
"Repack" or "Repackage" in this context refers to taking the raw installation files and creating a streamlined .exe or .zip file for easier distribution to independent machines. These devices operate independently
: Browse to a local folder and click OK to generate the standalone .exe or folder structure. 3. Manual Repacking (The Sylink Method)
Copy these raw installation files to a dedicated working folder on your machine (e.g., C:\SEP_Repack_Workplace\ ). Phase 3: Creating and Customizing the Repack
Because there is no SEPM to push definitions, ensure the local machine can reach Symantec’s public LiveUpdate servers over ports 80 and 443.
Right-click the .exe file and select "Run as Administrator." Security policies and scan schedules must be configured
You can deploy the raw files silently using Microsoft Installer (MSI) commands via a batch script or your preferred deployment tool: msiexec /i "Sep64.msi" /qn /norestart RUNLIVEUPDATE=1 Use code with caution. /i : Instructs Windows Installer to run an installation.
An bridges this gap. It allows administrators to configure custom policies, firewall rules, and scan schedules once, and then bundle those settings into a single, self-installing executable file. Prerequisites for Creating a Repack
An is a standalone installation of Symantec Endpoint Protection. Unlike its managed counterpart, it does not communicate with a SEPM server for policy updates or status reporting. Instead, it relies on local configurations and retrieves definition updates directly from Symantec LiveUpdate servers. Why Use an Unmanaged Client?
Before initiating a download, it is essential to understand the differences between managed and unmanaged clients, as this decision dictates which installation package you need. The primary distinction lies in how the client is controlled and where it receives its updates. Choose your desired platform (Windows, macOS, Linux)
Right-click the desired version (e.g., Windows 64-bit) and select .
in your chosen folder that can be run on any compatible machine. Linux Repackaging : For Linux systems, Symantec provides a specific SEP Linux Packager tool (seplpkg)
For Linux environments needing a custom offline installer, Broadcom provides the seplpkg tool, which runs on both Linux and Windows. This tool can create a full or offline LinuxInstaller package for a given platform or for all Linux distros, which can be installed behind a firewall. It allows you to specify the platform (e.g., RHEL 7, 8, 9; Ubuntu 20, 22; Debian 10, 11) and the product version.
An unmanaged client does not communicate with a management server and an administrator does not manage the client. In this scenario, the end user of the computer has all rights to configure the client, change settings, and manually run scans or retrieve updates via LiveUpdate directly from the internet. You should install an unmanaged client for scenarios such as test computers, or if the computer is primarily off-site and will not have a reliable connection to the corporate management server. The unmanaged client gets all its content updates from the Internet and LiveUpdate, and the client user must update the content on each client individually.
The original SEP installation media matching your organization's licensed version. Step-by-Step Guide to Exporting the Unmanaged Package