Orphaned Content Cleanup disrupted when distribution points are offline
Currently on Current Branch 1906. There are times when we have certain pull distribution points offline. When distmgr is attempting to do content cleanup for orphaned content, this cleanup process in distmgr.log is disrupted if it come across an offline pull distribution point. Here is an example where it's deleting fine from server XX and then encounters issues with an offline server YY.
Successfully removed content 889435e8-0ae8-4282-919b-8d078f95b024 from server XX 1/29/2020 7:29:12 AM 13776 (0x35D0)
permanently deleting 29493F5488AD32889C759D1264C33346F5EA60A46C2C1B0DBF5CE69A59870828 1/29/2020 7:29:12 AM 13776 (0x35D0)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba 1/29/2020 7:54:24 AM 13776 (0x35D0)
CWmi::Connect() failed to connect to \YY\root\SCCMDP. Error = 0x800706BA 1/29/2020 7:54:24 AM 13776 (0x35D0)
Failed to remove orphaned content from ["Display=\YY\"]MSWNET:["SMS_SITE=AUS"]\YY\, Error = 0x800706BA 1/29/2020 7:54:24 AM 13776 (0x35D0)
RunContentCleanUp() end. 1/29/2020 7:54:24 AM 13776 (0x35D0)
The negative impact is having our Orphaned content SQL tables (OrphanedContents and OrphanedContentsDP) grow. We have tried putting the offline pull distribution in DP maintenance mode, but the errors continues and the content cleanup is disrupted.
Can we please have content cleanup skip servers that are offline or at minimum skip the server if it's in maintenance mode?
Please fix this.
Chad Simmons commented