What are the ConfigMgr 2007 Site System roles?

Go back to the ConfigMgr 2007 Home Page

 

Contributed By: Cliff Hobbs [MVP ConfigMgr/ SMS]
ConfigMgr 2007 supports the following 16 Site System roles, with those prefixed with [NEW] being new to ConfigMgr:

  • Site Server - The server on which you install the ConfigMgr software.

  • Site Database Server - The server running SQL and hosting the ConfigMgr Site Database (only required for Primary Sites).

  • Configuration Manager Console - The interface for administering ConfigMgr. Installed by default on Primary Site Servers this role can also be installed on workstations to allow remote administration.

  • SMS Provider - The intermediate Windows Management Instrumentation (WMI), layer that sits between the Configuration Manager Console and the Site Database (the Configuration Manager Console accesses the Site Database via the SMS Provider). Only required for Primary Sites.

  • Component Server - All ConfigMgr Site System roles (except for the Distribution Point (DP)), requires ConfigMgr-specific software to be installed in order for the Site System role to function.  When such software is installed on a computer that computer becomes a Component Server.

  • Distribution Point (DP) - Stores ConfigMgr Packages from where Clients can access them to install them.  Only required for the Software Distribution, Software Updates, and Advertised Task Sequences functions of ConfigMgr

  • [NEW] Branch Distribution Point (BDP) - Allows a workstation to act as a DP in a remote location with typically less than ten workstations thus removing the need to install a Secondary Site Server.

  • [NEW] Fallback Status Point - A "catch all" Site System for Clients that cannot be installed because of various issues such as assignment, or their inability to communicate with their Management Point (MP).  Not required by default, but recommended to help with Client installation issues.

  • Management Point (MP) - ConfigMgr Clients do not communicate directly with the ConfigMgr Site Server and vice versa.  Instead all communication is facilitated via the Management Point.  A Default Management Point needs to be defined in every Site that has Intranet Clients.

  • [NEW] Pre-boot Execution Environment (PXE) Service Point - The Site System that responds to any computers requesting deployment of their Operating System (OS), via a PXE request.  Only required if Operating System Deployments (OSD), are going to take place using PXE boot requests.

  • Proxy Management Point (PMP) - Installed at Secondary Sites to act like a "funnel" to control Client communications both for Policy and uploading of data such as Inventory. Once the Proxy MP has been created, Advanced Clients retrieve Policy information from the Proxy MP which in turn queries the MP on the Primary directly on the Client’s behalf. In addition Advanced Clients upload their data to the Proxy MP rather than the MP on the Primary directly.  In this way the Proxy MP can bundle up the data it receives from the Clients and then using the Secondary Site’s Sender forward it onto the Primary.

  • Reporting Point (RP) - Hosts the Report Viewer component that provides the web-based reporting functionality of ConfigMgr. Only required if Reports need to be run on a particular Primary Site.

  • Server Locator Point (SLP) -  Responsible for informing ConfigMgr Clients which MP they should access in order to install the ConfigMgr Client software. Only required in some Client Deployment scenarios.

  • [NEW] Software Update Point (SUP) - Assigned to the computer running Windows Server Update Services (WSUS).  Only required if the Software Updates feature is going to be used.

  • [NEW] State Migration Point (SMP) - Stores the user's state migration data when a computer's OS is migrated.  Only required if the OSD feature is going to be used.

  • [NEW] System Health Validator Point (SHVP) - This role is assigned to the computer running the Network Policy Service.  Only required if the Network Access Protection (NAP) feature is going to be used.


To see other ConfigMgr 2007 Design related FAQs click here.
© FAQShop.com 2003 - 2009

Go back to the ConfigMgr 2007 Home Page