Content library cleanup tool
Applies to: System Center Configuration Manager (Current Branch)
Use the content library cleanup command-line tool to remove content that's no longer associated with any package or application on a distribution point. This type of content is called orphaned content. This tool replaces older versions of similar tools released for past Configuration Manager products.
The tool only affects the content on the distribution point that you specify when you run the tool. The tool can't remove content from the content library on the site server.
Find ContentLibraryCleanup.exe in
CD.Latest\SMSSETUP\TOOLS\ContentLibraryCleanup on the site server.
Only run the tool against a single distribution point at a time.
Run it directly on the computer that hosts the distribution point to cleanup, or remotely from another computer.
The user account that runs the tool must have permissions the same as the Full Administrator security role in Configuration Manager.
Modes of operation
Start with the what-if mode. When you're satisfied with the results, then run the tool in delete mode.
If you don't specify the
/delete parameter, the tool runs in what-if mode. This mode identifies the content that would be deleted from the distribution point.
When run in this mode, the tool doesn't delete any data.
The tool writes to the log file information about the content that it would delete. You're not prompted to confirm each potential deletion.
When you run the tool with the
/delete parameter, the tool runs in delete mode.
When run in this mode, orphaned content that it finds on the specified distribution point can be deleted from the distribution point's content library.
Before deleting each file, confirm that the tool should delete it. Select Y for yes, N for no, or Yes to all to skip further prompts and delete all orphaned content.
When the tool runs in either mode, it automatically creates a log. It names the log file with the following information:
- The mode the tool runs in
- The name of the distribution point
- The date and time of operation
When the tool finishes, it automatically opens the log file in Windows.
By default, the tool writes the log file to the temp folder of the user account that runs the tool. This location is on the computer where you run the tool, which isn't always the target of the tool. Use the
/log parameter to redirect the log file to another location, including a network share.
Run the tool
To run the tool:
Open a command prompt as an administrator. Change directory to the folder that contains ContentLibraryCleanup.exe.
Enter a command line that includes the required command-line parameters, and any optional parameters you want to use.
Use these command-line parameters in any order.
||Specify the fully qualified domain name (FQDN) of the distribution point to clean.|
||Required only when cleaning content from a distribution point at a secondary site. The tool connects to the parent primary site to run queries against the SMS Provider. These queries let the tool determine what content should be on the distribution point. It can then identify the orphaned content to remove. This connection to the parent primary site must be made for distribution points at a secondary site because the required details aren't available directly from the secondary site.|
||Required only when cleaning content from a distribution point at a secondary site. Specify the site code of the parent primary site.|
Example: Scan and log what content it would delete (what-if)
ContentLibraryCleanup.exe /dp server1.contoso.com
Example: Scan and log content for a DP at a secondary site
ContentLibraryCleanup.exe /dp server1.contoso.com /ps siteserver1.contoso.com /sc ABC
||Use this parameter when you're ready to delete content from the distribution point. It prompts you before it deletes content.
When you don't use this parameter, the tool logs results about what content it would delete. Without this parameter, it doesn't actually delete any content from the distribution point.
||This parameter runs the tool in a quiet mode that suppresses all prompts. These prompts include when it deletes content. It also doesn't automatically open the log file.|
||Optional only when cleaning content from a distribution point at a primary site. Specify the FQDN of the primary site that the distribution point belongs to.|
||Optional only when cleaning content from a distribution point at a primary site. Specify the site code of the primary site that the distribution point belongs to.|
||Specify the location where the tool writes the log file. This location can be a local drive or a network share.
When you don't use this parameter, the tool places the log file in the user's temp directory on the computer where the tool runs.
Example: Delete content
ContentLibraryCleanup.exe /dp server1.contoso.com /delete
Example: Delete content without prompts
ContentLibraryCleanup.exe /q /dp server1.contoso.com /delete
Example: Log to local drive
ContentLibraryCleanup.exe /dp server1.contoso.com /log C:\Users\Administrator\Desktop
Example: Log to network share
ContentLibraryCleanup.exe /dp server1.contoso.com /log \\server\share
When any package or deployment has failed, or is in progress, the tool might return the following error:
System.InvalidOperationException: This content library cannot be cleaned up right now because package <packageID> is not fully installed.
There's no workaround for this issue. The tool can't reliably identify orphaned files when content is in progress or has failed to deploy. The tool won't allow you to clean up content until you resolve that issue.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.