Currently you can only remove and remove all from a task sequence option condition. I think it would be very helpful and time saving if you could copy/cut/paste conditionals from a right click menu.

Sometimes it might be handy to remove a computer from the OSD collection as a final step during the task sequence. Or additionally add the computer to additional collection(s) for for example extra software deployment or another task sequence.
Now scripts need to be created therefore and in my experience this doesn't always work well.
A predefined step where the collectionname or collectionID needs to be added to add (or remove) the computer to (or from) would be much appreciated.

In order to avoid using distributed PXE Servers a support of the Option on PXE DHCP Handshake would make proper inter tenant forwarding possible.

Application A and Application B. Application B supersedes Application A. The content is removed off the DPs for Application A.. A task sequence (non-OSD TS) deployment of Application B fails with "The software could not be found on any servers at this time." After reading the logs, it is looking for Application A. BUT a regular application deployment Application B, it works fine, so this issue is ONLY occurring in TS.

We have the possibility to select to "Access content directly from the DP" when deploying a operating System image in a Task Sequence. It would be great to be able to do this for "Run Command Lines" as well.
Example scenario, you want to run a Powershell script from a package before the disk is formatted in a scenario where we use Bitlocker for instance.

Please add to the Restart Computer OSD task sequence step an option that will check if the system requires a reboot and then only restart the computer if it needs to. Right now to work around this need, we have to execute a PowerShell script and write the results to a custom task sequence variable and then use that variable as a condition on the Restart Computer step. Adding this option natively would be much more elegant. Attached is the script we're using.

Provide Mac Provisioning with CM12.

Other vendors provide the ability to image and fully manage the Mac device, when will Configuration Manager provide this feature? Imaging Windows platforms is only part of a corporation desktop landscape, we also support Mac, having a single solution would make logical sense.

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.

With more and more devices being connected to azure AD, SCCM should have an option to perform a zti deployment and join the newly deployed Windows 10 to azure AD only. not hybrid where GPO needs to exist, but a native support where the connection to SCCM already exist but the computer will not be connected to the onprem domain.

It would be convenient to have a method to enter/save your volume licensing credentials to have it directly download an iso from the volume licensing site, extract the wim into a designated storage location, and then import it directly into the console. This would especially be nice considering the more frequent release of new Windows 10 builds. I like running my B&C from the newest image available.

Give us the option to restrict a required Task Sequence to "When no user is logged on" This would be particularly helpful when using Task Sequences to push out Application updates. That way if the TS tries to run while a user is logged on it won't fail as soon as it hits the applications which are set to "When no user is logged on"

Use the value from the built-in variable SMSTSRebootDelay for reboots that occur during the 'Install Application - Install applications according to dynamic variable list' step. This would reduce the time for OS deployments.

It would be useful to integrate AD authentication in the WinPE boot image for PXE boot OSD.

When deploying operating systems with MDT and WDS, users are prompted to authenticate against AD when PXE booting. However, in SCCM the only supported way to secure the PXE point is with a DP password that all users share.

There are third party "hacks" which can integrate AD authentication in the WinPE boot image (Johan Arwidmark's ADSI drivers) but it seems like this would be simple to implement within the product itself since it is already done in MDT/WDS.

While a Step for Run Command line can be used for most Windows Installer, if an application uses a EXE it would be nice for the application to be downloaded and the exe used.

at the moment we need to use scripts with passwords in it against a CES/CEP because SMS Agent is in provisioning mode. It would be great to do certificate enrollments during deployment with the certificate enrollment point as the proxy. we use tpm attested certificates to check if the machine is known to increase security