Site System Roles
Full-Access Members Only
Sorry, this lesson is only available to Server Academy Full-Access members. Become a Full-Access member now and get instant access to this and many more premium courses. Click the button below and get instant access now.
Instructions
Q&A (0)
Notes (0)
Resources (0)
Saving Progress...
Resources
There are no resources for this lesson.
Notes can be saved and accessed anywhere in the course. They also double as bookmarks so you can quickly review important lesson material.
- What are Site System Roles?
They are roles that provide support for the Site. Listed are several of the roles that we will be working with in this course.
In our lab environment several of these roles are installed by default during the SCCM installation, or they are associated with the SQL installation. These roles are highlighted in yellow. I will point these out as we move through the list of roles.
To add a role is a very simple process. You just right click on the site, which in this case is
SA1, and select add Site System Roles
- Site System – A server that hosts one or more site system roles.
- Site Server – Is the machine on which you install SCCM. This role is automatically installed during SCCM installation.
- SMS Provider – This role is the interface between the Configuration Manager Console and the Site Database. This role could be installed on the primary, secondary or any other windows server.
If I right-click on the SMS Provider role, then click properties; this provides us additional
information about the role. This role uses WMI (Windows Management
Instrumentation) – The client uses WMI to extract information about the hardware, O/S and installed software of the client machine.
- HTTPS provides a security layer when clients using the administration service and are connecting to SCCM over the internet.
- Service Connection Point – This role is Installed during the SCCM installation. Connects
- Configuration Manager to Microsoft Cloud services. And is required to make updates for Configuration Manager available in the console. Can only be installed on the Primary Site.
- If we right-click on the server connection point then click properties.
- Here you have two choices. Online or offline. The default is on-line; this enables you to get the latest updates for your configuration manager installation, right there in the console. If you chose offline, then you have to use the Service Connection Tool. This tool enables you to manually import available updates
- Here is what the updates and servicing display looks like. Here you have updates from SCCM version 1902 to 1906 and then to 1910.
- Component Server – Is any server that runs the SMS Executive Service. This services consists of various threads or programs that run within the SMS Executive service.
This service is created automatically by configuration manager installation.
- Site Database Server – Hosts SQL Server Database. This stores information about the site.
- If we take a look at the properties of Site Database server The SQL service Broker Port is the port that is used by SCCM to replicate data between database sites. The default is set to port 4022. By default, compression is enabled when you are replicating to other sites.
- Management Point – Manages the communication between the client and the server. This role is automatically installed during the SCCM installation. This role could be installed on the primary, secondary, or any Microsoft Windows server
- The Management Point stores all the Policies from the Configuration Manager. Policies consist of all the client settings and the Client polling interval or how often the policies are deployed to the client on a schedule.
- If we right-click on the Management point and checkout MP properties, we see HTTP or HTTPS – For added security and If you have implemented PKI certificates, then you could use HTTPS, other wise the default setting of HTTP is fine for our lab.
- Clients upload all their software and hardware inventory data to the management point.
- Distribution Point – This role contains all the applications, software updates, O/S images, and their boot images. This role is automatically installed during SCCM. The DP could be installed on the primary, secondary or any Microsoft Windows server. You will configure the DP to enable PXE. PXE – Preboot Execution Environment – Let’s clients request and deploy operating systems across the network.
- There are several choices that you will need to make. I will explain each setting in detail in the OSD section of this course.
Server Academy Members Only
Sorry, this lesson is only available to Server Academy Full Access members. Become a Full-Access Member now and you’ll get instant access to all of our courses.
