Endpoint Protection

Hi all,

we are currently planning the Upgrade from SEPM 12 to 14.

During the Update Process the Installer closes in error because the SQL Database is not patched to the latest Version.

Now we are thinking babout using the SEPM off of our SQL Cluster to another independent SQL 2016 Server. But the question arised on how to license this Server. 

In My Opinion the SEPM is counted as ONE Client, other Colleagues think we need to have a license for every single SEP Client connected to the SEPM.

Can someone point me to the right direction here?

Thanks in Advance

Stephan

Each SEP client counts as one license.

So if you have 50 clients that equates to 50 licenses in use.

See these articles:

http://www.symantec.com/docs/HOWTO80852

http://www.symantec.com/docs/HOWTO80778

http://www.symantec.com/docs/HOWTO80795

You will still use the same license you were using earlier, 

Each machine on which you install SEP client will count a license. If you are installing SEP client on SQL 2016 it will need a license too.

Hi Guys, 

thank you for your answers, I am aware that I can continue to use my existing Endpoint Protection License which covers every SEP Client, no problem. 

My question was about the SQL Licensing, what kind of SQL Server-License do I need? Is one Client SQL CAL(for SEPM) sufficient? Or do I need ~12000 SQL CALs for each of the Clients?

SQL licensing is a different story. You only need 1 SQL CAL. If you plan to have or add more SQL servers for failover/load balancing then you'd need another CAL. But basically 1 CAL per SQL DB

Whats the SQL 2016 edition you have and processor core? You will be installing SEPM on new instance?

Its only SEPM who will talk to your DB not SEP clients