These systems connect directly to an on-premises or cloud-based SEPM console. The administrator controls policies, schedules scans, and pushes virus definition updates from a central location.
Embedding specific settings, such as scan schedules, exception lists, and firewall rules, directly into the installation package.
Note: While this is faster for one-off deployments, utilizing the SEPM Export method (Step 4) is preferred for distribution as it allows for pre-configuration of feature sets.
Forces the client to ignore server registration routines. These systems connect directly to an on-premises or
To build or repackage an unmanaged client, you must first obtain the full SEP installation package.
Since the client cannot receive policy changes from the console, any custom firewall rules, application control exceptions, or scheduled scan times must be configured directly within the client UI on that specific machine.
Step-by-Step Guide to Creating and Repacking an Unmanaged Client Note: While this is faster for one-off deployments,
To download and repackage a , you must obtain the official installer from Broadcom and, if necessary, export it via the Symantec Endpoint Protection Manager (SEPM) to ensure it does not attempt to connect to a management server. An unmanaged client operates independently, downloading its own security definitions directly from the internet via LiveUpdate. 1. Downloading the Base Installer
You need administrative access to a Symantec Endpoint Protection Manager console to generate the base installation files and custom policy files.
Standard unmanaged installations require manual configuration after setup. Network administrators often repackage or "repack" the installer to streamline deployment across multiple standalone machines. Key Drivers for Repackaging Since the client cannot receive policy changes from
When administrators search for a "repack download," they aren't usually looking for a hacked version. They are looking for officially documented methods to transform the standard MSI into a different installer.
Before generating a repackaged installation file, it is essential to understand how an unmanaged client functions compared to its managed counterpart.