Download and own part 1 to 21 of the SCCM Installation Guide in a single PDF file.

The PDF file is a 162 pages document that contains all informations to install and configure SCCM 2012 R2 or SCCM 1511 and later (Current Branch). Use our products page or use the button below to download it .

Icon Info

This blog post applies to both SCCM 2012 R2 and SCCM 1511.

In the first part of this SCCM 2012 and SCCM 1511 blog series, we planned our hierarchy, prepared our SCCM Server and Active Directory.

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.

Introduction

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.

Pre-Requisites

  • 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

SCCM 2012 Distribution point Installation

IIS

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.

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.

BITS

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.

Powershell 3.0

For Windows 2012 only, you need to enable Powershell 3.0 (or further) before installing the distribution point.

Firewall

Ensure that your firewall is set correctly. 2 ports needs to be opened.

SCCM 2012 Distribution Point Installation

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.

SCCM 2012 Distribution Point Installation

  • On the General page, specify the Name for the site system server
  • Select the Site Code and Click Next

SCCM 2012 Distribution Point Installation

  • Do not specify a proxy server, click Next

SCCM 2012 Distribution Point Installation

  • Select Distribution point in the role selection screen, click Next

SCCM 2012 Distribution Point Installation

  • Check Install and configure IIS if required by CM
  • Add a description if needed
  • Select HTTP
  • Select Create self-signed certificate, click Next

SCCM 2012 Distribution Point Installation

  • Set drive configuration to your needs. This is where the SCCMContentLib will be created so select a drive with enough storage space, click Next

SCCM 2012 Distribution Point Installation

  • Do not configure a pull distribution point, click Next

SCCM 2012 Distribution Point Installation

  • Do not configure PXE for now, click Next

SCCM 2012 Distribution Point Installation

  • Do not enable multicast for now, click Next

SCCM 2012 Distribution Point Installation

  • Enable content validation to occur where it fits your environment, click Next

SCCM 2012 Distribution Point Installation

  • Add the boundary group that needs to be associated with this DP and Uncheck the Allow fallback source location for content, click Next

SCCM 2012 Distribution Point Installation

  • Review the summary page and complete the installation, click Next

SCCM 2012 Distribution Point Installation

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.

Verification

Logs

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)

Windows Explorer

At this point, you will the SCCM file structure created on the site server.

SCCM 2012 Distribution Point Installation

Console

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

SCCM 2012 Distribution Point Installation

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

SCCM 2012 Distribution Point Installation

Replicate content

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

SCCM 2012 Distribution Point Installation

Verify that the content is well replicated in the SCCM Console. (or check distmgr.log)

SCCM 2012 Distribution Point Installation

That’s it ! You’re done creating your DP.

Monitoring

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.

SCCM 2012 Distribution Point Installation
4 - 10 votes
Comments
  • Michel
    Posted at 10:09 AM September 20, 2016
    Michel
    Reply
    Author

    Hi,
    I have a DP(DP1) that I will delete because the server will be shut down soon (I’m changing my infra). And I have an another DP(DP2) which is almost the same as the DP1 I want to delete.
    Is it possible to replicate DP1 to DP2 in SCCM 2012 R2 ?
    Thanks.
    Regards,
    Michel

    • Benoit Lecours
      Posted at 12:55 PM September 20, 2016
      Benoit Lecours
      Reply
      Author

      You mean the content of the DP ? If so, just create a Distribution Point Group and add your DP into the group.
      https://technet.microsoft.com/en-us/library/hh427335.aspx?f=255&MSPPError=-2147217396

      • Michel
        Posted at 2:18 AM September 21, 2016
        Michel
        Reply
        Author

        Exactly yes. Ok, I’ll try this, thanks :).
        Regards,
        Michel

      • Benoit
        Posted at 1:38 PM November 3, 2016
        Benoit
        Reply
        Author

        I create a new DP I did everything group boundary etc. but I am not sure the client are connecting to it. there were connecting to a other one (other site) but now I want them to connect to this new one.

        thanks

        • Benoit Lecours
          Posted at 1:57 PM November 22, 2016
          Benoit Lecours
          Reply
          Author

          Check CAS.log, it will state which DP it’s using.

  • Omar Abi Nader
    Posted at 7:15 AM September 15, 2016
    Omar Abi Nader
    Reply
    Author

    Hello,
    I installed a stand-alone site rolling MP and DP on the same server.
    I have a branch that have slow connection with site server. I configured one of its machines as DP. The rest of the machine are still pulling the client installation from the site server.
    Note that i created a boundary group for this branch and chose the DP as a fast connection.

  • LT.Son
    Posted at 7:19 AM July 11, 2016
    LT.Son
    Reply
    Author

    Hello, we have 32 DPs deployed to our remote offices. Today I noticed that 13 if them have only 2 roles installed. “Site System” and “Distribution point”. The “Component server” role is missing.

    One of these sites have reported OSD problems. Can this be related to the missing role?

    • JL
      Posted at 5:44 PM August 24, 2016
      JL
      Reply
      Author

      Hi LT, I have the same problem DP Component Server Rol is missing and I have OSD problems too. Could you solved that problem?

  • Kenneth Dean
    Posted at 11:36 AM April 29, 2016
    Kenneth Dean
    Reply
    Author

    I setup a DP for client settings etc. Does the the DP need IIS, BITS, Remote Diff. Compression and WDS on the DP server itself?

    • Kenneth Dean
      Posted at 1:16 PM April 29, 2016
      Kenneth Dean
      Reply
      Author

      NVM, it appears it does need these roles installed not just the site server but all DPs as well, lol.

  • sheikvara
    Posted at 1:45 PM July 10, 2015
    sheikvara
    Reply
    Author

    Nice

  • Joe
    Posted at 3:50 PM March 24, 2015
    Joe
    Reply
    Author

    What happens if you drop an NO_SMS_ON_DRIVE.SMS file on the root of every drive, except for the one where you want to install your Distribution Point? I’d really rather not have SCCM adding content to a second drive on my file servers if space becomes an issue. Would much rather just expand the existing drive if needed. Will the installation of the Distribution Points barf if I try this?

    • Benoit Lecours
      Posted at 8:15 AM March 25, 2015
      Benoit Lecours
      Reply
      Author

      You can place the file on every drives except the one you want content on. During the DP installation wizard you can also choose where to put your content.

      • Joe
        Posted at 8:26 AM March 25, 2015
        Joe
        Reply
        Author

        Understood, but when going through the DP wizard there is no option to not configuration a Secondary Content/Package library. It can be left as “Automatic”. My question is if I place the file on all drives except G, then select G as my primary content library location and leave the secondary options as Automatic…. is that a supported configuration for not having a secondary storage location? I’m just a little worried about doing this live on our production servers when the GUI doesn’t seem to support NOT having a secondary drive.

        • Benoit Lecours
          Posted at 8:42 AM March 25, 2015
          Benoit Lecours
          Reply
          Author

          Yes it’s supported. As long as there’s 1 drive without the file, the installation will succeed. If your G drive runs out of space, you’ll get an error and you won’t be able to distribute anything on this DP.

          I’ve setup hundred of DP this way, no need to be worried 🙂

          • Joe
            Posted at 8:44 AM March 25, 2015
            Joe
            Author

            Whew, good to know. Thank you!

  • Matt
    Posted at 4:44 PM February 26, 2015
    Matt
    Reply
    Author

    Are there any logs that show client connections to the DP? I am suspecting that my clients are still coming back to the site server for packages instead of the DP. I have boundaries and boundary groups configured, but I see no traffic when I do a netstat from the DP after doing a package push to the clients.

    • Benoit Lecours
      Posted at 2:52 PM February 27, 2015
      Benoit Lecours
      Reply
      Author

      I suggest that you check the LocationServices.log on your clients for this or you can check the MP_Location.log on the server to see clients incoming requests.

  • binary
    Posted at 11:51 AM February 1, 2015
    binary
    Reply
    Author

    Hi,
    I have a single site with SQL installed on the same machine and after CM2012R2 installation I’ve received an error on the DP:

    “Distribution Manager failed to process package “Configuration Manager Client Package” (package ID = PS100003).

    Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
    Solution: Verify that distribution manager can access the package source directory/distribution point.

    Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
    Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.

    Possible cause: There is not enough disk space available on the site server computer or the distribution point.
    Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.

    Possible cause: The package source directory contains files that might be in use by an active process.
    Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.”

    I solved the problem by adding my CM server to the local administrators group, like in your guide. But is it the best practice even in the production? I can also add that my CM installation was clean without any error messages or warnings.

    • Benoit Lecours
      Posted at 8:28 AM February 2, 2015
      Benoit Lecours
      Reply
      Author

      But is it the best practice even in the production?

      Yes, no problem there 🙂

      • Binary
        Posted at 12:34 PM February 3, 2015
        Binary
        Reply
        Author

        Great! Thank you for your answer 🙂

  • Simon
    Posted at 6:30 PM December 14, 2014
    Simon
    Reply
    Author

    Thanks for this valuable information.
    Is there a way to automate this in a TS?
    I would like to deploy/configure DPs via TS when a server is built. The Server OS will be Server 2012.

    • Benoit Lecours
      Posted at 9:02 AM December 15, 2014
      Benoit Lecours
      Reply
      Author

      Hi Simon,

      I’ve done it for a client a while ago. You’ll have to use PowerShell for that. Unfortunately, I can’t share the script as I’m not the owner.

      I can give you some hints :
      Use Import-Module for the prerequisites
      Use New-CMSiteSystemServer to add the site system
      Use Add-CMDistributionPoint to add the Distribution Point role
      Use Add-CMDistributionPointToGroup to add your DP to a group

      Hope it helps.

      Benoit

  • RP
    Posted at 3:56 PM December 4, 2014
    RP
    Reply
    Author

    We have used SCCM 2007 and are currently using SCCM 2012 RTM. I just built a SCCM 2012 R2 environment. I thought I had read somewhere in this version Microsoft was finally going to allow multicast directly by access content directly from the distribution point? If I force the WIM into multicast only and set the task advertisement to access content directly it starts a unicast. If I set the task to “download content locally” it does the usual multicast. Are we still not able to multicast directly off the distribution point? I may have read it in a forum a while back so it may never have been added in. We have 57 gig wim files we deploy which takes a while to expand and unwim once the transfer is complete (usually sent to 1200 machines in groups of 40 at a time). I am driving myself nuts trying to get this working but it could just be they haven’t actually built it into the product as of yet. If you are able to confirm either way it would be appreciated.

    Thanks!

  • Leave a Reply