Client piloting package fails after site expansion in Configuration Manager

Applies to: System Center Configuration Manager (current branch - version 1511)System Center Configuration Manager (current branch - version 1602)System Center Configuration Manager (current branch - version 1606)


Consider the following scenario:
  • You're running Configuration Manager current branch, version 1511 through 1610 or version 1606 LTSB.
  • The old primary site was being used for client piloting.
  • You perform site expansion.

In this scenario, the Microsoft Corporation Configuration Manager Client Piloting Package fails. You may receive a status message stating that Distribution Manager failed to access the source directory for Configuration Manager Client Piloting Package content. Additionally, the Distmgr.log file contains errors indicating that Distribution Manager cannot locate the source for PilotUpgrade and cannot process the snapshot of the package.


This issue occurs if the PilotingUpgrade and StagingClient folders are missing from the new CAS.


To work around this issue, manually create the StagingClient folder on the new CAS, and then create an empty file named CliUpg.acu in the folder on the CAS. This will trigger an update of the client packages by Hierarchy Manager.