Task Sequences should be supported outside of operating system deployment scenarios
Task sequences are only officially supported in operating system deployment scenarios. Task sequences are incredibly useful with their explicit logic and tight control. There's many cases where it can be useful to deploy task sequences outside of operating system deployment scenarios for complex software deployment scenarios.
Task sequences should be made a first class citizen outside of operating system deployment scenarios.
With ConfigMgr 1511, we now support non-OSD Task Sequences according to the following https://technet.microsoft.com/en-us/library/mt627920.aspx
Karin Hall commented
Would also be helpful if there is notification at the logon screen that shows the task sequence is running. To be used for non-OSD task sequences when a reboot is required or no user is logged on so the progress is not interrupted.
Jason Darst commented
I agree. We often go to deploy multiple pieces of software together and we want to control the order to ensure things install in a tested and controlled way. Task sequences would be great for this.
this would be more as helpfull.
I agree. Please give Task Sequences the attention they deserve. To add to this... allow us specify an icon when deploying a task sequence the same way we can with a standard application deployment. The custom icons in the software center make all the difference.
I agree completely. Task Sequences should be a Deployment Type. Should also be how we deploy Software Updates so we can have pre and post actions, like stop and start services, perform a reboot before installing updates, possibly run some validation scripts, runbooks, etc.
Manuel Müller commented
Plus, there should be an option to block user input.
i have no votes left , but i second this !