Welcome to the second part in this series. In the first part, we were introduced to Service Provider Foundation. In this next part we will review what is required to prepare the environment and the system requirements.
The following information is take from the following TechNet article: http://technet.microsoft.com/en-us/library/dn266008.aspx.
Here are the system requirements and considerations to keep in mind before you deploy Service Provider Foundation.
The two main products that Service Provider Foundation requires are System Center 2012 R2 Virtual Machine Manager and SQL Server. Please note:
- Only the VMM Console must be on the same server as Service Provider Foundation but the VMM Management Server can be on a different server. You can also have them all on the same server. The SQL Server database can be on any server, as only the server name and port number of the SQL Server installation are needed to install Service Provider Foundation.
- If you plan to implement usage metering to manage tenant costs, you will need an System Center 2012 R2 Operations Manager server and an Operations Manager Data Warehouse server.
Operating System Requirements
According to the Server Operating System Requirements for System Center, in order to deploy Service Provider Foundation (SPF for short), you need to be using Windows Server 2012 R2. That’s right, not even Windows Server 2012 is support, it must be the “R2” version. I’m not sure if that is completely true, but that’s what the article seems to indicate.
Server Roles and Features
The following Roles and Features are required as prerequisites for Service Provider Foundation (SPF).
Server Manager Roles
Web Server (IIS) server. Include the following services:
- Security > Basic Authentication
- Security > Windows Authentication
- Application Deployment > ASP.NET 4.5
- Application Development > ISAPI Extensions
- Application Deployment > ISAPI Filters
- Management Tools > IIS Management Scripts and Tools
Server Manager Features
- Management OData IIS Extension
- .NET Framework 4.5 features > ASP.NET 4.5
- .NET Framework 4.5 features > WCF Services > HTTP Activation
You can also install these roles and features by running the following PowerShell command.
Install-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Http-Tracing, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Basic-Auth, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Scripting-Tools, NET-Framework-45-ASPNET, NET-WCF-HTTP-Activation45, ManagementOdata, WAS, WAS-Process-Model, WAS-Config-APIs
SQL Server and Database Storage
Although it’s not required to install Service Provider Foundation, SQL Server is required on at least one server to contain the Service Provider Foundation database. 5 GB is sufficient storage for even large databases. Only the name and port for a SQL Server installation are required.
Install the following from the Microsoft Download Center:
Virtual Machine Manager
You must have System Center 2012 R2 Virtual Machine Manager in your environment, but you only need Virtual Machine Manager Console on the server where you install Service Provider Foundation .
You must obtain an SSL server certificate, or you can choose to have a test certificate automatically generated during setup.
In my lab, I’m going to use a self-signed certificate. Open IIS Manager, select the server in the left console and select Server Certificates in main area.
With the Server Certificates open, in the Actions menu on the right, select Create Self-Signed Certificate.
On the Create Self-Signed Certificate dialog, provide the friendly name. The friendly name must match the URL that is used when connecting to the Service Provider Foundation.
In my lab example, my SPF friendly name is: SPF.SC.LAB.
Now we can move onto the actual Installation of the Service Provider Foundation (SPF).