I didn't get any response under the SMS Mailing List so I thought I'd try with the MDT/OSD mailing list in case others have seen this issue with Task Sequences.
Thanks, Edward From: [email protected] [mailto:[email protected]] On Behalf Of Edward Woo Sent: Friday, July 19, 2013 1:59 PM To: [email protected] Subject: [mssms] Task Sequence for Software Install Fails to Run if Created on SCCM 2007 Central Site Hi All, This issue was raised by one of our team members and I can't seem to determine why it is failing. He's created a Task Sequence to deploy several programs one after the other. The packages are created on the Central site and package contents replicated to distribution points at the various child primary sites. The Task Sequence is advertised with the following settings: [cid:[email protected]] When the Task Sequence is advertised to the clients in the child primary site, the task sequence fails with: The program for advertisement "xxx1208E7 has failed because download of the content "xxx00160" - "*" has failed. The download failed because the content downloaded to the client does not match the content specified in the content source. This error occurs whether I create the advertisement on the Central Site or child Primary Site servers. If I deploy the same packages normally with a regular advertisement, the programs all download and install on the client so I know the packages and its contents are good. Most solutions I've searched online appear to point to refreshing the package contents to regenerate the hash, but if a normal advertisement works with the same content, the hash should be fine. Looking at the execmgr.log file, I see errors like: OnContentAvailable program * NOT available, 0x80091007 OnContentAvailable invalid request GUID handle The Task Sequence was then recreated on the child primary site server and the packages recreated on the child primary site server. When the task sequence is advertised to the clients using the same settings, it works fine. What's been reported so far is that whatever Task Sequence is created to deploy software created on the Central Site, they all generate the above error even though the contents resides on the child sites. If the task sequence is created on the child site along with the packages, it works fine. I was hoping some of you may have encountered a similar situation and may know where I should look to diagnose this particular issue or if this is a known issue. Thanks, Edward Woo
<<inline: image001.png>>
