Endpoint Services, SCCM, How do I provision a distribution point for SCCM?
SCCM distribution point configuration and system requirements
System Center Configuration Manager (SCCM) Current Branch
University of Illinois IT Pros leveraging Technology Services Endpoint Service SCCM Current Branch
You will need
- to add the relevant primary site computer object to its administrators group (e.g.
SCCMUIUCPS1$for UIUC, see table below) on your unit's distribution point.
AD object name Hostname Campus SCCMUICPS1 SCCMUICPS1.ad.uillinois.edu Chicago SCCMUIUCPS1 SCCMUIUCPS1.ad.uillinois.edu Urbana-Champaign
- to make a request which specifies if you want your unit's distribution point to be configured for PXE, and other functions such as HTTPS (manage off-campus endpoints) and USMT.
- a stable desktop-quality computer or virtual machine with at least 8GB RAM and a separate drive for storing the packages your group is likely to create and request. You should err on the side of supplying more storage space where possible.
Distribution points configured for PXE that reside on a network outside of the endpoints they support will need IP helpers configured on those additional networks. We recommend contacting firstname.lastname@example.org to get those set up. Please provide the network names and the IP address of the distribution point.
Contact the SCCM team and they'll help you get a distribution point set up. Follow these steps to configure a new distribution point:
- Install Windows Server 2019 with Desktop Experience
- Join the server to the appropriate Active Directory domain
- Reference the table above and add the appropriate primary site computer object to the local Administrators group (open lusrmgr.msc)
- Configure the Windows Firewall as per this Microsoft document
- Add the "Remote Differential Compression" feature to the server
- The following IIS options can be configured by SCCM automatically, or they can be manually installed:
- Enable the IIS role, with the following role options checked
- Common HTTP features
- Default Document
- Directory Browsing
- HTTP Errors
- Static Content
- HTTP Redirection
- Health and Diagnostics
- HTTP Logging
- Logging Tools
- Request Monitor
- Static Content Compression
- Application Development
- ISAPI Extensions
- Management Tools
- IIS Management Console
- IIS 6 Management Compatibility
- IIS 6 Metabase Compatibility
- IIS 6 WMI Compatibility
- Common HTTP features
- Enable the WDS role
- Select both Deployment and Transport options
- Create a file named "no_sms_on_drive.sms" at the root of every volume that ConfigMgr should not use to store content (such as the OS drive)
- Contact EPS to add the server as a distribution point for your unit