How to move SCCM Distribution Point content folders

Jonathan LefebvreSCCMLeave a Comment

One of the common mistakes we still see is having SCCM distribution point content folders on many different drives, most of the time not on purpose. Usually, this will lead to C drive being full, or the drive where the SQL database sit. This will then cascade into a series of errors all over SCCM.

In this post, we will show how to use Content Library Transfer tool to move distribution content folders

Prerequisites

  • If you are running SCCM latest build, the tool is now build-in the install folder

Move SCCM Distribution point content

Move SCCM Distribution point content

Important Info
Turn out that the built-in version of the Content Library Transfer in SCCM 1802 and higher as issues that should be fixed with v1810 that should release soon.

This user voice item as all the details

Move SCCM Distribution Point content

Limitations
  • Run the tool locally on the distribution point. You can’t run it from a remote computer
  • Only use it when clients aren’t actively accessing the distribution point. If you run the tool while clients are accessing content, the content library on the destination drive may have incomplete data. The data transfer might fail altogether leading to an unusable content library
  • Don’t distribute content to the distribution point when you run the tool. If you run the tool while content is being written to the distribution point, the content library on the destination drive may have incomplete data. The data transfer might fail altogether leading to an unusable content library. 
  • Find the drives where there are Distribution Point content folder that shouldn’t be there
  • Move SCCM Distribution point content

    • It can be seen also in the registry key: HKLM\Software\Microsoft\SMS\DP\

    Move SCCM Distribution point content

    • As stated in the limitation, the Distribution Point needs to stop providing content to clients. This can be achieved by multiple solutions:
      • Remove the distribution point from any Boundary group
      • stop network connection to that distribution point
      • Stop IIS on that distribution point
    • Open a command prompt on the faulty distribution point
    • Browse to <SCCM install folder>\Tools\ServerTools
      • Using the old SCCM 2012 toolkit, the path will be <Program Files(x86)\ConfigMgr 2012 Toolkit R2\Server Tools
      • If this is to be ran on a remote distribution point, simply copy over the ContentLibraryTransfer.exe
      • Command line: contentlibrarytransfer.exe -SourceDrive f -TargetDrive e
      • You will need to repeat this if you have distribution point content on multiple drives and want to consolidate all of them

    Move SCCM Distribution point content

    • Transfer started. This will take time has it copy over all the content

    Move SCCM Distribution point content

    • Transfer completed

    Move SCCM Distribution point content

    • Content has been moved off the F drive

    Move SCCM Distribution point content

    • Put the SCCM distribution point back online

    Hope you found this blog useful!

    1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)
    Loading...

    Share this Post

    Contributor of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM consultant, working in the industry for more than 10 years. He developed a strong knowledge of SCCM and MDT to build automated OS deployment solution for clients, managed large and complexe environment, including Point of Sale (POS) related projects.

    Leave a Reply

    Your email address will not be published. Required fields are marked *