Tuesday, 28 June 2016

Implementing Site Servers

The terms site and site server are often used interchangeably. In reality this shouldn’t be the case. A Configuration Manager 2012 R2 site encompasses all servers that are used to deliver the services offered by the site. Said another way, a Configuration Manager 2012 R2 site can consist of one to several servers. The size of the site will dictate how many servers are needed to deliver service to clients. In smaller environments it may be that only a single server is needed to host all components needed to deliver the site’s services. In larger environments multiple servers may be needed. With the new design of Configuration Manager 2012 R2 the expectation is that the number of total sites needed for an environment will decrease, but the number of supporting servers for a site might increase.

A site server is the one server in a site that orchestrates delivery of service to clients. This server will interact with any other servers that are in place supporting the site’s ability to deliver services. These additional servers are known as site systems. (A site server is also a site system.) As services are added to a site and assigned to a server, the list of site system roles will increase. A quick glance at the Configuration Manager console will reveal the site systems that are in use to support a site and also what services those site systems are delivering on behalf of the site. An example is shown in Figure . Note that two systems are shown related to site code PRI. One is the site server itself and the other is a site system server providing service for the site.

 


No comments:

Post a Comment