Split this item from a bigger umbrella item.
This is to specify an icon per App Task Sequence in the Software Center.1,946 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We’ve released our 2001.2 Technical Preview.
For more info:
This release has some update to the task sequence as a deployment type. See
Many organizations create their own front-ends for ConfigMgr Task Sequences (or leverage popular third-party ones like OSD++, Pretty Good Front End, etc.). However, these only are able to be used when the task sequence is in WinPE.
Please add the serviceui.exe functionality into the default task sequence environment so it is possible to display Light Touch prompts when starting the task sequence from an existing operating system. Including serviceui.exe would be enough, or the functionality to launch interactive UI could be added to the environment natively.148 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started. See https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Configmgr 2003 Technical Preview released today and has a new SDK method for task sequence progress.
For more info:
This should address some of the asks here, please try it out and let us know your feedback.
I would like more space in the OSD Task Sequence description field (and possibly even include a link) so that we can adequately tell people what's required before and after running the Task Sequence and to tell them where to find help.
At the moment, we only have 2-3 lines of text available.
Perhaps replicate what's currently available in the application model with the Localised description on the Application catalog tab.15 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started. see https://docs.microsoft.com/en-us/mem/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Our 2010 Technical Preview is released today.
This release includes changes to the task sequence properties – the limit is now increased to 512 characters.
(I neglected to make the same change to the wizard, I’ll get to that in the future)
Please give us task sequence variables for the following because WMI can be unreliable or sometimes can't be used. These would be nice to have in order to create conditions for performing actions such as enabling/disabling TPM and SecureBoot.
TPM owned/not owned
SecureBoot enabled/disabled4 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started – see
Our 2002 release added _TSSecureBoot
Use this variable to determine the state of secure boot on a UEFI-enabled device. The variable can have one of the following values:
NA: The associated registry value doesn’t exist, which means the device doesn’t support secure boot.
Enabled: The device has secure boot enabled.
Disabled: The device has secure boot disabled.
For TPM that’s achievable with task sequence conditions – I’ll look to add something to the Community Hub to demonstrate.
It would've been nice to have the ability to resize the new "Enter a PowerShell script" window to chech that everything looks good. The default windows is quite narrow. Maybe add som nice colour formatting to get a better overview.3 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We are working on improvements around the console for this scenario. You should see some of these in recent technical previews. We have also further improvements for improving the scripting experience planned for future releases.
- Don't see your idea?