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. F8 debug window no longer prevents reboot / restart in Windows 10 full OS, after upgrading to 1606 from R2 SP1

    The problem is that after upgrading from R2 SP1 to 1606, customer found that the debug shell window no longer suppresses the TS from restarting the computer in full OS.

    2 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 →

    Updating status to completed as this is expected.
    We actually never guaranteed that the F8 command-prompt will prevent the rebooting of a machine. It was just a side-effect of the implementation.

    In older builds, we launch the command-prompt as part of setup-complete. This prevents the reboot while our setup-complete is still running. The problem is that with Windows 10, that will not work because the access to the desktop has changed.

    Now, we launch the command-prompt from the TS Progress UI. Reboots now proceed without waiting for the command-prompt because our setup-complete is not waiting for the command-prompt.

  2. Add the option to set timeouts on more task sequence steps

    We recently added a task sequence step which involves querying a Dell web API for warranty information to write to WMI during OSD. We use a Run PowerShell script step for that. Unfortunately the Dell API is not always responsive which can lead to the TS hanging up on that step. I'm going to create a program for it for now so that it has a timeout, but it would be great if the Run PowerShell Script TS step had the option to check a box and specify a timeout period like some other steps have.

    2 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 →
  3. Make hidden Variable really hidden

    In SCCM are normal and hidden variables. These hidden variables are not really hidden. For example, when you use them during Installation, those variables are visible in the clients logfiles.

    2 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 →

    Thanks for the feedback, we’d missed updating this previously.

    There’s now options in the task sequence editor to specify if the variable is hidden, this will hide the variable in the log too. Same for the Run Command line action. See https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902#other-improvements-to-os-deployment & https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/15282795-secret-task-sequence-variable-value-exposed for more detail

  4. Run powerShell Script task sequence step to set variable appends to existing value instead of replace

    When using the new Run Powershell script step in a task sequence in CM 1902 and you use the "Output to a task sequence variable" option and choose and existing task sequence variable the value returned from the powershell script is appended to the variable instead of replacing the value of the variable.

    Seems this should set the value not append the value.

    2 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 →
  5. There are no task sequences available to this computer

    We have experienced the issue for Unknown computers,
    "There are no task sequences available to this computer. Please ensure you have at least one task sequence advertised to this computer"

    As per below blog, this issue is fixed in 1702 update rollup
    https://blogs.technet.microsoft.com/configurationmgr/2017/08/03/error-there-are-no-task-sequences-available-to-this-computer-during-a-pxe-boot/

    However, the issue still occurring after 1702 rollup fix.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. 1 vote
    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 →

    Updating status to completed. That message is shown when thereā€™s no Applications added to the step and is expected.

    You need to create an Application with a deployment type that installs as System, then you can browse to select in the Install Application step. More details here ā€“ docs.microsoft.com/en-us/sccm/osd/understan..

    Hope this helps answer your question? If not, please let me know.

  7. Add Retry Count and Delay between to Task Sequence

    Add a retry count and delay between retry properties to at least the most critical task sequence steps, if not all, so that we can make task sequences more resilient when there are hiccups to servers or network.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Task Sequence Missing package error message include Package ID

    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.

    1 vote
    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 →

    No further response so closing for 1802

    Explanation of behavior:

    If you select a task sequence which has a missing reference the Deploy option is inactive (grayed out) ā€“ thatā€™s done to prevent deployment when all required content is not available.

    The task sequences view also has the References tab which shows the distribution status of all statically referenced packages

    Editing the task sequence with a missing reference will pop a dialog listing any missing references

    If you launch via PXE any missing references are listed ā€“ the package Id or App Scope are shown with the message to validate content and use the retry to refresh policy.

  9. C:\_SMSTaskSequence folder is left behind with permissions of everyone Full control over this folder only 50% of the times

    When you run a task sequence on a machine, a "C:\_SMSTaskSequence" folder is created and ideally removed after the successfuly execution of the TS.
    This is correctly locked down to Builtin\Administrators - Full Control NT Service\TrustedInstaller - Full control

    But we have seen instances where about 50% of the time, even when the TS completes successfully, this folder is left behind and not cleaned up, with the error as below:
    ===============
    Execution engine result code: Success (0) Cleaning Up.
    Removing Authenticator
    Cleaning up task sequence folder
    Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.
    Failed to delete directory 'C:\_SMSTaskSequence'
    SetNamedSecurityInfo() failed. ā€¦

    1 vote
    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 →
  10. Fix Install Applications step support with OSD standalone media

    During standalone media deployments the CM1706 client attempts to contact a MP when executing the Install Applications step and fails. Please fix this, as this capability worked, though limited, in ConfigMgr 2012 R2

    1 vote
    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 →
  11. PostOOBE

    Copied and pasted from a closed feature request.

    Below is a feature that we at the AFECMO could use to ensure that our branding can be competed in a singe TS step. With out this functionality we have to create a task sequence step to manually run setup.exe with the desired arguments.

    Several command-line options are available to upgrade Windows 10 (https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/windows-setup-command-line-options).
    By default, the "Upgrade operating system" task use the following command "Setup.exe /auto Upgrade /NoReboot /Quiet /DynamicUpdate Disable /ImageIndex 1 /PostOOBE <location> /PostRollback <location>" and if you want to use other switches, you must delete theā€¦

    1 vote
    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. Add foldering to Task sequence choice in WInPE

    Add foldering to Task sequence choice in WInPE

    1 vote
    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 →
  13. Provide usable workaround for multiple UUIDs

    Currently if we add a new machine to sccm, and the OEM was lazy and reused a UUID builds won't start, and there seems to be no easy way aside from standalone build media to get around this.
    since we have to provide a uuid and mac address when we create new machines, why is it not smart enough to use the mac with the generic uuid to identify the correct machine?

    1 vote
    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 →
  14. Add a custom section to osdinjection.xml

    Add a custom section to the osdinjection.xml fie (just like we have for configuration.mof), that makes it easier to add custom settings after the upgrades. As it is now, 1602 upgrade will override the existing file. Future upgrades might do the same. A custom section will make it so much easier for us to add our stuff back thus not loosing valueable changes.

    1 vote
    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 →

    Setting to Completed

    In 1606 release thereā€™s changes made to Boot Image Customization. \sms\pkg\sms00001 is now added to path ā€“ that package path is whatā€™s added in the Package used for the Prestart command (see Boot Image Customization tab)

    Any tools etc. in that path can be accessed in WinPE. Any updates can be done via updating the Package, then refreshing content.

  15. Stop filling smsts.log with useless ****

    Troubleshooting a failed task sequence is sometimes impossible, after the TS completes you sometimes end up with 3 files and 6MB of useless debugging junk, sometimes an entire 2MB file is full of nothing but lines like TS deleting 'CCM_CIVersionInfo.PolicyID=. It's amazing things ever work correctly with that much mayhem going on.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Task sequences that are run should be able to find out if the task sequence is run on a laptop, desktop or surface and run the job accordin

    Task sequences that are run should be able to find out if the task sequence is run on a laptop, desktop or surface and run the job accordingly. The power states might be different on them.

    1 vote
    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 →
  17. Exclude a mac address directly from the console

    I'd like to be able to add a mac address to an exclusion list directly from the console, in a order to use the same NIC (usb adapter) on different devices (example : pxe deployment).
    Today, we have to add manually the mac address in a registry value.
    The procedure is described in this Technet blog article -> https://blogs.technet.microsoft.com/configurationmgr/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/

    1 vote
    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 →
  18. Add pre-cache support for Required deployments

    Excited to see pre-cache support as some of my customers now have more laptops than desktops, and this will be crucial for the success of WaaS task sequences (it is not realistic to decouple application, driver, and maintenance steps from feature updates yet). However, why is it not supported for Required deployments? That is absolutely the scenario we wish to leverage it for - set a deadline and ensure that the content is there in the client cache before execution,.

    1 vote
    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 →

    Marking Completed
    This was answered on SMSTalk – the ability to precache content for required deployments has been around since v3 at least.
    Select Download all content locally before starting task sequence in the deployment wizard. Also, there’s a status message sent from client once content download has completed

  19. Add time-out option to Powershell step in TS

    Please add a time-out option to the "Run PowerShell Script" task sequence step.

    1 vote
    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 →
  20. Ability to upgrade Server Operating systems using Upgrade Task Sequence

    Just as we are all familiar with Workstation OS upgrades and using upgrade task sequences to move from a lower version to a higher version workstation OS I would like to ask that this be allowed for Server OS'es. Never mind the methodology you subscribe to when thinking of "upgrading" a server OS, having it as a 'possible' tool in the admin chest would be awesome.

    I recently discovered a bug on guest OS Linux RHEL 7 running on Server 2012 R2 Data-center Hyper V where the RTC clock injects very/different time wrong at boot. There is a fix "onā€¦

    1 vote
    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 →

    Hi Patrick,

    Apologies for the delay in updating this item. We do support upgrade for Server, our documentation didn’t call that out directly and I made sure that was updated. See – Ability to upgrade Server Operating systems using Upgrade Task Sequence
    That was updated last September and I forgot to loop back on your User Voice time

    Also, passed this information re: Server support to our CSS to make sure everyone’s on the same page

  • Don't see your idea?

Feedback and Knowledge Base