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. 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 →
  2. 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ā€¦

    88 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

    Updated by bobmn for sangeev/OSD

  3. 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.

    36 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

  4. 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

  5. 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

  6. 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.

  7. 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 →
  8. 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

  9. 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

  10. Add Battery, Power state check to Task Sequence "Check Readiness"

    Add Battery, Power state check to Task Sequence "Check Readiness"

    Would be nice to add an extra option there to check the power state, this is very important for when making a task sequence available to the user.

    31 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

    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

  11. Enable "Servicing Screen", similar to W7 Thin PC for large upgrades to prevent PC use...

    Enable a "Service Screen" (similar to W7 Thin PC) for Software Updates, OSD, large-chained deployments to prevent PC use. Make it optional for the Admin to select to use it and basically reboot into "maintenance mode", run all tasks/Adverts and re-enable the standard UI again on the last reboot of the sequence. Enable the OS to get around this mode in safe boot, if necessary...

    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

    Updated by bobmn for sangeev/OSD

  12. Allow suppression of exit codes during Install Application Task Sequence Step

    During an OSD deployment we install several applications that return a reboot exit code.

    Each time they install they reboot, rebooting takes a minutes or two to restart the task sequence engine so each application is adding 2-3 minutes to the build time.

    I would like to ignore these reboot exit codes because I know I will be rebooting at the end. We would prefer to not have a separate application for OSD and for Software Center.

    28 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

  13. Introduce TS step to rearm Office

    As we have TS step to sysprep Windows and ConfigMgr, it would be also highly usable to have a step for rearming Office installation after deploying the image.

    Now it's usually done by "Run command line step".

    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

    Updated by bobmn for sangeev/OSD

  14. Allow for multiple task sequences on a single stand-alone media

    Currently you are limited to a single task sequence per stand-alone media. This means techs have to carry around multiple USB flash drives, one for each task sequence.

    If each task sequence is using the same boot image I see no reason why this can't be done. You can combine all the package references into the ..\SMS\PKG folder and then the only differences are in the ..\SMS\data folder which is basically just the task sequence XML and variables.

    15 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

  15. DCR: Task Sequence Export / Import

    Add an optional option to provide new source location path for each package, application, ... when importing a Task Sequence that has been exported with content and references. Imagine you have 2 ConfigMgr environment a Test and a Production environment completely isolated from each other and you want an easy way to sync. A cool thing would be to only export "Metadata" of the Task Sequence and all References (Applications, Packages, ...). At the target site you have the same folder structure for content source for example \\sccmsources\share\Applications,\\sccmsources\share\Packages, ... and so on. If you start the import, you will beā€¦

    64 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

  16. DCR: OSD Task Sequence - Create Baseline of existing TS and allow Remediation

    From my field experience I have seen many times OS Deployments which did not really succeed, because of Continue on error conditions. In most cases the reason was to not end up with systems staying in Provisioning Mode. I know some guys just "re-deploy" the TS with checks if everything was done properly. This brought up the idea - why not using Compliance Settings for this purpose? At least to check if the system meets the Desired Baseline. Everything needed should be stored in the Task Sequence anyway and it would allow a "Report" summary client side after Deployment.

    0 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 →
  17. DCR: Boot Images. Provide an option to prevent re-downloading boot images (Boot / Prestage Media)

    Scenario: You create a Boot Media or Prestaged Media. Current behaviour is that as long as the boot image version from creation date matches the version inside the infrastructure everything is fine. System is starting Windows PE and executes the Task Sequence. If you add for example a new driver now to the boot image the new version causes Configuration Manager to download the boot image inside Windows PE and another restart into the updated version of the boot image. In case of a Prestaged Media scenario this painful, as UEFI systems might no longer work.

    Possible SOLUTION: Add aā€¦

    61 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. Should be easier to re-deploy the same machine in OSD (unknown)

    Should be easier to re-deploy the same machine in OSD (unknown)

    5 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

  19. Ability to easily copy files during TS to any location on computer

    It would be nice to be able to have a built in step to be able to select a folder/file from a share and then a location on Windows to copy the files to.

    6 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

  20. Deploy multiple task sequence to a collection at once

    Why is not possible to multi-select task sequences and deploy them at once to a (user or device) collection? Now you have to deploy them one by one. In test scenario's where you have a device collection with test machines and hundreds of task sequences you want to deploy to the collection, you have to do it manually one by one. Not really efficient.

    6 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