Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

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.

Please do not use UserVoice to report product bugs or for assisted support.
If you believe you have found a product bug, please send us a bug report through the Configuration Manager Console (1806 and newer). To do this, press the 🙂 button in the top right corner and choose “Send a Frown”. For more details, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help.

If you require assisted support, please see https://aka.ms/cmcbsupport for more details.

Standard Disclaimer – our lawyers made us put this here ;-)
We have partnered with UserVoice, a third-party service, so you can give us feedback. Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft Configuration Manager. Do not send any novel or patentable ideas, copyrighted materials, samples or demos. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Install Software updates TS step improvements

    The "Install Software Updates" TS step could use some improvements, including adding an option to run a package after the reboots (before update step continue), and customizing the restart time-out and messages. The status messages are also pretty vague. For example, we know that after it installs the updates it can check for updates again, but it doesn't actually say when it's doing that. I've also noticed some blank black screens showing up for at least a minute as it is about to reboot.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Re-think task sequence policy download in OS

    Currently deployed task sequences create a lot of policy download and slow down the initialisation of a workstation. If they worked like in bootable media, or another way - I don't know if say downloading the TS policies as a zip would help?

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Ability to see/change available task sequences list order

    A computer may be member of several collections. When we deploy multiple task sequences to different collections, available task sequences list changes when computer is booting from PXE. So, we need to check the list order, after deploying new task sequence. Also, first task sequence is selected automatically and users are inclined to select the first one.
    It is now alphabetic order, but we should see the list order without booting PXE and maybe we can change the order or set a task sequence to the top.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add subfolder search to Task Sequence Install Package

    When you use the action "Install Package" you can search for the package but it only searches the selected folder and not the structure. Could a switch be added to search subfolders?

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

  5. A task sequence step that dumps SMS logs to a network share on TS failure

    Add a step or option to a task sequence that will dump any SMS logs to a predefined location, either a network share or USB drive.

    It is a total PITA to watch every machine as a TS runs so we cant always copy the logs off before the machine automatically reboots.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  6. driver import bug

    When importing
    \\dfs\shared\SCCM\Packages\OSD Drivers\Sources\Windows 10\x64\Surface Pro 3 v2

    without a slash at the end

    It imports
    \\dfs\shared\SCCM\Packages\OSD Drivers\Sources\Windows 10\x64\Surface Pro 3\

    as well..

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Bypass "Press Enter" Prompt on Available TS Deployments with CM WDS UEFI PXE Boot

    When you deploy an OSD TS as Available, you are prompted to "Press ENTER for network boot service." If you do not press enter it instead boots to the OS (if any). This does not occur when using a required deployment. It would be useful to bypass this for available deployments.

    This behavior is documented by Microsoft.

    https://docs.microsoft.com/en-us/sccm/osd/deploy-use/use-pxe-to-deploy-windows-over-the-network#BKMK_Deploy

    There is a previous UV that mentions this from 2017, but it was declined. The reasoning does not pan out for me, though. It does not appear to be a hardware issue as it occurs on both physical and virtual workstations. It…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Run Powershell Script (Task Sequence Step) passed parameters not visible in logging

    When parameters are provided on a 'Run Powershell Script' in a task sequence, the SMSTS.log only logs the name of the script. It does not log the full command (including parameters) that are invoked.

    For example: if I call Java.ps1 with parameters -level 1 -language eng the SMSTS.log only shows...

    Running powershell script: 'Java.ps1'(PkgID: SCM00000) with execution policy 'Bypass'

    This would be helpful in troubleshooting what parameters were actually passed to the script that is executing. Otherwise you have to track down the task sequence and assume everything entered is passed and run. Or you have to build your PS1…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Let the TSAgent consume enough RAM in VMs configured with Dynamic Memory for OSD compatibility checks to succeed

    Setup: Hyper-V Gen2 VM configured with 1GB startup RAM, Min 512MB, Max 4GB.

    I was testing servicing Windows 10 1511 to Windows 10 1607 on my VM and the compatibility check failed because the VM was only consuming 1560MB at the time of the compatibility check. I'd think that it would be able to tell if the VM's maximum RAM value was higher than the minimum RAM requirement for Windows 10.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow running PowerShell script synchronously during Task Sequence

    When using the Run PowerShell script step in a Task Sequence, the Task Sequence waits for the completion of the script before continuing.

    It would be useful to have a "Run Synchronously" option to allow the Task Sequence to continue to the next step without waiting for the script to complete.

    At the moment I use the command line CMD /C START Powershell.exe to achieve this goal.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  11. setupcomplete.cmd

    Please hide the DOS Box with setupcomplete.cmd in the Task Sequence Windows 10 Upgrade process.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Offline servicing : install servicing stack update first

    When scheduling offline updates to OS images, make sure SCCM install the Servicing Stack Update before the Cumulative Update (or allow the users to determine which update has to be installed first).

    For example, I had an issue when trying to install SSU KB4498947 and CU KB4494440. SCCM tried to apply the CU before its prerequisite SSU, resulting in the CU being absent from the image.

    And the worst thing is that I cannot create another schedule for this CU as it is now missing from the list of available updates. As if SCCM permanently consider this CU as non…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
1 2 19 20 21 23 Next →
  • Don't see your idea?

Feedback and Knowledge Base