Announcement

Collapse
No announcement yet.

Lizensierung für SEPM mit Windows Server & SQL-DB

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    Lizensierung für SEPM mit Windows Server & SQL-DB

    Um auch bei der Lizensierung Ihres Symantec Produktes bei Microsoft auf der sicheren Seite zu sein,
    sollten Sie vor der Inbetriebnahme Ihres Symantec Endpoint Protection Managers mit Microsoft SQL Datenbank Ihre Lizenz Situation beachten.


    Microsoft SQL-DB:

    Bei der Verwendung vom Symantec Endpoint Protection Manager, unter einer Microsoft SQL Datenbank, können abhängig von Ihrer verwendeten Lizenz,Lizenzgebühren durch Unterlizensierung der SQL-Datenbank an Microsoft anfallen.

    Diese sind abhängig von Ihrer verwendeten SQL-Lizenz.

    Sollten Sie eine User-Basierte Lizensierung verwenden, muss eine CAL (Client Access License), für jeden SEP Clienten erworben werden,
    der über den Manager (direkt oder indirekt) auf die SQL-Datenbank zugreift.

    Sollten Sie eine Core-Basierte Lizenz nutzen können hingegen beliebig viele Ihrer Klienten,
    sich mit Symantec Endpoint Protection Manager verbinden und es fallen keine weiteren Lizenzgebühren für neue Klienten an.

    Quelle (Siehe Seite 9):

    https://download.microsoft.com/downl...uide_EN_US.pdf

    Core-Based Licensing

    Under the Per Core licensing model, each server running SQL Server 2016 software or any of its components (such as Reporting Services or Integration Services) must be assigned an appropriate number of SQL Server 2016 core licenses. The number of core licenses needed depends on whether customers are licensing the physical server or individual virtual operating system environments (OSEs).

    Unlike the Server+CAL licensing model, the Per Core model allows access for an unlimited number of users or devices to connect from either inside or outside an organization’s firewall. With the Per Core model, customers do not need to purchase additional client access licenses (CALs) to access the SQL Server software.



    Windows Server:

    Anders sieht hierbei die Kommunikation zwischen SEP und SEPM selbst aus.

    Die Kommunikation von SEP 12.x & SEP 14.x findet mit dem Manager über Apache Webserver, ohne die Authentifizierung von Windows User Accounts statt.

    Somit fallen hier für die Benutzung des Symantec Endpoint Protection Manager auf einem Windows Server keine zusätzlichen CAL für die Nutzung Ihrer SEP Klienten an.

    Quellen:

    https://support.symantec.com/en_US/a...ECH162350.html

    https://blogs.technet.microsoft.com/...s-license-cal/

    Hierzu Bezug nehmend auf die Referenz Punkt 5:

    5 – Do I need a CAL when my Windows Server is used to run a web server?
    Windows Server 2012 R2 configured to run Web Workloads ** do not require CALs or External Connectors. Web workloads, also referred to as an internet web solution, are publically accessible (e.g. accessible outside of the firewall) and consist only of web pages, web sites, web applications, web services, and/or POP3 mail serving. Access to content, information, and/or applications within the internet web solution must be publically accessible. In other words, they cannot be restricted to you or your affiliate’s employees.

    If you have Windows Servers configured to run a “web workload” these users will not require CALs or External Connectors. However, let’s say you are using Windows Server to setup an online store where customers can buy widgets. You have front end Windows Servers setup to support your website, and backend servers (e.g. commerce servers) setup so customers can check out and buy your widgets. The front end servers used to host your website would generally be considered as running “web workloads” and CALs or External Connectors will not be required to access these servers. Once the customer adds a widget to their shopping cart, creates an account and enters their credit card and shipping information to complete the sale – they are now authenticated via your back end commerce servers/application (non-web workload). Since users are accessing the backend commerce servers which web workloads are not running – CALs or External Connectors will be required for users to access these back end servers.

    ** Web Workloads (also referred to as “Internet Web Solutions”) are publicly accessible and consist solely of web pages, websites, web applications, web services, and/or POP3 mail serving. For clarity, access to content, information, and applications served by the software within an Internet Web Solution is not limited to your or your affiliates’ employees.
    Software in Internet Web Solutions is used to run:

    - Web server software (for example, Microsoft Internet Information Services), and management or security agents (for example, the System Center Operations Manager agent).
    - Database engine software (for example, Microsoft SQL Server) solely to support Internet Web Solutions.
    - The Domain Name System (DNS) service to provide resolution of Internet names to IP addresses as long as that is not the sole function of that instance of the software.


    Mit freundlichen Grüßen,

    Keksdose
    Last edited by Keksdose; 19.04.2017, 12:49.
Working...
X