In my customers SCCM 2012 environment I have noticed a nice little Bug in SCCM 2012.
In a SCCM 2012 Task Sequence, we have a Task Sequence Step, which installs SCCM-Applications by using a variable list.
At this Step, the Task Sequence stops with the following error in SMSTS.log:
App policy for ‘Test-Application’ not received. Make sure the application is marked for dynamic app install
Policy download failed, hr=0x80004005
Failed to run the action: Install Application.
Unspecified error (Error: 80004005; Source: Windows)
After doing some research I found out that, the MDT 2013 Integration was the Problem.
If you have created some SCCM-Application and implement those in a Task Sequence to install the SCCM-Applications by using variable list
all things will run well.
However, if you perform a MDT 2013 integration after that, you will fall in to the bug showing above in the SMSTS.LOG, and your TS will failed.
There is no Bug fix provided by Microsoft. The three things you can do to work around that issue:
- Do not integrate MDT in SCCM 2012
- Create your SCCM-Application after your MDT integration
- Re-create or copy your SCCM-Applications with MDT integrated.