Ideas
What features would you like to see?
All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Microsoft Endpoint Configuration Manager, though we can’t promise to reply to all posts.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
Make ConfigMgr work with Autopilot and Enrollment Status Page (ESP)
When deploying a device using Autopilot, the Enrollment Status Page (ESP) is used to prevent access to the desktop until the device provisioning tasks are complete. But ConfigMgr doesn't integrate with the ESP, so there's no way to wait for packages, apps, or task sequences - the user doesn't know when the process is done. Add that integration.
867 votes -
Allow custom icons in software center for Task Sequences
Split this item from a bigger umbrella item.
This is to specify an icon per App Task Sequence in the Software Center.1,746 votesstarted ·AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.See https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1905#bkmk_tsdt
& https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Group-applications-into-a-single-deployment-in-ConfigMgr/ba-p/624318 -
Apply Configuration Baseline/item during OSD
When trying to move away from Group Policies to Configuration times/baselines and in every other scenario as well, add a step in Task Sequence to evaluate and remediate select Configuration items/baselines. Then we can select which one of the Configuration Items/baselines should be applied during OSD so the settings are present when the user logs on for the first time
79 votes -
Add keyboard layout settings in the Apply Windows Settings step
I would like you to add the keyboard layout setting in the Apply Windows Settings step.
Please add it as shown in the screenshot below.
Currently, keyboard layout settings are manually added to the registry within the Task Sequence.Command line:
cmd.exe /c reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "LayerDriver JPN" /t REGSZ /d kbd106.dll & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardIdentifier" /t REGSZ /d PCAT106KEY & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardSubtype" /t REGDWORD /d 2 & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardType" /t REG_DWORD /d 736 votesstarted ·AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started – this item was implemented in our 1908.2 Technical preview release – https://docs.microsoft.com/en-us/configmgr/core/get-started/2019/technical-preview-1908-2
We’ve also reiterated on the additions based on your feedback. Check out any of the recent Tech previews.
-
GitHub integration for Task Sequence Changes
Having version control for Task Sequences would be invaluable.
If we could link a GitHub account we could easily monitor Task Sequence changes either in Github or SCCM. The ability to roll versions with Administrator approval (similar to publishing scripts) would be ideal.
Expanding on this idea more, highlighting additions/edits/deletes within the Task Sequence dialog would be the icing on the cake.
28 votes -
Import Task Sequence - Add Option to Create Duplicate with New Name / ID
When Importing a Task Sequence, I'd like the ability added to Import a Duplicate, but it would NOT overwrite the original, it would create a duplicate with modified name and new package ID.
Situation, I've created v1 of the TS and exported for sharing. Others have taken v1 and modified and started to use.
I then export v2 of same TS and made available, others want to import but it will overwrite. Would like the ability to allow others to import v2 without impacting v1.7 votes -
Add application group in task sequense
It would be great if the created application groups can be added in a task sequence.
Instead of having long lists in a task sequense you could manage default apps in the application groups
14 votes -
allow export all task sequences or folder of task sequences
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.
45 votesThanks for your feedback, updating status to noted.
Just in case it’s not well known, we support multi-select for Task Sequence export.
Any packages or applications that are referenced across multiple task sequences are only exported once.
Does this help address the ask?
-
Variable with Full OU path
Take the OU path from 'Network Settings" and turn it into a variable e.g. _SMSMachineOUpath
I use dynamic variables to determine the OU based on location and device so my Domain OU path has OU=%devicetype%,OU=Location,OU=workstations,DC=Contoso,DC.com
so it would be nice to have the actual value in a variable that I can reference later say in a script to move existing object to the above created OU. I can see the full path in the SMSTS.log, but not in a variable. Also removing the LDAP:\ from the start could be handy in some situations I guess.1 voteHi Marty,
Vlad ask to pass this on:
He can try at the beginning of TS to add steps to set variables that I listed in my reply to the same strings that he entered in the UI of Network Settings step? Which will result in Network Settings step take the values from these global variables (not from UI, even though they may be the same). But it will also have a side effect that these variables will be available during task sequence for whatever he wants to user them for.
I’ll have a bit of time at the weekend. I’ve a couple of ideas about removing the LDPA:\\ you mentioned. Can you describe the scenario you want to address, please?
Thanks
-
OSUninstall - Make ConfigMgr Aware of going back to previous builds
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…
61 votesplanned ·AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to planned.
Thanks for the feedback, I filed the exact same issue in our database a while back. We’ve addressed recovery from being stuck in ProvisioningMode in our 1902 release. See https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902#bkmk_client
Next step is to clean up the task sequence.
-
Ignore DHCPINFORM messages in SMSPXE.log for sccmpxe service.
Team,
Currently when the non-WDS PXE responder is enabled, all DHCPINFORM messages are logged in the SMSPXE.log. This floods the log with unnecessary information and makes the troubleshoting more difficult as the log gets overwritten very often.
Please perform the change to at least not log these DHCPINFORM messages.
8 votesThanks for your feedback. Updating status to noted.
May I ask which version you are seeing this occur on. We addressed this in our 1906 release so upgrading to latest will solve this – our 1910 release is in opt-in phase now (fast ring)
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Update-1910-for-Microsoft-Endpoint-Configuration-Manager-current/ba-p/1032459
Docs: https://docs.microsoft.com/configmgr/core/plan-design/changes/whats-new-in-version-1910Thanks
-
Administration service URL Task Sequence variable
With the new great possibilites using the Administration Service it would be great to have a Built In task sequence variable with the URL to the SMS Provider(s) so we can easily call that in our OSD Powershell scripts during OSD
8 votes -
Show Ethernet connection speed before start OSD task sequence
Sometimes the users just don't know their computer is actually connected LAN at 100 Mbps instead of 1Gbps due to network port issue or network cable issue. It will take almost 5 times longer time to complete the OSD task sequence. It just messes up the things. I hope the network connection speed info is visible in WinPE or give user a warning before kicking off the OSD task sequence.
1 vote -
pre-cache content and packages
Pre-caching content for a task sequence is great, but we do not use driver packages for installing drivers in a task sequence. We use normal packages and the download package content step. This is true for in-place upgrades as well. As it works right now, when running an upgrade task sequence, the client downloads all of the packages for drivers, regardless of whether they are needed for that particular model. It would be nice to have a way to specify which package containing drivers gets cached for a particular model.
4 votes -
Install Third Party Software Updates during TS Install Software Updates step
Currently (v1806 or later) Third Party Software Updates are not being installed during the Install Software Updates step in a Task Sequence.
Ideally third party software updates should be installed just like regular updates during the Task Sequence. A machine should be fully patched (secure and end-user ready) when it leaves the deployment bench.
44 votes -
Conditions Library for Task Sequence Editor
We often find ourselves duplicating conditions in Task Sequences. The ability to copy/paste/move conditions in TP 1908 is excellent but I would suggest we could go one step further.
To have a conditions library where we could select custom - predefined conditions would be excellent. We should be able to add/edit/delete our own predefined conditions.
6 votes -
monitor the ConfigMgr PXE Responder Service
I would like a way to monitor the ConfigMgr PXE Responder Service when an error occurs. For instance, when starting an osdeploy and the bootimage fail to load with error 0xC0000001, the smspxe.log simply stops its output, not generating any error. With the WDS-service, this error was easily detected in the eventlog.
5 votes -
Have the console alert when the task sequence size is reached
The task sequence has a 32MB size limit for all policy. But for some reason they are actually limited to 16MB. But the Product Group is aware of the problem. I know they are working on fixing the 16MB limit.
This will help us troubleshoot and determine when the task sequence has reached this size.
5 votes -
Bitlocker Network Unlock with WDS-less PXE
With Bitlocker Network Unlock, a WDS server can automatically unlock your bitlockered device without requiring the user typing the PIN at boot. (https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock).
As we all go forward using the SCCM WDS-less PXE-provider instead of WDS, it would be a good idea, if it supported Bitlocker Network Unlock, too.9 votesThanks for the feedback.
Updating status to Noted – for an explanation of status values see here:
https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion -
Store output of run command line to TSEnv with "RunAsUser".
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…
11 votesUpdating status to noted. See https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.
- Don't see your idea?