Applications are absolutely supported and working in the task sequence. And we're continuing to improve the experience with each release based on customer feedback. There are some improvements in the upcoming service pack, and we're targeting additional work for vNext as well. A few additional feedback items that are on our radar and we're investigating: picking a specific deployment type from the task sequence, or picking an application that has a user targeted deployment type. There are still some specific instances in which a really fast device (like with an SSD) can't properly detect its location fast enough after a reboot.
If there's anything else that's causing folks issues with using applications in the task sequence, PLEASE file feedback on Connect. We can't code changes against rumors, only bugs. :) We want to enable customers to be successful with applications via direct deployments as well as via task sequences, without having to resort to legacy packages or even worse IMO, duplication. Aaron From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, May 13, 2015 10:47 AM To: [email protected] Subject: [mssms] Question from the Ignite Conference Hello I vaguely remember hearing that CM2012 will have difficulty installing/provisioning "Applications" (in task sequences) in Windows 10 as well as Office 365 indicating Task Sequences have issues reading the rules associated with those Applications. As I remember they indicated this will NOT be fixed until ConfigMgr 2016 is released. Can anyone corroborate or provide additional information about this? Thanks
