Currently deployed task sequences create a lot of policy download and slow down the initialisation of a workstation. If they worked like in bootable media, or another way - I don't know if say downloading the TS policies as a zip would help?

when creating a stand alone media, a option to update an existing ISO would be great. also, would be great if you could create an iso and an extract of the iso (like on MDT) so when you copy the files using a slow link connection you only need to copy the changed files and not all files.

the task sequence media has been created for offline scenarios, so the data does not get copied to the sccm. it would be great to have a task sequence media that is online, so all information is also sent and the checks also happen, like a boot image does, the only difference would be instead of downloading the software from the DP it would use the local usb/dvd disk

Setup: Hyper-V Gen2 VM configured with 1GB startup RAM, Min 512MB, Max 4GB.

I was testing servicing Windows 10 1511 to Windows 10 1607 on my VM and the compatibility check failed because the VM was only consuming 1560MB at the time of the compatibility check. I'd think that it would be able to tell if the VM's maximum RAM value was higher than the minimum RAM requirement for Windows 10.

The "Install Software Updates" TS step could use some improvements, including adding an option to run a package after the reboots (before update step continue), and customizing the restart time-out and messages. The status messages are also pretty vague. For example, we know that after it installs the updates it can check for updates again, but it doesn't actually say when it's doing that. I've also noticed some blank black screens showing up for at least a minute as it is about to reboot.

When using the Run PowerShell script step in a Task Sequence, the Task Sequence waits for the completion of the script before continuing.

It would be useful to have a "Run Synchronously" option to allow the Task Sequence to continue to the next step without waiting for the script to complete.

At the moment I use the command line CMD /C START Powershell.exe to achieve this goal.

A computer may be member of several collections. When we deploy multiple task sequences to different collections, available task sequences list changes when computer is booting from PXE. So, we need to check the list order, after deploying new task sequence. Also, first task sequence is selected automatically and users are inclined to select the first one.
It is now alphabetic order, but we should see the list order without booting PXE and maybe we can change the order or set a task sequence to the top.

there should be an option for disable/enable all conditions. For testing or debug, without deleting conditions, we can disable them and then re-enable.

Display the DP the content is coming from in the Progress UI after the % Complete.

"Downloading install.wim (64% complete) from DP: DPOINT01"

Instead of making a dozen If/Then/Set dynamic variable statements, allow some form of creating a switch statement to assign variables.

E.g. if I want to assign a variable based on SMSTSModel
Switch SMSTSModel
case "Latitude 5600"
Set MyVar = "Value"
case "EliteBook G4 840"
Set MyVar = "Value2"
case Default
Set MyVar = ""

There is currently an option to allow the TS step to retry if the computer unexpectedly reboots. Would it be possible to add an option to retry the app installation if it fails, so that the entire TS doesn't fail? Would be useful when there's a network glitch that interrupts an app/pkg download, or if an app just has a hiccup and would have worked fine the second time around.

Desired options would be number of retries and delay between retries (to give the network glitch time to clear itself up for example).

Inside the Apply Driver Package step, it would be useful to be able to insert a variable in order to allow the driver to be applied dynamically based on the vendor or model.