3

My SCCM hierarchy has three Distribution Points and I am adding a fourth.

The new Distribution Point is added successfully, and when I check Content Status I see that all of my content items are now properly targeting all four Distribution Points, with the exception of one package:

  • Microsoft Corporation Configuration Manager Client Piloting Upgrade Package

This package still only targets the original three.

When browsing through the Packages list (via Software Library | Packages) this Package is not visible.

Using PowerShell, Get-CMPackage with the ID of this package returns nothing. Likewise Get-CMPackage | ft PackageId doesn't list the package ID (it does list my other packages correctly).

How do I amend this package to target the new fourth Distribution Point?

Swisstone
  • 6,725
  • 7
  • 22
  • 32
Maximus Minimus
  • 8,987
  • 2
  • 23
  • 36
  • Is there any info referring to it in distmgr.log or despool.log? – Crimsonfox Aug 04 '21 at 14:36
  • @Crimsonfox - no, not in either. Confirming also that I've searched for the package by ID, not by name, and that my other packages are present, likewise by ID, not name. – Maximus Minimus Aug 04 '21 at 15:30
  • Does it show in the Content Library Explorer? – Crimsonfox Aug 04 '21 at 16:44
  • @Crimsonfox - yes on the 3 previously-existing distribution points, no on the new one. – Maximus Minimus Aug 05 '21 at 09:58
  • Have you tried this: https://www.vansurksum.com/2012/11/25/configmgr-2012-what-to-do-when-the-configuration-manager-client-upgrade-package-is-deleted-somehow/#comment-4511 but renaming ccmsetup in the the PilotingUpgrade folder too? – Crimsonfox Aug 05 '21 at 10:41
  • Actually, instead of adding the client.acu file, try CliUpg.acu, that should recreate the packages as opposed to just redistributing them. Also, check if there is any reference in DataTransferService.log or PkgXferMgr.log. – Crimsonfox Aug 06 '21 at 18:54

1 Answers1

-1

In the absence of a documented solution from Microsoft outlining the procedure for redistributing this package, and explaining what it is and why it appears the way it does, I have decommissioned the new Distribution Point and will engage Microsoft Support for the next steps.

Maximus Minimus
  • 8,987
  • 2
  • 23
  • 36