Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM | Configuration Manager

Learn how to Remove ConfigMgr Package Content from a Distribution Point (DP). I have seen several issues with the content distribution of SCCM packages. The package content distribution failure could be because of several reasons and I have given some examples in the below paragraph of this post.

The first troubleshooting step to resolve content transfer failures is to remove content to the problematic distribution point(s). In this post, you will learn how to remove the ConfigMgr package content to individual DPs from the admin console.

The following posts might help to understand related issues with content distribution. Learn about Fix ConfigMgr DP Issue RPC server is Unavailable Error Code 0x800706ba, Fix SCCM SendFiles Failed 0x80070003 Error, and How to ConfigMgr Redistribute Content to Distribution Point.

Remove Content

Let’s assume you have already distributed the content to distribution points. But the content distribution failed. The removal action (as part of troubleshooting) makes sure all the source files are removed from the distribution point or distribution point group. The following is one of the troubleshooting steps to fix content distribution issues.

Patch My PC
  • Remove the content.
  • Wait for an ample amount of time (review log files).
  • Add the content back to the distribution point.

As I mentioned above, this removal action helps to resolve content distribution-related issues for a particular package. You can remove the content from different places in the admin console. More details in the below sections.

Software Library – Remove ConfigMgr Package Content

Removal action from the Software library is the first and most commonly used method to repair or fix the content distribution issue of a particular package or application. This action is very useful when you are troubleshooting the distribution issues of a single package/application.

Let’s check how to Remove package or application content from a Distribution Point.

1E Nomad
  • Navigate to the Software Library workspace.
  • Select the content types that you want to remove.
    • You can choose any type of distributed content available in the software library
      • Package
      • Applications (CMPivot)
      • Software Update
      • Boot Image
      • Operating System Images
      • Etc…
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
  • On the Home tab of the ribbon, in the Properties group, select Properties.
  • Click on the Content Locations tab.
  • Select the distribution point (or distribution point group) that you want to remove the content.
  • Click on the Remove button.
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
  • Click OK on the warning window to initiate the removal of the package content.

Administration workspace – Remove Package Content Option

The removal option from Administration workspace distribution point properties is a good option when a particular DP has issues with content distribution for many packages/applications.

Let’s check how to Remove ConfigMgr Package Content from DP properties.

  • Navigate go to the Administration workspace.
  • Select the Distribution Points node.
  • Select the distribution point to which you want to remove content.
  • Click on the Home tab of the ribbon.
  • In the Properties group, select Properties.
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
  • Select the Content tab.
  • Select the content to remove.
  • Click on the Remove button.
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
  • Click OK on the warning window to initiate the removal of the package content.

Best Place to Remove Package

Here you go! As per my experience, the following is the best method to Remove ConfigMgr Package Content for different workloads or deployment packages in SCCM.

  • Navigate to \Monitoring\Overview\Distribution Status\Content Status
  • Use the search bar to find any deployment packages like Application, Task Sequence, Boot Image, or Software Update.
  • Select one particular package (CMPivot) that you want to remove.
  • Right-click and select View Check the View Status option.
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
  • Select the DP where you have an issue with package replication.
  • Right-click on the DP and click on Remove.
  • Click OK on the warning window to initiate the removal of the content.
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM

SMSProv.log Process

Veeam Windows 10
Advt

You can refer to SMSProv.log (SMS Provider log @primary server where the console is installed) snippet to give you an overview of Package removal. The following log entries might help you to troubleshoot and confirm whether the removal really worked for you or not.

DeleteInstanceAsync SMS_DistributionPoint.PackageID="MEM00023",ServerNALPath="[\"Display=\\MEMCMSecondary.memcm.com\\"]MSWNET:[\"SMS_SITE=HS0\"]\\MEMCMSecondary.memcm.com\",SiteCode="HS0"
  • Requested class =SMS_DistributionPoint
  • Requested num keys=3
  • IExtClassManager::ValidateAuthenticationLevel…
  • CExtProviderClassObject::DoDeleteInstance
  • Auditing: User MEMCM\anoop deleted an instance of class SMS_DistributionPoint.
  • CExtUserContext::LeaveThread : Releasing IWbemContextPtr=605966976
  • ExecQueryAsync: START SELECT * FROM SMS_DistributionStatus WHERE PackageID = ‘MEM00023‘ AND Type = 2
  • Execute WQL =SELECT * FROM SMS_DistributionStatus WHERE PackageID = ‘MEM00023‘ AND Type = 2
Execute SQL =select all SMS_DistributionStatus.Assets,SMS_DistributionStatus.LastUpdateDate,SMS_DistributionStatus.MessageCategory,SMS_DistributionStatus.ObjectID,SMS_DistributionStatus.ObjectTypeID,SMS_DistributionStatus.PackageID,SMS_DistributionStatus.Type from vSMS_DistributionStatus AS SMS_DistributionStatus where (SMS_DistributionStatus.PackageID = N'MEM00023' AND SMS_DistributionStatus.Type = 2)
  • ExecQueryAsync: COMPLETE SELECT * FROM SMS_DistributionStatus WHERE PackageID = ‘MEM00023’ AND Type = 2
  • ExecQueryAsync: START SELECT * FROM SMS_DistributionStatus WHERE PackageID = ‘MEM00023’ AND Type = 1
  • Execute WQL =SELECT * FROM SMS_DistributionStatus WHERE PackageID = ‘MEM00023‘ AND Type = 1
Execute SQL =select all SMS_DistributionStatus.Assets,SMS_DistributionStatus.LastUpdateDate,SMS_DistributionStatus.MessageCategory,SMS_DistributionStatus.ObjectID,SMS_DistributionStatus.ObjectTypeID,SMS_DistributionStatus.PackageID,SMS_DistributionStatus.Type from vSMS_DistributionStatus AS SMS_DistributionStatus where (SMS_DistributionStatus.PackageID = N'MEM00023' AND SMS_DistributionStatus.Type = 1)
  • ExecQueryAsync: COMPLETE SELECT * FROM SMS_DistributionStatus WHERE PackageID = ‘MEM00023’ AND Type = 1
  • Execute WQL =SELECT * FROM SMS_DistributionDPStatus WHERE PackageID = ‘MEM00023’ AND MessageCategory = ‘121’
Execute SQL =select all SMS_DistributionDPStatus.GroupCount,SMS_DistributionDPStatus.ID,SMS_DistributionDPStatus.InsString1,SMS_DistributionDPStatus.InsString10,SMS_DistributionDPStatus.InsString2,SMS_DistributionDPStatus.InsString3,SMS_DistributionDPStatus.InsString4,SMS_DistributionDPStatus.InsString5,SMS_DistributionDPStatus.InsString6,SMS_DistributionDPStatus.InsString7,SMS_DistributionDPStatus.InsString8,SMS_DistributionDPStatus.InsString9,SMS_DistributionDPStatus.IsPeerDP,SMS_DistributionDPStatus.LastStatusID,SMS_DistributionDPStatus.LastUpdateDate,SMS_DistributionDPStatus.MessageCategory,SMS_DistributionDPStatus.MessageFullID,SMS_DistributionDPStatus.MessageID,SMS_DistributionDPStatus.MessageSeverity,SMS_DistributionDPStatus.MessageState,SMS_DistributionDPStatus.NALPath,SMS_DistributionDPStatus.Name,SMS_DistributionDPStatus.ObjectID,SMS_DistributionDPStatus.ObjectTypeID,SMS_DistributionDPStatus.PackageID,SMS_DistributionDPStatus.ResourceType,SMS_DistributionDPStatus.SiteCode from vSMS_DistributionDPStatus AS SMS_DistributionDPStatus where (SMS_DistributionDPStatus.PackageID = N'MEM00023' AND SMS_DistributionDPStatus.MessageCategory = N'121')
  • ExecQueryAsync: COMPLETE SELECT * FROM SMS_DistributionDPStatus WHERE PackageID = ‘MEM00023’ AND MessageCategory = ‘121’
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM

DistMgr.log – Package Content Removal Process

You can refer to DistMgr.log (@ secondary server) snippet to get an overview of Package removal process. The following log entries might help you to troubleshoot and confirm whether the removal really worked for you or not.

NOTE! – The package MEM00023 is removed from secondary server DP. So, I have not seen any activity on the primary server DistMgr.log.

  • Adding package ‘MEM00023’ to package processing queue.
  • Started package processing thread for package ‘MEM00023’, thread ID = 0x1698 (5784)
  • \?\C:\SMSPKGSIG\MEM00023.1 could not be located
  • GetContentLibLocation – MEMCMSecondary.memcm.com
  • Finished GetContentLibLocation – MEMCMSecondary.memcm.com
  • GetDPUsableDrives – [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com\
  • Finished GetDPUsableDrives – [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com\
  • Start deleting package MEM00023 from server [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com…
  • Created DP processing thread 5496 for removal of package MEM00023 on server [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com\
  • Waiting for all DP threads to complete for package MEM00023 processing thread.
  • Attempting to remove package MEM00023 from distribution point [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com\
  • [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com\ is NOT a Pull DP
  • Successfully removed the package MEM00023 from server [“Display=\MEMCMSecondary.memcm.com\”]MSWNET:[“SMS_SITE=HS0”]\MEMCMSecondary.memcm.com\
  • CStateMsgReporter::DeliverMessages – Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\xam510ne.SMX
  • Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
  • Exiting package processing thread for package MEM00023.
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM
Remove ConfigMgr Package Content from a Distribution Point | Best Method | SCCM

Check the SCCM log files related to DPs. The PkgXferMgr.log file is your best friend for remote DP distribution/package replication issues.

distmgr.logPackage Application distribution process
PkgXferMgr.logRecords the actions of the SMS_Executive component that is responsible for sending content from an SCCM primary site to a remote DP.
Package Content Removal

NOTE! – The PkgXferMgr.log is the log file that you need to check to understand how removal works for remote DPs.

Resources

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.