SCCM Content Library Cleanup Tool

If you want to clean up the content library in SCCM, you must use the Content Library Cleanup tool. The content library clean up tool deletes the orphaned content from SCCM distribution point.

In this post I will cover what is content library cleanup tool, it’s requirements and how to use it. You can find ContentLibraryCleanup.exe in CD.Latest\SMSSETUP\TOOLS\ContentLibraryCleanup on the site server.

What is SCCM Content Library Cleanup Tool

The content library clean up tool is basically a command line tool. Using this tool you can delete orphaned content on distribution point.

What is orphaned content on distribution point ?. Any content that is not associated with SCCM application or package is considered as orphaned content. Deleting the orphaned content is important because that will save disk space on your distribution points. It doesn’t make sense to keep orphaned content on a distribution point ?.

This tool was first introduced in Technical Preview version 1612. But now you should find this tool with every release of SCCM current branch.

SCCM Content Library Cleanup Tool Requirements

Before you perform content library cleanup, here are some of the requirements to use this tool.

You can run the content library cleanup tool directly on the computer that hosts the distribution point. Most of all you can also run the tool remotely from another server. You can run the tool against a single distribution point at a time.

If you are running this tool then ensure you are a Full Administrator on the Configuration Manager hierarchy. Otherwise you will see the below error.

System.Management.ManagementException: The tool cannot be run using the current user, because the current user does not have the ‘Full Administrator’ RBAC role and ‘All’ scope.

Content Library Cleanup Tool Command Line Options

As I mentioned before the SCCM content library cleanup is a command line tool. So this tool comes with multiple switches and the below table lists all of them.

Content Library Cleanup Tool SwitchDescription
/delete(Optional) Delete the content from DP
/q(Optional) Quiet mode, suppresses all prompts
/dp <DP FQDN>(Required) Specify distribution point FQDN
/ps <Primary Site FQDN>(Optional) Specify the FQDN of primary site the distribution point belongs to
/sc (site code)(Optional) Specify the site code of primary site the distribution point belongs to
/log(Optional) Outputs the result in a log file

Tool Usage

Most of all the tool can be run in two modes What-if mode and Delete mode. When you run the tool in what-if mode, the tool finds orphaned content that can be deleted from DP. However the content is not deleted.

A log file records all this information. You can grab the log file from Temp folder.

When you run the tool in delete mode, the orphaned content is deleted from DP’s content library. Therefore it is recommended that you run the tool in What-If mode first and review the resulting log file before you use the /delete switch.

How to Use Content Library Cleanup Tool in SCCM

Here are the steps to use content library cleanup tool in SCCM.

First of all locate the content library cleanup tool. Look for ContentLibraryCleanup.exe in CD.Latest\SMSSETUP\TOOLS\ContentLibraryCleanup on the site server.

Exploring SCCM ConfigMgr Content Library Cleanup ToolTo run this tool on a distribution point server, copy this tool to the machine. Run the command prompt as administrator. Run the command ContentLibraryCleanup.exe without any switches and you should see the tool usage options.

Exploring SCCM ConfigMgr Content Library Cleanup Tool

To perform the content lib clean up run the below command on a distribution point server :-

ContentLibraryCleanup.exe /dp DP FQDN /log <folder path>

In my case the server has almost no orphaned content on it. This is my lab server so when I run the command in whatifmode, I see very small amount data that is actually stale. As a result there is nothing much to delete from distribution point and hence I see a message that there is no orphaned content that can be freed.

Exploring SCCM ConfigMgr Content Library Cleanup Tool

Furthermore when I check the log file, it states the same thing that there is no content that can be freed.

Exploring SCCM ConfigMgr Content Library Cleanup Tool

In case you got stale content on your distribution point server, you must run the tool in delete mode.

ContentLibraryCleanup.exe  /delete /dp <DP FQDN> /log <log file path>

Exploring SCCM ConfigMgr Content Library Cleanup Tool

The log file shows approx 0 bytes were freed. Since there was no stale content to delete, the message is correct.

Exploring SCCM ConfigMgr Content Library Cleanup Tool

Content Library Cleanup Tool in Action

Now I am going to run content library cleanup on the distribution point server that is in my prod environment. First I run the tool in what-if mode. Type Y to proceed.

Exploring SCCM ConfigMgr Content Library Cleanup Tool

The output shows approx 137,11,835 bytes of data can be freed.

Content Lib Cleanup Tool usage

Finally I run the tool in /delete mode on prod DP server and all the orphaned content is deleted. I have read some comments where some people got errors while running the tool. I will cover the errors in a separate post.

Exploring SCCM ConfigMgr Content Library Cleanup Tool

Note – If you use the older version of the content library tool, then you end up seeing the error. This version of this tool is expired and cannot be used.

Content Lib Cleanup Tool usage

Video Tutorial – Content Library Cleanup Tool

Here is a video tutorial that shows how the configuration manager content library cleanup tool works.

You might also like

39
Leave a Reply

avatar
15 Comment threads
24 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
newest oldest most voted
mohammed irfan siddiqui
Guest
mohammed irfan siddiqui

Dear Rrajwal,

I checked in the path, the file is Content Library Cleanup file is there , but it seems to be corrupted, it is only 1KB and seems to be notepad, please let me know , from where can I download the Content Library Cleanup file ?,

lokesh kumar
Guest
lokesh kumar

sccm 1606 have content library cleanup tool not available under provided location. Please suggest me to download.

lokesh kumar
Guest
lokesh kumar

content library cleanup tool download is not available in sccm 1606 Then how i can download tool.

Naman
Guest
Naman

Hi,
How does the tool look for orphaned content? What exactly does it check and compare to id that a content is actually orphaned. Just interested in knowing what goes on under the hood.

Gwyn Jones
Guest
Gwyn Jones

Had some good success, but now getting this on the majority of DP’s when running the tool.
System.Management.ManagementException: Unable to load valid packages. Please che
ck the specified site server location and ensure you have access to the site ser
ver and the provider. —> System.Management.ManagementException: Quota violatio
n
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStat
us errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.Mo
veNext()
at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.Load
PackageToContentFromProvider()
at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.Load
ValidContentData()
— End of inner exception stack trace —
at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.Load
ValidContentData()
at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary..cto
r(String remoteDPFqdn, String primarySiteServerFqdn, String primarySiteCode)
at Microsoft.ConfigurationManager.ContentLibraryCleanup.Program.Main(String[]
args)

Joe T
Guest
Joe T

I have the same problem. Were you able to find a solution?

John Davis
Guest
John Davis

I have SCCM 2012 R2. I would like to be able to run ConfigMgr Content Library Cleanup Tool but obviously my version doesn’t have it. Do I have to install “Technical Preview version 1612” or later to get my hands on ContentLibraryCleanup.exe, or is it available for download elsewhere. As you stated the tool can be run on SCCM 2012 R2, how can I obtain it?

Danny
Guest
Danny

Not much of an error but more of this tool not working correctly…Reported some orphaned content and I was confirming the deletion one by one but then it didnt look right. On the next package I deleted, I looked in the SCCM console and it was successfully distributed to the DP i was running the tool on. I went ahead and confirmed the deletion of the next orphaned item and then did a validate of the package on that distribution point and came back red…content error. So what exactly is this tool doing or how is it determining the content… Read more »

Hemant
Guest
Hemant

I am getting this error while running from DP as well as Primary server.
Gathering information…
Loading information from distribution point…
System.Management.ManagementException: The tool cannot be run using the current
user, because the current user does not have the ‘Full Administrator’ RBAC role
and ‘All’ scope.
at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary..cto
r(String remoteDPFqdn, String primarySiteServerFqdn, String primarySiteCode)
at Microsoft.ConfigurationManager.ContentLibraryCleanup.Program.Main(String[]
args)

Thinh Ngo
Guest
Thinh Ngo

Hi
Thanks for a nice post!
I have successfully running this tool on DPs
However it failed on Secondary Site with DP role installed. I know this tool cannot run on Primary site, but not on Secondary either?

Matt
Guest
Matt

I am encountering the same problem when trying to run this tool.
I get the error “…cannot be cleaned up right now because package “PR000F5” is not fully installed.
How do I go about making sure that package is seen as complete or working on it please?
(As far as I can see the package is correctly distributed as it has been running fine).
thanks in advance

robp2175
Guest
robp2175

I get this erro “System.InvalidOperationException: This content library cannot be cleaned up righ
t now because package BGR0006D is not fully installed.” I received this error on a couple of other packages and removed them. However, there is no package with this ID in my system. When I run
PS BGR:> Get-CMPackage | select PackageID

PackageID
———
BGR00001
BGR00003
BGR00009
BGR0000C
BGR00014
BGR00015
BGR0001D
BGR00026
BGR0002A
BGR00030
BGR00035
BGR00047
BGR00048
BGR0005A
BGR0005F
BGR00060
BGR00061
BGR00062
BGR00067
BGR00068
BGR00069
BGR0006A
BGR0006F
BGR00075
BGR0007A
BGR0008D

As you can see, no package BGR0006D. Any ideas what to do now? Thanks for any assistance.

Al Din
Guest
Al Din

Can the tool be ran if you are on an older version of CM?
I’m on CM 1606.
What would the effect be if you run the tool in this case?

David Wolf
Guest
David Wolf

Great preview of a useful tool. I’m curious, will the formatting of the bytes that will be deleted be fixed in the Current Branch version? 137,11,835 should be 13,711,835 bytes. Minor annoyance at most, though.

Anders Rødland
Guest
Anders Rødland

So this tool is only in technical preview release now but is to be included in next the production release?

I can see this tool freeing up a lot of diskspace for some of our customers distribution points.

Emiliano Prosseda
Guest
Emiliano Prosseda

The tool crashes if any distribution is inprogress or failed state 🙁

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. AcceptRead More