You can install one or more optional site system roles at each System Center 2012 Configuration Manager site to extend the management functionality of the site. You can specify a new server as a site system server and add the site system roles, or install the site system roles to an existing site system server in the site.
|When a site system server is a computer other than the site server, it is referred to as a remote site system because it is remote from the site server in the site. Similarly, any site system role on that server is referred to as remote. For example, a remote distribution point is a site system server on a computer other than the site server, and which has installed on it the distribution point role.|
|When you install a site system role on a remote computer (including an instance of the SMS Provider), the computer account of the remote computer is added to a local group on the site server. When the site is installed on a domain controller, the group on the site server is a domain group instead of a local group, and the remote site system role is not operational until either the site system role computer restarts, or the Kerberos ticket for the remote computers account is refreshed.|
Use one of the following wizards to install new site system roles:
- Add Site System Roles Wizard: Use this
wizard to add site system roles to an existing site system server
in the site.
- Create Site System Server Wizard: Use
this wizard to specify a new server as a site system server, and
then install one or more site system roles on the server. This
wizard is the same as the Add Site System Roles Wizard,
except that on the first page, you must specify the name of the
server to use and the site in which you want to install it.
|Configuration Manager does not support site system roles for multiple sites on a single site system server.|
By default, when Configuration Manager installs a site system role, the installation files are installed on the first available NTFS formatted disk drive that has the most available free disk space. To prevent Configuration Manager from installing on specific drives, create an empty file named no_sms_on_drive.sms and copy it to the root folder of the drive before you install the site system server.
Use the following sections to help you install and configure site system roles for System Center 2012 Configuration Manager:
- Install Site System Roles
- Install Cloud-Based Distribution
Points in Windows Azure
- Configuration Options for Site
- Configure the Proxy Server for Site
|For planning information, such as where to install site system roles in the hierarchy, see Planning for Site Systems in Configuration Manager.|
Install Site System Roles
How you install a site system role depends on whether you add the site system role to an existing site system server or install a new site system server for the site system role. Use one of the following procedures.
|Configuration Manager lists the site system roles that are available for you to install. This list depends on your hierarchy configuration and whether you have already installed an instance of the site system role. For more information about the available placement of site system roles, see the Planning Where to Install Sites System Roles in the Hierarchy section in the Planning for Site Systems in Configuration Manager topic.|
To install site system roles on an existing site system server
To install site system roles on a new site system server
Install Cloud-Based Distribution Points in Windows Azure
|For Configuration Manager SP1 only:|
Before you install a cloud-based distribution point, make sure that you have the required certificate files:
- A Windows Azure management certificate that
is exported to a .cer file and to a .pfx file.
- A Configuration Manager cloud-based
distribution point service certificate that is exported to a .pfx
For more information about these certificates, see the section for cloud-based distribution points in the PKI Certificate Requirements for Configuration Manager topic. For an example deployment of the cloud-based distribution point service certificate, see the Deploying the Custom Web Server Certificate for Cloud-Based Distribution Points in the Step-by-Step Example Deployment of the PKI Certificates for Configuration Manager: Windows Server 2008 Certification Authority topic.
After you install the cloud-based distribution point, Windows Azure automatically generates a GUID for the service and appends this to the DNS suffix of cloudapp.net. Using this GUID, you must configure DNS with a DNS alias (CNAME record) to map the service name that you define in the Configuration Manager cloud-based distribution point service certificate to the automatically generated GUID.
If you use a proxy web server, you might have to configure proxy settings to enable communication with the cloud service that hosts the distribution point.
Use the following sections and procedures to help you install a cloud-based distribution point.
Configure Windows Azure and Install Cloud-Based Distribution Points
Configure Name Resolution for Cloud-Based Distribution Points
Configure Proxy Settings for Primary Sites that Manage Cloud Services
Configuration Options for Site System Roles
Many of the configuration options for the site system roles are self-explanatory or display additional information in the wizard or dialog boxes. Use the following tables for the settings that might require some information before you configure them.
Application Catalog Website Point
Application Catalog Web Service Point
Enrollment Proxy Point
Fallback Status Point
Out of Band Service Point
Configure the Proxy Server for Site System Servers
You can configure a site system server to use a proxy server for connections to the Internet that site system roles that run on that computer make. For information about the site system roles that can use the proxy server configuration, see the Planning for Proxy Servers Configurations for Site System Roles section in the Planning for Site Systems in Configuration Manager topic.
Use the following procedure to edit the proxy server configuration of a site system server.