When deploying a device using Autopilot, the Enrollment Status Page (ESP) is used to prevent access to the desktop until the device provisioning tasks are complete. But ConfigMgr doesn't integrate with the ESP, so there's no way to wait for packages, apps, or task sequences - the user doesn't know when the process is done. Add that integration.

By default you can pause a Task Sequence by adding a step in the TS that will display a msgbox.

It would be cool to be able to pause a TS when you want and as many times you want.

It is possible by changing the ztiutility.vbs file and add the below process:
- Create a new TS variable TSPause
- If this variable is configured to True a msgbox is diplayed

See a post I did about this:
http://www.systanddeploy.com/2020/02/pause-task-sequence-when-you-want-with.html

Split this item from a bigger umbrella item.
This is to specify an icon per App Task Sequence in the Software Center.

When trying to move away from Group Policies to Configuration times/baselines and in every other scenario as well, add a step in Task Sequence to evaluate and remediate select Configuration items/baselines. Then we can select which one of the Configuration Items/baselines should be applied during OSD so the settings are present when the user logs on for the first time

I would like to add setting of LayeredDriver (106/109 key, etc.) during OSD (OS deployment).
These settings are "very important topics" for OSD guys in Japan and Korea.
Without this setting, the keyboard will become an English keyboard.

LayeredDriver [Microsoft Docs]
https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-international-core-winpe-layereddriver

We are seeing a number of unexpected restarts during the "Upgrade Operating System" Windows 10 feature update that causes the task sequence to fail. These restarts are happening during the "setup.exe" phase of the process. Allowing the task sequence to continue would resolve this issue.

The new Model field on drivers is useful, but needs to be extended to other content types, like Packages & Applications, where Model specific items need to be installed (e.g. specific HP SoftPaqs, or video drivers that need to run from .EXE etc).

It would be great if the created application groups can be added in a task sequence.

Instead of having long lists in a task sequense you could manage default apps in the application groups

Having version control for Task Sequences would be invaluable.

If we could link a GitHub account we could easily monitor Task Sequence changes either in Github or SCCM. The ability to roll versions with Administrator approval (similar to publishing scripts) would be ideal.

Expanding on this idea more, highlighting additions/edits/deletes within the Task Sequence dialog would be the icing on the cake.

When Importing a Task Sequence, I'd like the ability added to Import a Duplicate, but it would NOT overwrite the original, it would create a duplicate with modified name and new package ID.

Situation, I've created v1 of the TS and exported for sharing. Others have taken v1 and modified and started to use.
I then export v2 of same TS and made available, others want to import but it will overwrite. Would like the ability to allow others to import v2 without impacting v1.

We have many task sequences, sorted into folders for multiple users, when it comes to archiving them, it's tedious, we'd like to archive multiple task sequences by user (or by folder), this would be great, right now you have to export one task sequence at a time which is tedious.

The essential need to run executable content from package before drive partitioning step (or any other case of unavailability of writable partiotion). "Data Access" package feature seems not working in OSD TS.

Currently you can't create offline media for OS upgrades. I'd like to see an option added where you can create offline media (that you don't need to boot from) that can upgrade an OS. At the moment, you can create standalone bootable media, copy the TS and change every source location/install to a run command.

Kind of hybrid between prestage and standalone. Not everyone connects to 'work' via fast always active links. VPN users over slow links are not currently catered for.

Take the OU path from 'Network Settings" and turn it into a variable e.g. _SMSMachineOUpath
I use dynamic variables to determine the OU based on location and device so my Domain OU path has OU=%devicetype%,OU=Location,OU=workstations,DC=Contoso,DC.com
so it would be nice to have the actual value in a variable that I can reference later say in a script to move existing object to the above created OU. I can see the full path in the SMSTS.log, but not in a variable. Also removing the LDAP:\ from the start could be handy in some situations I guess.

Add an option to only allow a Task Sequence to be run by a user with local administrative rights.

This will allow a Task Sequence to be advertised to systems but ensure that only support staff who have local admin rights can initiate the Task Sequence, preventing standard users from accidentally re-imaging their computer.

In the past we have used the option to 'run another program first' on a Task Sequence and call a script to evaluate the current users groups/permissions, but it would be really useful if this was a native feature.

Stop resolving environmental variables in Unattend.xml; for example, %SystemDrive% is resolved to “X:” which is of no usage in a RunSynchronousCommand. To clarify, TS Variables are fine as they are.

When reimaging a machine it would be most helpful if the machine would retain the name it already has. It greatly annoying that it gets renamed to "Desktop- something or another". Other imaging solutions have this ability (Acronis) without having to do it in some convoluted way; why can't SCCM? Thanks,

I would love to have the option to allow our users to have access to some Task Sequence folders but, not other folders.

I get the option to limit the folders but this prevents them from either being viewed or being copied/modified.

I would like my Task Sequences viewable but not editable. It would be great if users could copy from 'read only' area into their 'test' area and can the create/modify without any risk.

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

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