The PDF file is a 162 pages document that contains all informations to install and configure SCCM Current Branch. Use our products page or use the button below to download it .size>
This blog post has been updated. Please refer to the new SCCM Current Branch Installation Guide.
In part 2, we installed and configured SQL in order to install SCCM.
In part 3, we installed a stand-alone SCCM Primary site.
In the next 16 parts, we will describe how to install the numerous site systems roles available in SCCM 2012 R2 and SCCM 1511. Role installation order is not important, you can install roles independently of others.
In this part, we will describe how to perform a SCCM 2012 or SCCM 1511 distribution point installation.
I saw a lot of posts recently on the Technet forum which leads me to think that there’s a lack of documentation explaining this.
Several distribution points can provide better access to available software, updates, and operation systems. A local Distribution Point also prevents the installation thought the WAN.
- Functional SCCM 2012 hierarchy
- SCCM 2012 Admin console access
- RDP access on the Distribution Point server
- The required level of security in the SCCM console
Distribution point server configuration
Prevent package from replication on the wrong drive
- Logon locally on the target machine with remote desktop
- Create an empty file called NO_SMS_ON_DRIVE.SMS on the root of each drive where SCCM should NOT write. (If any)
Local Administrator group
On the DP, add a group that contains your site system computer account in the Administrators group.
I like to create a SCCM system groups that contains all my distribution points.
- Open Server Manager
- Expand Local Users and Groups
- Click on Groups
- Double-click on “Administrators”
- Add the security groups that contain the SCCM computer account
Windows Server configuration – Roles and Features
Configuration Manager requires some roles and features to be installed on the server prior to the DP installation
Remote Differential Compression
- Open Server Manager, on the Features node, starts the Add Features Wizard.
- On the Select Features page, select Remote Differential Compression
IIS needs to be installed on the server but it will automatically be installed using the site installation wizard.
For Windows Server 2003, you must install and configure IIS manually.
Make sure that these roles are installed on your server prior to the installation :
- IIS WMI Compatibility tool
- IIS Scripting Tool
Windows Deployment Service
For Windows Server 2008, 2008 R2, 2012 and 2012R2, WDS is installed and configured automatically when you configure a distribution point to support PXE or Multicast.
For Windows Server 2003, you must install and configure WDS manually.
With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS
Microsoft Visual C++ 2008 Redistributable
You can run the Microsoft Visual C++ 2008 Redistributable Setup from the Configuration Manager installation at: <ConfigMgrInstallationFolder>\Client\x64\vcredist_x64.exe
For Configuration Manager SP1, vcredist_x64.exe is installed automatically when you configure a distribution point to support PXE.
For Windows 2012 only, you need to enable Powershell 3.0 (or further) before installing the distribution point.
Ensure that your firewall is set correctly. 2 ports needs to be opened.
DP site server installation
Reboot your server to avoid case where your server is in “Reboot pending State” which will result in unexpected reboot during distribution point installation.
Now that the Distribution point server is ready to receive a new role, we need to add the server to the site server list
Add new distribution point server to the SCCM console – Site System
- In the Configuration Manager console, click Administration
- In the Administration workspace, expand Site Configuration, and then right click Servers and Site System Roles.
- Select Create Site System Server. The Create Site System Server Wizard opens.
- On the General page, specify the Name for the site system server
- Select the Site Code and Click Next
- Do not specify a proxy server, click Next
- Select Distribution point in the role selection screen, click Next
- Check Install and configure IIS if required by CM
- Add a description if needed
- Select HTTP
- Select Create self-signed certificate, click Next
- Set drive configuration to your needs. This is where the SCCMContentLib will be created so select a drive with enough storage space, click Next
- Do not configure a pull distribution point, click Next
- Do not configure PXE for now, click Next
- Do not enable multicast for now, click Next
- Enable content validation to occur where it fits your environment, click Next
- Add the boundary group that needs to be associated with this DP and Uncheck the Allow fallback source location for content, click Next
- Review the summary page and complete the installation, click Next
WARNING Your remote server may reboot if there’s a missing requirement
At this point, the major part of installation a distribution point server is completed.
You can track the installation progress in 2 logs:
- Distmgr.log on the site server
- Smsdpprov.log on the distribution point. (InstallationDrive\SMS_DP$\SMS\Logs)
At this point, you will the SCCM file structure created on the site server.
You can also track the installation progress in the SCCM console under Monitoring / Distribution Status / Distribution Point Configuration Status
- Click on your DP
- Click the detail tab on the bottom
- Check for green check mark on all components
Note: Error on the IIS Virtual directory is normal at the start of the process. SCCM is making a check as if IIS is installed at the start of the process even if you tell SCCM to enable you IIS for you. That results in errors but be patient and the installation should succeed anyway
- Verify the status of your new DP in Administration / System Status / Site Status
You can now replicate your content to your newly created DP. Replicate manually all your content or add your DP in an existing DP group.
Replicate a package or Application to your newly created site system
Verify that the content is well replicated in the SCCM Console. (or check distmgr.log)
That’s it ! You’re done creating your DP.
If you have multiple Distribution Point, I suggest you to read our post on 8 ways to monitor your distribution points. This post explain in details the various options to make sure that your DP are healthy.
You can also check our custom report about Distribution Point Monitoring to display all your DP status using a single click.
Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.