Please Make CM aware if an OSUninstall (Reverting to previous Build) has happened, so it can heal itself into a functional state. Currently if you perform an OSUninstall from say 1809 to 1709, after you've upgraded originally to 1809 using a CM Task Sequence, the CM Client is non-functional.
Client is in Provisioning Mode, Services are disabled, and once you fix that, it thinks it's int he middle of the Task Sequence and shows the Upgrade TS "Installing", so then you need to clear that out.

Please make OSUninstall & CM Play Nice together, so we can offer users the ability to revert to previous build if they find an application problem or other issues after upgraded.

Running a step as a user prevents you from using the TSEnvironment in order to store any data returned.

The step could be anything, like getting a byte array of a certificate, ad-groups of the computer or primary user or as in this example, getting the TPM OwnerAuth from MBAM.

I would rather store it directly in the TSEnv instead of in a temporary file and run another script to read the file just to be able to use the password, as a variable, from a “Run commandline”-step.

The only other workaround I’ve found this far is running the step the normal way and supply the credentials in the command line or within the script it executes.
Storing a pw, even if encrypted, in a package which every user has default access to isn’t optimal and using a password, in clear text, in a run command line step has security impacts as well.

Suggestion: Add the possibility to store the output/data returned from a "run command line"-step as a task sequence variable, even if runasuser is chosen. (see pic)

Can you add Output to the ShowMessage Method Please.
https://docs.microsoft.com/en-us/sccm/develop/reference/core/clients/client-classes/iprogressui--showmessage-method

You currently have the ability to create a Message Box with several Options for the Buttons, but no matter what you pick, or options you choose, you never get anything actionable.

Current Actions:

0 - Ok
1 - Ok/Cancel
2 - Abort/Retry/Ignore
3 - Yes/No/Cancel
4 - Yes/No
5 - Retry/Cancel
6 - Cancel/Try Again/Continue

If you could have it Create a Variable upon the end of the step
SMSTSShowMessageOutput = "ButtonName"

Which then would supply one of the following Values:

Ok, Cancel, Abort, Retry, Ignore, Yes, No, Retry, Try Again, Continue

I'd like in the Right Click Menu on a TS to have a "View" option that includes all of the Referenced Task Sequences populated into the TS as a Group.

We have so many sub task sequences in our main task sequence that sometimes it is easy to get confused where exactly a step is going to be run in the process. Providing a view that enumerates all of the steps from the sub task sequences and places them into the parent would be helpful. (just view, not edit) Similar to how the client merges all of the policies into one large policy, do the same in the console to create a view option.

This would also allow the UV for a search TS Feature to work better, as you'd be able to search the "Full" TS, not just a parent or child.

https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/10015995-task-sequence-editor-search

We maintain 2 copies of our task sequence. We make changes to the DEV TS then copy the entire TS contents into the Prod TS when we have completed testing. The issue we generally have is that we also have Dev/Test versions of our apps/packages/etc. If our DEV TS is referencing the DEV items, we then have to go through the Prod TS after we paste and update them back to the prod versions. In some cases, we've just added logic to test if we are in DEV and always use the DEV packages, but that adds extra processing steps to the TS (we generally delete the added steps from the PROD TS).

Can we have a feature that allows us to relate apps/packages to each other to specify that one is DEV and one is PROD. Then in the TS, we could specify that we are using DEV or PROD and they would automatically choose the correct version?

If not that complex, at least adding the ability to right click in the references tab and swap out a reference and have it auto update ALL references for that item in the TS.

Essentially, add a way to easliy manage all references within a TS to make it easier to migrate changes between DEV and PROD.

This a two part request actually
1. The ability to use the content already downloaded into the ccmache folder, rather than duplicating the required disk space by copying the content from ccmcache to _SMSTaskSequence\Packages during the TS execution.

2. The ability for an in place upgrade Task Sequence with Pre-caching enabled to run the option checks on the TS steps (like WMI queries for driver packages) so that the device only downloads what is needed to run the upgrade on that device

The amount of additional disk space/network bandwidth required for both of these scenarios is magnitudes larger than it needs to be to complete the upgrade.

I think it is about time that we had the ability to use Powershell to query and set conditions within the task sequence. I.E. we currently use WMI queries to check bios versions to decide whether or not to upgrade the bios version similar to this …
"SELECT * FROM Win32_BIOS WHERE SMBIOSBIOSVersion < "1.9.3""
the problem with this is this is a string value so with POSh you could easily convert that to an integer and then use that as your condition.
What I would like to see is something similar to the new edit script interface in 1902 but for conditions as well.