In enterprise IT environments, Symantec Endpoint Protection (SEP) is a standard for securing workstations. While the ideal deployment method involves pushing a "Managed Client" via the Symantec Management Console (SEPM), there are specific scenarios where an Unmanaged Client is required.
He opened his laptop and began writing a resignation letter. But first, he had fifty-three long, painful phone calls to make. But first, he had fifty-three long, painful phone
To download and repackage a Symantec Endpoint Protection (SEP) unmanaged client, 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 a machine in a DMZ
To create a true repack, modify the sylink.xml. In an unmanaged client, this file is local. Edit the LocalPolicy section to define: or a standalone server
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.
Repackaging can involve: