Did you know you can move the content library folder to another drive on your Distribution Point ? It’s quite simple.
Simply use the ContentLibraryTransfer.exe from the SCCM SP1 Toolkit.
You didn’t already downloaded the toolkit ? Shame on you ! Here’s the download link : http://www.microsoft.com/en-us/download/details.aspx?id=36213
The syntax of the tool is straight forward :
ContentLibraryTransfer.exe –SourceDrive <Current Drive Letter> -TargetDrive <New Drive Letter>
There’s no “built-in” logs but you can pipe the output in a text file
Example : ContentLibraryTransfer.exe –SourceDrive C -TargetDrive D > c:CLT.log
Once completed, you can validate the change in the registry :
HKLMSOFTWAREMicrosoftSMSDPContentLibraryPath
Note : A NO_SMS_ON_DRIVE.SMS file will automatically be created on the Source Drive after the process is completed.
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.
3 Comments on “Move Content Library to another Drive”
Thanks for this brief article, and all the many others I have followed carefully. These are a great help to me.
Hi Team, Could you please us with below issue?
CLT:04/10/2017 12:00:14 Reading Host Configuration: Completed Successfully
CLT:04/10/2017 12:00:14 Verify Drives: Validating drives specified for the transfer exist
CLT:04/10/2017 12:00:14 Verify Drives: Completed Successfully
CLT:04/10/2017 12:00:14 Verify Destination: Check if target drive has enough space for the transfer
CLT:04/10/2017 12:00:39 One or more directories required for this transfer has an invalid length. Caught The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
CLT:04/10/2017 12:00:39 The destination does not have enough space to complete the transfer. Provide a different destination
Check if you have any SMSPKG$ already created on the destination drive , if so delete the folder and it will start transferring . I have faced similar issue .