Does a CA ITCM environment with thousands of computer objects require a Microsoft SQL Client Access License (CAL) for every managed endpoint, or only for the servers that directly connect to the SQL MDB?
This article clarifies Microsoft SQL Server licensing requirements (CAL vs. Per Core) within a CA Client Automation (ITCM) environment, specifically addressing how Microsoft's 'multiplexing' rules apply to ITCM architecture.
In a standard ITCM deployment, individual Agents and Scalability Servers do not establish direct sessions with the Management Database (MDB). Instead, data is aggregated through Scalability Servers and processed by the Domain Manager, which performs the actual write operations to the MS SQL Server instances (visible in TRC_DBAPI logs).
Because of this architecture, customers often inquire whether they only need licenses for the Domain Manager rather than every endpoint.
CA Client Automation - All supported version.
Microsoft SQL
Under Microsoft's licensing definitions, the ITCM architecture is considered a form of multiplexing (pooling connections or data through an intermediate server/software).
Per Microsoft Licensing guidelines, multiplexing does not reduce the number of Microsoft licenses required. Any user or device that accesses the SQL Server—even if that access is indirect through a front-end application like ITCM—must be properly licensed.
For large-scale ITCM environments, the Per Core licensing model is typically the most cost-effective option.
To ensure full compliance and optimize licensing costs, Broadcom recommends that customers review their specific Microsoft Enterprise Agreement (EA) with a Microsoft Licensing Representative. Licensing terms can vary based on the specific version of SQL Server and the terms of the customer's agreement with Microsoft.