HOTFIX: An Alternate Content Provider does not work in a task sequence for a System Center 2012 Configuration Manager SP1 site

HOTFIX: An Alternate Content Provider does not work in a task sequence for a System Center 2012 Configuration Manager SP1 site

  • Comments 2
  • Likes

download5331Consider the following scenario:

- 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:

KB2870742  - FIX: An Alternate Content Provider does not work in a task sequence for a System Center 2012 Configuration Manager SP1 site (http://support.microsoft.com/kb/2870742)

J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

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

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

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/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I'm trying to install this hotfix as part of my OS deployment task sequence and it's not working.  I continue to get the error "The sms client service is not running" when trying to install the patch.  I've tried at various points during the deployment process and it does not seem to matter.  Is there guidance available for adding this patch during a task sequence deployment?

  • Old Post I know, but...

    You're probably better off detecting it on all your clients and having an ongoing deployment to all your clients so they get it in the next Maintenance Window.  I try not to over complicate my OSD too much.  That being said, it would of course, if you install it as a SCCM Application or Package, have to go after a step that you added from Add->Images->"Setup Windows and ConfigMgr", so that the client would be installed and running.