System Center Configuration Manager Feedback

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 System Center Configuration Manager, though we can’t promise to reply to all posts.

Standard Disclaimer – our lawyers made us put this here ;-) Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos which you do not want to grant a license to Microsoft. See the “User Voice Terms of Service” link below for more information.

How can we improve Configuration Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.

You can remove your votes from an open idea you support.

To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Tell us your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

It would be great if we had the option to set a required Windows 10 in place upgrade Task Sequence with scheduled notifications for users with an installation deadline. This would allow In-Place upgrade deployments to be enforced ensuring timely Windows 10 version updates whilst allowing the end user enough time to schedule the upgrade.

I work in an environment that does not allow me to enable the command prompt in a boot image. This makes it difficult to check what went wrong. During the dependency check in a PXE advise which dependencies failed on the screen as well as the log. It would be good to state if the NIC and storage drivers are working ok.

In TP1802, new feature allow Windows 10 in-place upgrade task sequence via cloud management gateway, which is very good feature, so please allow distribute Task Sequence content to cloud distribution point. In this moment, clould distribution point is not in the list when try to distribute Task sequence contents.

Currently Task Sequences can be backed up and restore via the ConfigMgr PowerShell module. When it is time for Dev TS's to become production, it would be nice to be able to import the settings from the Dev TS directly into the production one. This way deployments don't need to be recreated and changes don't need to be meticulously documented and recreated in the production TS.
Simply replacing the prod TS with the Dev one isn't as clean as new TS's take much, much longer to show up in the Software Center.

When a package is missing on a distribution point for a task sequence, the error message used to include the package ID, so we knew which package to deploy. That is now missing in the latest build. Now it's a guessing game on what's missing. Return the Package ID so that troubleshooting gets easier, not prettier.

A nice feature would be an integrated solution to allow a computer to remain awake during large content download. We currently have the ability to WOL for deployments, but in a some situations where content is not pre-staged/downloaded or if you use the option to download all content locally before running a task sequence the computer can sleep during content download. A use case is for this example is Windows 10 in-place upgrade TskSeq. Please implement a Power Availability Request based on process or thread to resolve this issue. The alternative of managing custom power plans or hacking a toggle for active power plan isn't pretty. Thanks.

A nice feature would be an integrated solution to allow a computer to remain awake during large content download. We currently have the ability to WOL for deployments, but in a some situations where content is not pre-staged/downloaded or if you use the option to download all content locally before running a task sequence the computer can sleep during content download. A use case is for this example is Windows 10 in-place upgrade TskSeq. Please implement a Power Availability Request based on process or thread to resolve this issue. The alternative of managing custom power plans or hacking a toggle…

If a boot image fails to update on distribution points, then the process continues to execute and the errors and indication of an unsuccessful update are only shown after the process completes. It would be nice if the process would stop when a failure occurs so the admin can troubleshoot and fix the issue. Otherwise, I'm just twiddling my thumbs with the console open while the process takes forever to complete.

When we are deploying a OS over a SCCM Boot Media Iso there is a possibility to define a IP, Gateway, Subnet ... If there is a tipping error the TS will fail and we have the possibility to push the previous button. In this Case the "Configure network settings" button is greyed out. Would be great if we could modify this settings

The 'Check Readiness' TS Step will fail if it cannot find a fixed disk with a partition that meets the requirements defined in the step.

Because it is looking for a partition, if there is a new disk or a disk which has been cleaned, but no partitions created, it will fail even if that disk has the required space available and would be successfully partitioned/formatted by the TS.

Maybe the step should consider fixed disks with no partitions when evaluating space required.

I do some customisations (remote control, scripts for support, bginfo) to our boot.wim files by copying files while it's mounted and doing an Update distribution points. It would be nice to be able to inject files to certain folders (like Windows\system32) in the property page of the boot image in a separate tab. Also include command to execute these custom scripts in winpeshl.ini just before TsBootShell.exe

X:\sms\pkg\sms00001 is the path the files/content from the ‘Prestart source directory’ is added too.

The doc link – https://docs.microsoft.com/en-us/sccm/osd/get-started/customize-boot-images
has this entry
When you boot to WinPE from a customized boot image that includes tools that you added, you can open a command prompt from WinPE and type the file name of the tool to run it. The location of these tools are automatically added to the path variable. The command prompt can only be added if the Enable command support (testing only) setting is selected on the Customization tab in the boot image properties.

Notebooks move around, users with pc's also moves around between site codes. It would be great to be able to F12 build a machine from a different site code with it's assigned Task Sequences without having to delete and recreate it in the correct site code.
I know it can be moved in the console but what if the machine's current windows installation is corrupt and cant be moved to a different site code to F12 build it with it's assigned Task Sequences.

Custom Task Sequences allow for simple WMI queries for BIOS version detection. This is a nightmare when attempting to do in an Application. I am unable to deploy this task sequence to just my IT teams, and keep it hidden from regular users.

Currently, anytime you run the upgrade OS step, it set the client into provisioning mode, despite the options you're choosing. Could this be changed, that if you pick "Compatibility scan without upgrade" it would NOT put the client into provisioning mode.

I've had users reboot the computer when the scan was running (silently in the background), and then the client was in provisioning mode.

Would be great when during the Import of Computer Information we would get a hint that the MAC, GUID or Name already in SCCM exist and we get a message box with the question if we like to overwrite it. At the Moment we have the situation, when for example a MAC already exist, the Computer Object name will be overwrite but the information like SiteCode or Inventory and Collection membership are still there.

The addition of run task sequence step is great. I see many useful ways of using this feature. However i would like to have the possibility to control if the parent task sequence checks the referenced packages in the child task sequence.

I would like to see a tick box on the Run Task Sequence step called something similar:
Check refences packages in child task sequnce.

It could be ticked as default.

Here is an example how this could be used:
My idea is to have country specific applications and roles that currently exist in MDT in separate task sequences instead. The problem with using this is how the current "Run task sequence step" works is that i would need to have all packages referenced by all child task sequences on all DPs.

Since i would have some kind of option on the Run Task sequence step it would only run when a role or language is selected in for examle UDI wizard. The content would only be needed in corresponding country DP and not on all DPs. This would help me replace MDT with something easier to maintain.

Also bonus features if you choose to use TS as roles to replace MDT:
- You could run steps before and after applications install in a role
- You can run the roles after a machine is deployed

The addition of run task sequence step is great. I see many useful ways of using this feature. However i would like to have the possibility to control if the parent task sequence checks the referenced packages in the child task sequence.

I would like to see a tick box on the Run Task Sequence step called something similar:
Check refences packages in child task sequnce.

It could be ticked as default.

Here is an example how this could be used:
My idea is to have country specific applications and roles that currently exist in MDT in separate task sequences…

SCCM needs to have the ability to use a Pre-Installed OS (OEM, Manually Installed, Push Button Reset) as an alternative to a wipe and load. Combined with AutoPilot and/or provisioning packages, this would decrease the time required to deploy devices.

Currently, there’s no way to install the SCCM client into the installed OS from WinPE nor a way to deploy a task sequence to an unmanaged (no SCCM client) device that has been Provisioned (domain joined) and is booted into Windows. Additionally, the SCCM client installer launches sub processes then exits, which makes monitoring for successful installation difficult.

Our current process includes applying a Provisioning Package to domain join, use Import-CMComputerInformation to pre-add the device to the TS collection, then install the SCCM client. Collection membership processing combined with client policy retrieval (without manual intervention) is slow and essentially cancels any time gained by using the pre-installed OS.

SCCM needs to have the ability to use a Pre-Installed OS (OEM, Manually Installed, Push Button Reset) as an alternative to a wipe and load. Combined with AutoPilot and/or provisioning packages, this would decrease the time required to deploy devices.

Currently, there’s no way to install the SCCM client into the installed OS from WinPE nor a way to deploy a task sequence to an unmanaged (no SCCM client) device that has been Provisioned (domain joined) and is booted into Windows. Additionally, the SCCM client installer launches sub processes then exits, which makes monitoring for successful installation difficult.

Modify the Download Package Content step to include a dynamic option similar to the Install Package step (see attached mock up). This will allow the ability to selectively download content that is not a direct task sequence reference. When deploying the task sequence, the direct references (common to every system) can be downloaded ahead of time and then the system specific items can be downloaded selectively at TS run time. OSDDownloadContent.exe already performs a dynamic content location request, which is super useful when needing to pre-cache or download driver packages, BIOS packages and other items that are machine specific.