OSD Task Sequence - Install Software failed, hr=0x80008013

Question

I am attempting to add Cyberlink PowerDVD into a Task Sequence to deploy to our Dell desktops.  If I advertise the package to a member of a collection, it will install successfully in a Windows XP environment without any issues.  However, if I add a step in a Task Sequence to install the package, it fails with the following error;
The task sequence execution engine failed executing the action (Install Cyberlink PowerDVD 7.0.0.1024) in the group (Dell) with the error code 2147516435
Action output: Per-system Unattended",PKG_PackageID="DC10009A"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,282)
0, HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,746)
Entering ReleaseSource() for \\server.domain.com\SMSPKGD$\DC10009Areference count 1 for the source \\server.domain.com\SMSPKGD$\DC10009A\ before releasing
Released the resolved source \\server.domain.com\SMSPKGD$\DC10009ApInstall->Install(sPackageID, sProgramName), HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374)
Failed to invoke Execution Manager to Install Software for PackageID='DC10009A' ProgramID='Per-system Unattended' AdvertID='DC1200A9' hr=0x80008013
InstallSoftware failed, hr=0x80008013
Install Software failed, hr=0x80008013.
Any help or ideas would be greatly appreciated.
Thanks in advance.

Answer 1

 bradz123 wrote:
The 0x80008013 is a return result failing to detect that the dependency was installed. I ran into this one myself and have struggled quite a bit with it.
E_FAIL_DEPENDENCY_NOT_RUN 0x80008013
http://technet.microsoft.com/en-us/library/bb632794.aspx
The trouble is that in the OSD, SCCM is not smart enough to detect and run the dependent program, even though all of the data is available and in the database for it to build this information on it's own.
This is a HUGE downfall of the OSD and requires one of a few workarounds.
You can either ensure that the package is installed prior to that one by manually install the dependant application or use the MDT databse add the correct fields.
Another pain in the arse is when you have a package that has a custom action which REQUIRES it to be run on the local drive and not from a network drive which is an even worse beast.
Brad
As a side note to any Microsoft staff out there looking at this, is this ever going to be an option/fix in future releases? You can script it a whole infrastructure to just do this option since everything is already there but it's much less fun that just pointing and clicking, not to mention you have less logging and error control and it's a pain.
If you are taking any suggestions for additional features or functionality I'd add this one and an update to how the driver library functions.
Thanks,
Brad