For the task sequence steps make it easier to arrange the steps. Constantly have issues moving a step up the the chain steps to the top level group.

The problem:
When multiple admins are working on OSD Task Sequences, it is not obvious to see if a boot image is being called by a TS without going into the Properties of every single TS. This is exacerbated by WIMs created outside of SCCM, as is the case with MDT Boot images.

Suggestion:
Add "Referenced by Task Sequence" item to Boot Image Summary or Details tab.

OS Upgreade TS: Add percentage complete next to the install bar. It would be easier to keep tabs on the installations.

Please hide the DOS Box with setupcomplete.cmd in the Task Sequence Windows 10 Upgrade process.

Allow you to be able to paste in an unattend.xml file directly into the Apply Operating System Image task sequence step instead of having to use a package. Similar to how you can add a PowerShell script directly in to the task sequence step in SCCM 1902.

The new step which lets you run powershell scripts in a task sequence have an open and a browse button. It would be awsome if a button was added which lets us select a configuration items remediation item (script or registry or w/e).

This way we can set up the machine the same say we do after it has its client configured but we dont need to add startup scripts or services to fix this before first logon.

In these days of huge USB drives, it would be really beneficial to be able to boot from USB media, then capture the .wim to that same media, rather than to a network location (which we don't have on many machines). Thank heaps.

The MDT OSD "Execute RunBook" Task is cannot connect to Orchestrator once Orchestrator is moved to https with the error "Unable to connect to Orchestrator web service"

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.

Allow language localization on task sequence User Notifications like we have for applications. currently if you change the default task sequence user notifications, they only show in the language they were entered in, not the users localized language. Same for making the task sequence name, in localized language

It would be very useful to be able to control if a Task Sequence has been "Installed" or not by adding a custom detection method like we have in the AppModel.

This is valid in scenarios where we do a bare metal required rollout and in in-place-upgrade scenarios. Combined with having different versions of a task sequence being deployed.

This Cmdlet does not support using a cloud distribution point as the distribution point source (and neither does the GUI).

This means that in order to use this feature we have to have an on-premise DP purely for this purpose.

Regards
Wayne

When a specific app or utility needs to be run (ex. a custom monitoring application) after each restart, it would be handy if we could put the command in a variable. The command should then be executed after each restart, before the TS continues.

Organizations prefer implementing a standard start menu and taskbar layout across all end user devices. There are powershell scripts available to achieve this during build sequence. However, it will be nice to have a built in feature\step in the TS to perform this. Also, with Windows 10 upgrades\servicing, I have seen issues with these layouts being reset to defaults. It may be worth adding a Windows 10 workspace of its own in the ConfigMgr console for creating customization policies and deploying them in conjunction with Compliance settings.

Driver pack life cycle management, This would make managing driver packs easier and create an easier mechanism for reporting to management that driver packs are up to date easily

- Add fields to track last date verified to facilitate weather there is a new replacement
- Supported OS releases as defined by vendor release docs, to assist in troubleshooting in the rare instance a driver does not work with a future release
- Add Life cycle field for ie New/Testing/in use/soon to be replaced and retired

With all of the new USB type NIC dongles needed to image devices, I've run into issues with some devices not joining the domain because the internal NIC didn't initialized in time. I know there's a "Join Domain or Workgroup" step you could add but it would be easier if the retry/delay could be included in the "Apply Network Settings" step versus having to create another group/step as a backup. Or even creating a TS variable that could be adjusted in the TS similar to SMSTSDownloadRetryCount & Delay.