Before I go on, I have a very experienced packager/re-packager working for me, who full understands MSIs, exit codes, logging and transforms etc. Neither of us can explain the following.
Scenario: Config Manager 2012 R2 w/ UDI MDT 2013 pages during Task Sequence. Two applications that haveConfiguration Manager client will force a mandatory device restart set.
Issue: Since my upgrade to R2 SP1 it seems this reboot causes anyproceeding dynamic list applications (i.e. COALESCEDAPPS) to not then install. They never start. AppDiscovery/Enforce/smsts and install log files generated by both applications indicate a return code of 0 as expected and then...that's it. The TS doesn't pick up again, instead rebooting into the login screen. Prior to R2 SP1 this didn't happen, the TS continued on after reboot and installed the remaining applications.
There is one caveat here: Neither my packager nor I even remember ever setting this option since we pretty much rely on the correct exit codes to implement behaviour and not User Experience set to a restart is required. Checking the Revisions shows these Applications having Configuration Manager client will force a mandatory device restart set right from the off but I really, really question that, since I *know* for certain one of the Applications doesn't require any kind of restart in order for it to work.
Shouldn't the TS pick up again regardless of the UEx set as mandatory restart anyway?
I have seen a reply to a similar post stating: An unexpected reboot during the TS often kills it so you need to configure your command-line to prevent this. ConfigMgr cannot override what an MSI actually does internallybut this isn't an unexpected reboot!
Thanks all, Nick