- You configure an application that takes advantage of the Alternate Content Provider (ACP) to distribute packages in a Microsoft System Center 2012 Configuration Manager Service Pack 1 (SP1) site.
- You create a task sequence that includes an "Install Application" step.
- You include a single application in the step.
- You specify the following options, and then you deploy the task sequence:
- Download all content locally before starting task sequence
- When no local distribution point is available, use a remote distribution point
- Allow clients to use a fallback source location for content
- A client receives the policy for deployment, and then begins to process the task sequence according to schedule. Or, you click Install for the task sequence deployment in Software Center on the client.
In this scenario, the ACP is not invoked in the ContentTransferManger.log file when you download the content.
There is a new downloadable hotfix available for this issue and you can get all the details here:
J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division
System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/