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

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.

After an operating system upgrade, it would be nice to be able to delete the files of the previous installation in order to free up disk space. Cleanmgr.exe doesn't work under SYSTEM context.

Often times, when WinPE boots and there is an error before OSD completely loads, WinPE simply reboots without showing any errors and does not give you the opportunity to gather log files via console. While this issue is typically a driver or time issue, it's impossible to know for sure without looking at the logs. This forces the techs to submit tickets and for the SysAdmins to guess as to the cause of the issue.

Following on from the excellent view only option added to task sequences - https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/20361052-task-sequence-view-only-option - can we have the ability to copy a task sequence step from this view? We can already copy text from e.g. Run Command Line but we can't copy task sequence steps themselves or view conditions on steps in a way that allows copying text from them so we still need to open the task sequence in Edit mode to do this.

Add the option in Apply Operating System to add a script that can modify the WIM file once it is downloaded (i.e. changes would be local only to the current OS installation).

This would allow you to keep the WIM file as generic as possible while still allowing it to be modified, reducing the number of WIM files required in an environment that may require multiple WIMs per OS.

Allow the ability to override maintenance windows and client settings during an initial OSD task sequence setup of a client device. This would allow the initial OSD, Drivers, applications and software updates to complete in an expected timeframe. Currently additional scripting and checks are required to accomplish "a ready to deliver device" to a client, and in most cases, additional updates are still pending after a device is delivered.

Hello

I'm trying to create a 'big' stand alone media..and timeout is not enough.. actually, if i select everything, timeout generate an error ..

could you think a possibilities to extend the timeout for big infrastructure and task like me ?

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.

I'd like to be able to put in the name of the copy as I make it and not have to go into properties and then rename it. This takes forever considering how slow SCCM often goes. So to save time being able to rename it when I right click and hit Copy would be ideal. Plus having the copy cut off half of my task sequence name with Hex nonesense is annoying.

Add
MDT Define Microsoft Deployment Toolkit Package
Use Defined Microsoft Deployment Toolkit

So you can define then just use the defined MDT Toolkit. This would make it easier when you have multiple Use Microsoft Deployment Toolkit Package, in the TS. This way they wouldn't all have to be edited. So after you make a change/update your UDI for whatever reason usually applications upgrades.

This would same a major amount of time also ensure you don't miss one, and less time editing and testing.

The ability to identify which components have Multicast enabled or disabled when deploying a task sequence to help id multicast issues.

Ability to browse registry when adding Registry Conditions in Task Sequence.

I don't know if this is possible, but it would be very useful to be able to customize the OOBE option in the TS through the GUI. Currently you need to create an xml file for customization with WSIM, which works, and provides a ton of options, but it would be nice to have a generic set of the most common options as checkboxes or something. If someone needs further customization they could use an XML file instead. Part of the problem is that many options are "deprecated" yet they still seem to work?

Add an option to the "Restart Computer" Step to have it shutdown instead of restart.

Use Case: We are using ConfigMgr OSD to build reference images in VMWare for VDI. We need the ability to take clean snapshots along the way for auditing and spinning off variations.

In the TS, we'll trigger a micro service on an automation server to control the VMWare vCenter and take a snapshot once the VM is shutdown, then turn it back on.

Customer does not have the store installed and using the built-in TS step keeps files and apps. I know that the "OSDSetupAdditionalUpgradeOptions" variable can be used, but it would be nice to have the option on the built-in TS step.

Can we have a where used tab in Operating System images and upgrades?

Hierarchy settings does not seem to be the most appropriate location for this, engineers in the field would be adding dongle MAC addresses quite often.