: All policies and settings must be managed locally on the client machine itself.
Which of those would you like?
In newer versions of SEP (14.3 MP2 and later), Broadcom has streamlined the console. Sometimes the "Unmanaged" export is hidden. You may need to create a "Non-Shared" group in SEPM, assign a "Default" policy to it, and then export that package. Even if it tries to call home, without a valid certificate or reachable server, it will function as an unmanaged standalone client. : All policies and settings must be managed
: Log in to the Symantec Endpoint Protection Manager console.
To repack the client specifically for unmanaged use: Sometimes the "Unmanaged" export is hidden
Downloading and repackaging a Symantec Endpoint Protection Unmanaged Client is a straightforward process performed through the SEPM console's "Install Packages" section. By creating a custom install setting and exporting it, administrators can provide robust endpoint security for remote or isolated devices that cannot communicate with the internal management server
Once you have the base .exe or extracted folder structure, you need to prepare it for deployment. This is where you ensure the "Unmanaged" client doesn't just install default settings that annoy your users. : Log in to the Symantec Endpoint Protection Manager console
: Click Add Client Install Feature Set . You can enable or disable specific features such as Virus and Spyware Protection , Network Threat Protection (Firewall) , and Proactive Threat Protection .