Hi We currentlly have an R3 install of SCCM that has been updated to MDT 2010 Update 1. All Operating System installs that were built using the orginal version of MDT 2010 still work. Task Sequences that have been created with MDT 2010 Update 1 fail on installing applications with the error: The task sequence execution engine failed executing the action (Adobe Acrobat Reader X) in the group (Adobe Applications) with the error code 2147491844 Action output: Distribution.ADV_AdvertisementID="PMO201A8",PRG_ProgramID="Install",PKG_PackageID="PMO0010D"' Verified policy is compiled in 'root\ccm\policy\machine' namespace content location count = 1 Invoking Execution Manager to install software FALSE, HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,282) 0, HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,746) Entering ReleaseSource() for \\SERVER1.DOMAIN.CORP\SMSPKGP$\PMO0010Dreference count 1 for the source \\SERVER1.DOMAIN.CORP\SMSPKGP$\PMO0010D\ before releasing Released the resolved source \\SERVER1.DOMAIN.CORP\SMSPKGP$\PMO0010DpInstall->Install(sPackageID, sProgramName), HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374) Failed to invoke Execution Manager to Install Software for PackageID='PMO0010D' ProgramID='Install' AdvertID='PMO201A8' hr=0x80002004 InstallSoftware failed, hr=0x80002004 Install Software failed, hr=0x80002004. The operating system reported error 1: Incorrect function. What could be the cause of this?

I am wondering if it is the firewall? Double checking this now.

I assume you mean that you are trying to run a task sequence from SCCM (with MDT integrated). Are all the applications failing during the task sequence? If so can you check ccmexec.log (to see if the client is even running) and the execmgr.log (to get more information about the failing applications).My Blog: http://www.petervanderwoude.nl/

All client activity in ConfigMgr is client intitiated so unless you have a software firewall configured to block outbound traffic or a hardware firewal in place it's not the firewall. Also, if the the firewall were blocking one thing, it would block everything so we should be able to safely rule that out. Is the Adobe Reader X package new? If so, did you check the check box at the bottom of the Program Advanced tab says something like allow this program to be installed even if not advertised? And finally, there is no such thing as Acrobat Reader; hasn't been called that for around 10 years. It's Adobe Reader without the Acrobat because it reads many different formats now. (Sorry just a huge pet peeve of mine).Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi it is failing for all software, on the windows 7 image, but not failing for a windows xp image. regards

All applications are set to be distrubted as part of an OS Deployment, as some of these applications we distributed to our XP image, and they are compatiblity with Winodws 7

Error code 80002004 = "The software distribution policy was not found." This imples there is something wrong with your advertisements or programs like they are expired or only targeted at XP systems. Have you tried to create a clean, test package and program to see if it works in the TS?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi, Please go to check the ExecMgr.log to see if it failed to find the policy for the above package/ program. If so, it can be caused by the Software Distribution Advertisement or the Task Sequence Advertisement got Expired. Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Check the package and make sure you allow it to run on windows 7, it sound like you have only allowed it to run on XP. Louis

Hi Just an update, a normal configmgr osd sequence will run through successfully and install applications with no problem. It just seems to be ones newly created with MDT. Existing ones with created with MDT are fine. Now my understanding is that you can update MDT 201 to MDT 2010 Update 1 with no issues and still use task sequences that were created with the orginal version of MDT. (Please note that this is a problem with new MDT task sequences created after the update and ones MDT 2010 RTM that have been modifed after) Regards

If you have updated MDT ,Its my understanding that you need to create new tool kit packages to use the newley created task sequences steps, have you done this?

Yes I have, I am wondering whether to completely uninstall MDT (all Versions, if hte uninstall of Update 1 leaves RTM on the machine afterward), then install Update 1 on its own?

It general you can just upgrade MDT 2010 to MDT 2010 Update 1, but there are a few exceptions, see: http://blogs.technet.com/b/mniehaus/archive/2010/07/08/quick-notes-about-mdt-2010-update-1-released-today.aspxMy Blog: http://www.petervanderwoude.nl/

Hi, Regarding the MDT upgrade, it is also recommended to post a new thread in Microsoft Deployment Toolkit Forum for discussion. Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.