>

In the world of enterprise IT, few tasks are as simultaneously critical and frustrating as deploying antivirus software across a fleet of machines. If you are a System Administrator or an IT Security Specialist, you have likely encountered the specific headache of installing Symantec Endpoint Protection (SEP) on machines that exist outside your standard Active Directory domain structure.

Whether it is a remote worker’s laptop, a machine in a DMZ, or a standalone server, these devices cannot easily pull the installation package from the Symantec Management Console. This is where the Unmanaged Client comes into play.

However, simply downloading the default "Unmanaged Client" from the Symantec website is rarely enough. It often comes bloated with default settings that conflict with your internal policies. To save time and ensure consistency, you need a repackaged installation file—a customized package that installs silently with your specific configurations pre-applied.

In this guide, we will walk through the process of obtaining, customizing (repackaging), and deploying the Symantec Endpoint Protection Unmanaged Client.


When deploying Unmanaged Clients, administrators must weigh the benefits against the security trade-offs:

Repackaging SEP for deployment in an organization can be necessary for various reasons, such as:

However, it's crucial to download software from official sources to ensure security and compliance. The official Symantec (now part of Broadcom) website or your licensed distributor are the best places to obtain legitimate and up-to-date versions of SEP.

Repackaging can involve:

back-icon