Home » Groups » Security & Compliance

Rolling out Symantec Endpoint

Rolling out Symantec Endpoint
Filed under: Symantec Endpoint Protection, Symantec Endpoint Protection Integration Component Security, Troubleshooting
neil_rogers's picture
Submitted by neil_rogers on 26 February, 2008 - 10:31.

If you are looking to deploy Symantec Endpoint Protection (SEP) in your environment, there are a few pointers to make it work better in the initial rollout.

These steps are what I would call "critical" in an organization with more than one global policy for their computers.

  1. Build a package in the SEP Manager (SEPM) to point it back to the manager and the group that they should be in once they are deployed. This is important if there are a number of groups and having the machine go to the correct group on installation rather than move them later. Very important for IT computers and kiosk computers.
  2. Build a new SWD task and package to deploy SEP client. Use the newly created package and send it out in the environment, and make a SWD Task and Package per install program that has the different policies predefined for it. To write that another way, have a SWD policy and task for IT, for Kiosk machines, for call center machines etc. This way they do not need to be moved into the correct group later, they get their policies right away. It is a lot quicker to build a swd package and task than it is to move the computers as they appear in the console.
3.857145
Average: 3.9 (42 votes)

I am wondering what the

Submitted by ConQuer0r on 27 February, 2008 - 14:52.

I am wondering what the impact would be to an NS server when adding the Symantec Endpoint Protection Integration Component.

The server is already kinda busy.

Or should you point me to a different forum?

Symantec Endpoint Protection Integration Component Load

Submitted by stebro on 12 June, 2008 - 10:30.

The Symantec Endpoint Protection Integration Component should have minimal impact to an existing NS. There are two key processes that will impact the load:

1 - Software Delivery of the SEP package which is around 60 Mb depending on the version you are deploying. This can be minimized if you have package servers in your environment.

2 - Reporting of the SEP data. The Integration Component will link the majority of the report data directly from the SEP manager and only imports computer records if they aren't present on the NS already. This can be minimized based on the import schedule.