Allow to download windows wim file from SCCM console. Windows 10 is available from online publicly using media creator tool. So adding this option will make it easier to download in one place

When you choose Restart Computer in a Task Sequence you can only choose the assigned boot image or the installed OS. This requires we have duplicate Task Sequences for 32-bit vs 64-bit for UEFI, or we have to create child-Task Sequence relationships when really we should just be able to pick a boot image like any other package!

Options should be:
- Installed OS
- Assigned Boot Image
- Select a Boot Image

It would be great to have the ability to customize the USMT without being burdened with XML configuration. Although this could remain as an option being able to restrict themes from migrated and restrict pulling over the registry would be great. Sometimes with the registry you can often pull problems over with the migration.

Presently nested task sequences only run under a single context. There are some workloads that it would be helpful if a child task sequence could run under a different context. For example, the system account of the computer may not have sufficient rights to add an object to an AD group, but capturing administrative credentials and passing to a child task sequence would facilitate this function.

I would like to se some telemetry / insights where client is going to push its USMT data before deployment starts. Need to know if disk space is sufficient on USMT stores.

As clients roam the network, I cannot predict where yesterday's clients are going to push their USMT data today when deployment starts.

Software updates for workgroup machines doesn't work during build and capture. Panu says it works if you domain join; and then patch; and then leave the domain... but doesn't work if you are workgroup machine one.

to have an easy to use registry key / value application script builder that could be used to deploy to a collection group or be used in operating system deployment

A button where is possible export MDT Task Sequence Configurations for be used as a template.

add additional statuses to Task Sequence Deployment, so we can see if content was already downloaded when this feature is selected. Similar experience to Application Required deployment. Right now it requires lot of administrative work to check if WS is ready to start TS.

Add the Option to rerun the deployed Task Sequence of a Device-Collection. Also it would be good to have the Option to rerun a deployed Task at the Monitoring-Tab in the failed-Tab.

When importing a TS, and you have multiple dependencies to import with it, would be nice to have a check box to overwrite all, instead of clicking on each one to overwrite, or ignore.

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

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.

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.

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.

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.

Existing task sequence which was previously used to deploy Windows 10 version 1809,1803 & 1709, is not failing with version 1903.

Task Sequence fails while trying to install applications, none of the application gets installed. We are getting error "NotifyProgress received: 16 (Application failed to evaluate )".

If I change the install.wim from 1903 to 1809 or any previous version, it works absolutely fine.

Seems like bug with version 1903 only.