Hi Daniel - I think this hotfix is specific to SP1, although the issue does occur in R2 as well. Sustained engineering is already tracking a fix for R2 (but don't ask me when, I don't know). The following is the key log entry in execmgr.log:
ContentProgressEx invalid request GUID handle The following Connect item lists some options to workaround: https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/813943/pfe-client-stuck-at-0-downloading-for-swdist-based-task-sequences. I think switching to download on demand is another workaround. Aaron p.s. is this the issue we discussed at TechEd? From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, May 27, 2014 12:49 PM To: [email protected] Subject: [mssms] HOTFIX: A command-line action that has a linked package doesn't start in ConfigMgr 2012 OSD FYI The issue is that a Task Sequence (TS) doesn't start as expected in System Center 2012 Configuration Manager (ConfigMgr 2012). This issue occurs if the Run Command Line Action sequence step has a link to a package, and the deployment for the task sequence has the Download all contents locally before starting task sequence configuration applied to it. This problem occurs only if multiple task sequences include the same package and the package has a larger source size. http://blogs.technet.com/b/configurationmgr/archive/2014/05/27/hotfix-a-command-line-action-that-has-a-linked-package-doesn-39-t-start-in-system-center-2012-configuration-manager.aspx http://support.microsoft.com/kb/2961924 Hoping to get clarification on whether this only affects SP1 or is R2 affected as well. Daniel Ratliff The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
