An update is available to support Alternate Content Provider in Task Sequence in System Center 2012 Configuration Manager

An update is available to support Alternate Content Provider in Task Sequence in System Center 2012 Configuration Manager

  • Comments 1
  • Likes

Capture This article describes an update is available to support Alternate Content Provider in Task Sequence in System Center 2012 Configuration Manager.

In an Operating System Deployment scenario, Distribution Point locations that are stored in task sequence variables are currently inaccessible to Alternate Content Provider. Therefore, applications that are written to use the Alternate Content Provider APIs in System Center 2012 Configuration Manager will be affected.

To support Alternate Content Provider in Task Sequence, this update introduces the SMSTSDownloadProgram task sequence environment variable. The SMSTSDownloadProgram task sequence environment variable is specified as follows:

  • A predefined environment variable that contains the path of the downloader program (.exe file) will be set in the SMSTSDownloadProgram task sequence environment variable.
  • We recommend that you make the downloader program available on the boot image. Therefore, the downloader program can be run securely.
  • During the download process, the task sequence download library will check the environment variable to see whether there is a defined downloader program. If there is, the program will be run in order to perform the download.
  • The following two command line parameters will be passed to the external downloader program:
    • Package ID
    • Absolute path of the download folder

For all the details including a download link, please see the following:

2744420 - An update is available to support Alternate Content Provider in Task Sequence in System Center 2012 Configuration Manager (http://support.microsoft.com/kb/2744420)

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

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security 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
  • Are any more details available?

    Do I have to make any adjustments to my task sequence other than setting the variable to make this works?

    Any logfiles I can look at to see whether this worked?