Hi everyone. Seeing some strange (we think) behavior when we are deploying a task sequence containing applications.
SCCM 2012 RTM (no SP1 - we're in the process of planning that upgrade to overcome some other bugs we ran into)
TS Scenario:
1.) Uninstall application (cmd line)
2.) Reboot
3.) Install application (application with supersedence relationship - however, we are manually uninstallaing as part of the TS)
4.) Reboot
Deployment timing: Available (start time): tonight 8pm
Assignment time: 2 days out from now @ 8pm
Observed behavior: After the deployment has been submitted, the targeted systems pick up policy, and we see AppIntentEval start processing the application install referenced - sees supersedence in effect, etc. Fine? OK, well AppEnforce then comes in during the nightly maintenance window and actually ACTS on the application supersedence and uninstalls the superseded application.
The superseded app has a forced configmgr restart, so at the maintenance window, it restarts and then the new app is installed.
Keep in mind this is all before the TS has run!
When the TS assignment time hits, the TS runs and fails on removal (already removed), which we have ignored and then proceeds to install (enforce what's already installed).
As a "workaround" we have set our deployment availability and assignment times a few seconds apart, so App enforcement doesn't jump the gun per se and that seems to work.
We've already verified that there are no other deployments of the superseded application that are causing this.
Is this the way SCCM handle application installs inside a TS?
I can live with policy coming down and AppIntent knowing something is in the pipeline, but I don't like that the application is enforced ahead of the TS running...
Thanks for any feedback.
Steve