This post has been republished via RSS; it originally appeared at: Configuration Manager Archive articles.
First published on TECHNET on Dec 15, 2016Consider the following scenario:
- You're running Configuration Manager current branch, version 1511 through 1606, or version 1610 LTSB.
- Your old primary site was being used for client piloting.
- You perform site expansion.
In this scenario, the Configuration Manager Client Piloting Package fails. When this occurs, you 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.
We have a new KB article that describes this issue as well as how to work around it. For more information please see the following:
3205797 - Client piloting package fails after site expansion in Configuration Manager ( https://support.microsoft.com/en-us/kb/3205797 )
J.C. Hornbeck
, Solution Asset PM
Microsoft Enterprise Cloud Group