PowerShell cmdlets for editing task sequences
Being able to edit task sequences with PowerShell would make managing task sequences much easier. Some possible new cmdlets could include:
Add-CMTaskSequenceStep
Get-CMTaskSequenceStep
Remove-CMTaskSequenceStep
Set-CMTaskSequenceStep
Add-CMTaskSequenceGroup
Get-CMTaskSequenceGroup
Remove-CMTaskSequenceGroup
Set-CMTaskSequenceGroup
Matthew
shared this idea
AdminAdam Meltzer (ConfigMgr Product Team)
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
This work should be completed in 1802.
If there’s any specific Task Sequence scenarios that you feel are missing post-1802, please open a new feedback in UserVoice so we can track these items individually.
Thanks!
11 comments
-
Adding a nested task sequence to a task sequence in PowerShell is already possible in 1906 release or later: New-CMTSStepRunTaskSequence
-
dan felman
commented
i am very interested in adding a nested task sequence to a task sequence in powershell... will that be possible?
-
Noé
commented
Hello,
Do we need to update SCCM server to 1706 (already update my windows to 1706 if we need access to the command "Add-CMTaskSequenceStepRunCommandLine" ?
-
Anonymous
commented
Please add a "Apply driver package" step. Also will we be able to set what's available under the Option tab? Specially add WMI queries.
-
Release notes: https://docs.microsoft.com/en-us/powershell/sccm/configurationmanager/1706_release_notes.
Please keep the feedback coming!
-
@oyvsi thank you for the feedback. Needless to say we're working on adding additional TS types. We are targeting the most common step types for 1706 and our current plan is for full UI parity in 1710. I will pass the TSStep/TaskSequenceStep feedback to our developer.
We're not planning on having a single Set- cmdlet to cover all TS operations. We've been moving away from this design over the past couple of years for numerous reasons (hard to use, hard to document, hard to maintain). We will maintain generic Get and Remove cmdlets, though.
Thank you again for trying this out!
-
oyvsi commented
I just got 1705 installed and this was the first thing I checked for. Great work. Some feedback: the naming seems a bit inconsistent; both *CMTSStep* and *CMTaskSequenceStep*. It appears that there are only a few types of steps which is currently possible to edit. The most valueable to me would be where one would expect differences between environments. e.g. network settings (domain name, OU and account) and Apply operating system (different sysprep file). Would it not be possible to have a generic Set-CMTaskSequenceStep instead of having to break all the different kind of steps into cmdlets?
-
I see this has been updated to started, but I don't see any of this in 1704. Which part has been implemented?
-
Really missing this feature. Hope it gets included soon
-
Anonymous
commented
It would be nice to see the ability to also modify/add conditions for each of the objects as well.
-
Matthew
commented
Glad this is planned now! Another task sequence cmdlet that would be really useful is one that lets you copy a task sequence. It could be named Copy-CMTaskSequence.