Very interesting wiki post on Technet: Microsoft Multi-tenant self-service portals that integrate IaaS through Microsoft System Center 2012 SP1 > http://ow.ly/dF9qn
Service Provider Foundation is provided with Microsoft System Center 2012 – Orchestrator, a component of Microsoft System Center 2012 Service Pack 1 (SP1). Service Provider Foundation exposes an extensible Open Data Protocol (OData) API over a Representational State Transfer (REST) web service that interacts with components of System Center. This enables service providers and large enterprise organizations to design and implement multi-tenant self-service portals that integrate IaaS capabilities available through Microsoft System Center 2012 SP1.
- Web Based Management Interfaces to System Center – Service Providers have invested over time as they have grown from virtualized infrastructures to a public or private cloud services provider offering self-service management portal capability. Web based management interfaces to System Center allow service providers to perform complex management operations using industry standard web service interfaces on cloud resources exposed by Microsoft System Center while retaining their investment in existing self-service portal capabilities.
- Retain Existing Portal User Interface – This scenario is related to the previous web based management scenario in that service providers have built unique and differentiating capabilities into their self-service management portals. Traditionally System Center has required Microsoft provided management interfaces to perform operations on cloud resources exposed by System Center. By exposing System Center capability through web based management protocols service providers can easily integrate System Center Infrastructure as a Service capability into their existing user interfaces.
- Multi-tenancy – Service providers have a broad customer base, these are tenants of the cloud service platform. Management portals that expose Infrastructure as a Service capability to tenants must do so in a manner that uniquely identifies them and isolates tenants from each other on the platform.
Management Across Instances of System Center Components – Users demand the ability to host their workloads across geographically separated boundaries for protection against a significant failure or other incident that may have broad reaching impact on a datacenter or facility. Service providers desire to distribute workloads across resources that are most efficient and/or manageable at any given moment of the life-cycle of each service. Both of these requirements require the platform to seamlessly support service management across multiple instances of System Center components. The instances of System Center components and associated infrastructure is referred to as a “stamp”. The concept of stamps is covered in the Architecture section of this article.
As some viewers are confused on the answering the question in my title, hereby a short summary. Important to mention, this is a view on the SPLA license model. This license model can divert from the Volume Licensing model. More information can be provided by your Microsoft account manager.
- Licensing a Managed Server
- for SCCM = 1x System Center 2012 Standard. SCEP rights are included in this license, so you do not need to buy an extra license.
- Licensing a Managed Client (e.g. laptop, computer …)
- for SCCM = 1x System Center 2012 Configuration Manager for clients. SCEP is NOT included in this licenses.
- for SCEP = 1x System Center 2012 Endpoint Protection for clients.
- REMARK 1: Both licenses are included in the Core CAL.
- REMARK 2: System Center 2012 Client Management Suite includes beside SCCM and SCEP also the licenses for SCOM, SCDPM, SCSM and SCORCH.
With the introduction of System Center 2012, the rules of the licensing game are (yet again) changed.
Gone are the separate licenses for each product in the System Center stack.
Following licenses are available in SPLA (maybe I’ll do another blog post with non-SPLA licenses).
- System Center 2012 Endpoint Protection for clients (SAL)
- System Center 2012 Configuration Manager for clients (SAL)
- System Center 2012 Client Management Suite (SAL)
- System Center 2012 Standard (Processor)
- System Center 2012 Datacenter (Processor)
Generally speaking, there are 2 components for SCCM (and the other System Center products, but I’ll focus on SCCM in this post):
- Managed Client licenses
- Managed Server licenses (for patch management, software distribution, sw/hw inventory etc.). Every management license for servers includes the right for 2 physical CPU sockets. No dependency on the amount of virtual CPU’s.
For the SCCM infrastructure itself (the servers) no licenses are necessary any longer (also the distribution points!). in the System Center server SAL’s, the rights for the management servers are included.
Also the SQL server licenses are included so no extra SQL licenses need to be purchased. One condition: only the databases of the System Center products may run on this SQL server.
Following products are available in the license
For Managed Servers
For Managed Clients
ConfigMgr 2012: Mastering the Fundamentals Kindle book now for only $9.99 on Amazon
GA for Windows Server 2012 is 4 September 2012. Windows 8 is planned on 26 October 2012.
Off course RTM is already available for MSDN and Technet subscribers
The entire quadrant can be found at http://www.gartner.com/technology/reprints.do?id=1-1AVRXJL&ct=120612&st=sb
Versions of the hypervisors (among others) vSphere 5.0, Hyper-V 2008 R2, XenServer 6 …
From the conclusion:
“VMware remains the market share and technology leader, but the market continues to grow, and competitors have a growing share of the market. While the majority of Global 1000 enterprises are heavily virtualized, a growing percentage have multiple virtualization technologies in place …”
PS: Microsoft has a very clear hybrid hypervisor strategy with SCVMM 2012