Microsoft

Microsoft Endpoint 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 Microsoft Endpoint 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 Microsoft Endpoint Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve 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. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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

  7. Implement a "Suspend Task Sequence" Step in OSD like the LTISuspend.wsf script in MDT

    During a build and capture task sequence, it can be necessary to suspend the build so that one can run some application installs, make customization's, etc. These customization's can require reboots, which kill the task sequence. Please implement a solution similar to the LTISuspend.wsf script in MDT, where you can run the step and it creates a shortcut on the desktop to resume the task sequence.

    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 →
  8. OS Upgreade TS: Add percentage complete next to the install bar.

    OS Upgreade TS: Add percentage complete next to the install bar. It would be easier to keep tabs on the installations.

    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 →
  9. Inject files/commands in boot image properties page.

    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

    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 →

    Marking completed for 1802

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

    The doc link – docs.microsoft.com/en-us/sccm/osd/get-start..
    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.

  10. creating image for windows 10 for sccm

    Would like to capture and deploy image of windows 10 PC to SCCM

    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 →

    Updating status to completed.

    Support for Windows 10 was added in our 1511 release back when Windows 10 was released. As well as the same Build, Capture, Deploy we’ve had for all previous Windows versions we added a new In-place Upgrade task sequence template and step

    https://docs.microsoft.com/en-us/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems

    Is there a gap in the functionality you’re seeing or something else – let us know, we’d like to address your ask and help you with deploying Windows 10.

  11. Add import code button to new Run PowerShell script task sequence step

    The 1811 Technical Preview added a "enter or paste a PowerShell script" function to the "Run PowerShell script" Task Sequence step. That is an awesome feature, but even more awesome would an import code button that automatically puts the code in for you when you direct it to a .ps1 script.

    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. failed to run task sequence due to missing content - show package ID not GUID

    When you start a task sequence and it starts off by validating content. If it can't find a given package/application, it used to just say something like "content for package ID ABC000123 could not be found on any distribution points". That was super easy to find in the console and either update distribution points or whatever needed to be done.

    With the 1702 update, it appears package ID has been replaced with ScopeID(longnastyGUID)/Application(Anotherlongnasty_GUID). When this happened to me last week, I couldn't find the ScopeID or Application GUID anywhere in the console, and had…

    0 votes
    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 →

    No response back, closing for 1802

    The message you’re seeing is for Applications – Applications use CI’s rather than the ABC00001 you see for SWD Packages, Boot Images, Task Sequences etc.

    In the Software Library, Applications – add CI Unique ID to the columns view. Type in the first few characters of the CI and any apps that match that are shown. You don’t need the column – I’m just suggesting that to help illustrate.

    In the Task Sequence view, the References tab shows all referenced content and distribution status. Right-click on any item and you’ll be shown which Distribution Points have that item. Also, the Object ID will show the CI/GUID or Package Id depending on the item type.

    Another option is selecting the Task Sequence and selecting Distribute Content – the wizard will show any referenced content that is not yet distributed.

    Lastly, within the Admin Console…

1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base