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. Allow unsigned drivers to be added to Boot Images

    By default when ConfigMgr adds drivers to a boot image, unsigned drivers are not allowed and causes the 'Update Distribution Points' action to fail with the following error in C:\windows\logs\dism\dism.log:

    Cannot install non-signed boot-critical drivers on amd64 images. Use /forceunsigned switch to override.

    The workaround is to manually add the unsigned drivers to your boot image using DISM and /forceunsigned.

    If we could automatically add the /forceunsigned switch when ConfigMgr attempts to update the boot image, this would be a non-issue.

    14 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 →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

  2. Support OSD over Wireless

    As more and more devices are shipping without wired network adapters, and more business areas are going "wireless only," the traditional ability to reimage a device in place is getting scarce. This is especially true in primary and secondary education institutions.

    Please provide support for adding Wireless drivers to WinPE, and the ability to provision wireless network profiles for the WinPE phase of the task sequence to enable imaging over wireless network connections.

    479 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    19 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Updating this item as there’s support for Windows 10 In-place upgrade using the Cloud Management Gateway – see https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1802
    Adding this in case some folks missed it or Win 10 In-place upgrade addresses their requirement.

    I recognize this it not full OS Deployment as there’s no WinPE phase (WinPE has no wireless stack)

  3. Allow to select WinPE language pack when you generate Boot Image

    It would be great to customize WinPE language pack when Generating standard or MDT Boot Image, like select box that will list lp.cab that are present in ADK installation folder "Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs"

    11 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 →
  4. Boundary Group Variable

    Create an OSD task sequence variable for Boundary Group(s). Ex. OSDBoundaryGroup = VPN_ABC

    10 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 →
    Noted  ·  sangeev responded

    Thanks for providing that detail – much appreciated.
    We agree there’s a lot of value with such an addition.

  5. Add Architecture Column in Driver Catalog

    Add a column in the Driver Catalog for x86 and x64 Architecture.

    It would also be nice if Architecture was searchable in the Search field.

    5 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 →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

  6. Have a Task Sequence Step to call the Uninstall of an Application and support both the Standard Install and Dynamic Install.

    While a Step for Run Command line can be used for most Windows Installer, if an application uses a EXE it would be nice for the application to be downloaded and the exe used.

    34 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 →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

  7. Revision History for task sequences

    Could you add Revision History for task sequences? It would save you the effort of exporting and importing task sequences or keeping copies for References. This would be a nice to have feature in the Configuration Manager Console - although I'm sure we all have a scheduled job for exporting SCCM configuration automatically anyway.

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

    Thanks for the feedback. Task Sequence export/import has Administrative comments field that can be used as well as the task sequence properties.
    There’s no console versioning for task sequences currently but this is noted for future.

    Updated by bobmn for sangeev/OSD

  8. Maximize import driver window when selecting drivers

    When importing drivers to catalog, I get a window to select/tick drivers which the CM has read from inf files and import them. That window has very poor capability to scroll and view full paths and other info of drivers. It would be better, if I can set/fix/maximize the size of that window and drag columns how ever I like to. Now selectind and seeking between x86 and x64 folders, or OS folders is pain.

    4 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. Simulate Task Sequence

    I'd love an option to run a Task Sequence in simulation mode (potentially on a Virtual Machine) that can check for any "logic" issues in the Task Sequence. As an example, I just made a change to an MDT Integrated Build & Capture TS to just be a WORKGROUP machine, rather than domain joined. I made the necessary SMSMP= change to the ConfigMgr client install for application installs to work, but I forgot to change the capture path to a FQDN - therefore it got the whole way through and failed. A quick simulation would have saved me 45 minutes.

    22 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

  10. Use SMSTSRebootDelay value during 'Install Application' Step

    Use the value from the built-in variable SMSTSRebootDelay for reboots that occur during the 'Install Application - Install applications according to dynamic variable list' step. This would reduce the time for OS deployments.

    41 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

    This is also similar to ‘Allow suppression of exit codes during Install Application Task Sequence Step’
    Updated by bobmn for sangeev/OSD

  11. Display Task Sequence Step no. in Task Sequence Editor

    Display the Step No. in the Task Sequence Editor so it can be easier to find where in the TS an issue is occurring. This could be handy because you could have multiple steps of the same name (especially gather & User Toolkit)

    33 votes
    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 →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

  12. Change State migration point to user based

    You could automate the computer change, if State Migration Point would be user based, not computer based (and existing linking created). When user get's new laptop from pre-installation, she will open it from package and connect cables. After that she logs on and runs State Migration Recovery that loads everything back to the new operating system.

    If using user based model, you don't have to manage MAC-addresses (that aren't in fact known beforehand). Easy to use for end-user:

    1 - Click one - Start scanning [---100%---] OK, shut down the old machine and log on to new one
    2 -ā€¦

    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. Mark easy way to query Driver Versions of all drivers on a system.

    Please make an easy way to query Driver Versions of all drivers on a system from SCCM Hardware inventory without creating a custom MOF or looking at registry files? I found a forum thread on TechNet a few years old that said Microsoft said that using WMI class win32_pnpsigneddriver was unreliable and is why it was not available in SCCM hardware inventory and they were considering removing the class entirely. However the class remains in win 10 and is still the only way to query driver version using a script. It would be really useful to be able to haveā€¦

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

    Updated by bobmn for sangeev/OSD

  14. AD Authentication for PXE boot

    It would be useful to integrate AD authentication in the WinPE boot image for PXE boot OSD.

    When deploying operating systems with MDT and WDS, users are prompted to authenticate against AD when PXE booting. However, in SCCM the only supported way to secure the PXE point is with a DP password that all users share.

    There are third party "hacks" which can integrate AD authentication in the WinPE boot image (Johan Arwidmark's ADSI drivers) but it seems like this would be simple to implement within the product itself since it is already done in MDT/WDS.

    41 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 →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

  15. OSD Win PE error codes

    instead of having error codes when deploying OS deployment Task Sequences that the end user or administrator has to struggle to find out what the code means only for it to be the hard disk is too small. Could the error codes if already known be displayed with meaning full reasons rather than error 0x8004352

    4 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

    Thanks for the feedback. This is the same as ‘More meaningful TS error messages in UI (no more 0×80004005!)’. I’ll look to see if they can be merged.

    Updated by bobmn for sangeev/OSD

  16. Run Task Sequence with local administrator account context for B&C scenario

    in MDT OSD the task sequence runs with local admin context. that's why B&C are more easy in MDT because we can modify the admin user's shortcuts, pinned items, registry keys, etc... and then capture it with using the <CopyProfile> tag in the unattend.xml and have the settings copied to the default profile.
    It will have a huge impact to be able to do the same in SCCM OSD without custom scripting on the default profile that some of them aren't possible without <CopyProfile>.

    9 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

  17. Provide GUI option in disk partitioning Task Sequence step to guarantee drive letter selection

    We were trying to build a Windows 10 deployment and got stuck for a little while. We used the 1511 WIM from VLSC and had the OSPreserveDriveLetter = True variable. We did NOT do a build and Capture to create the customized WIM. We used the Stocked 1511 WIM to try and lay down the Windows 10 Image.

    After lots of reading, troubleshooting, and frustrations, we were finally able to get the TS to use the C drive to lay down the OSDisk.

    It would be awesome if we could have a task sequence step that allows the OSD adminā€¦

    6 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 →
    Noted  ·  sangeev responded

    In 1606 we have deprecated OSDPreserveDriveLetter – instead of using the captured driver letter the change leaves Windows Setup to determine the best drive letter.

  18. Add option to "Run PowerShell Script" Task Sequence step to run as a 64-bit process

    Posted as a bug on connect (https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/2183906) but would also like this as a feature. We are running a PowerShell script that adds Microsoft .NET Framework types (classes) to a Windows PowerShell session (via Add-Type). On 64-bit OS it must run under a 64-bit PowerShell process in order to be successful. Otherwise it just fails with exit code 1. As a work-around we can run a command line step.

    5 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. Allow for an advanced filter under 'Run only on..' in task sequence

    Allow for a WMI filter or alternative in the advanced tab of a task sequence so we can run only on that hardware type. For example I have an OSD task sequence that I need to advertise to unknown however I actually only want to run on Model XYZ. This should be evaluated at the WinPE stage and then drop out of the TS if no match is found. This could equally be used similar to the existing format with a TS advertised in the software center.

    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 →
    Noted  ·  sangeev responded

    Thanks for the feedback. We’re looking at moving the functionality of the Check Readiness step to the task sequence properties and this is one of the additions were considering. Please note this is not scheduled work yet.

    Updated by bobmn for sangeev/OSD

  20. Windows 7 vNext

    Windows 7 is in extended support until 2020.
    If extended support ends, it is likely removed from SCCMs supported OSes.
    In certain cases you have to keep Windows 7 "alive", e.g. factory, where the cost of the machine that the PC is controlling is far higher, then in an office environment.
    To keep this systems alive we canĀ“t deploy a cloud solution.
    Deploying the cloud will have the risk we canĀ“t control the Windows 7 machines anymore and canĀ“t setup a new machine anymore, in case the old one needs to be replaced or reimaged.
    So keeping at least aā€¦

    3 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

  • Don't see your idea?

Feedback and Knowledge Base