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

    29 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. Suppress user logon while using Task Sequences outside of OSD that require a restart

    When using task sequences to deploy applications or settings that require a restart, please include a check box on the "Restart Computer" action to suppress the user logon actions (ie. Ctrl + Alt + Del).

    27 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 →
  3. PXE Boot menu with selection of additional images (e.g. MDOP DaRT)

    There is a buisiness need to be able to select a different bootimage as the one linked to a task sequence. This can be used for administrative tasks of a client such as booting MDOP DaRT over the network. Implement the ability to define which bootimages can be selected at a TFTP boot. (Of cause, OSD is only possible with the image linked to the task sequence)

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

    Updated by bobmn for sangeev/OSD

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

    26 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

  5. run not only applications on a tasksequence, seperate deploymenttypes would be better

    Not only applications or packages/programs run in a TS would be nice to select a special deploymenttype to run. In packages with programs is it possible why not with applications and his deploymenttype.

    24 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

  6. Make Windows 10 Setup Compatibility Scan Language Neutral

    It would be nice if a checkbox "Perform Windows Setup Compatibility scan withnout starting upgrade" inside "Upgrade Operating System" step in SCCM Upgrade Task Sequence would be language neutral.

    What I mean by this is that we would like to run this scan prior to the Upgrade itself but to be able to do that currently we have to switch the running OS to en-US (the same language as the Upgrade iso), then run the scan and in case an error is found, we need to switch back to original language again and reboot the computer. This is not aā€¦

    23 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 →
  7. Possibility to priorize an (InPlace) Upgrade Task Sequence over Update Installation

    Since Microsoft introduced the strategy to deliver two new OS builds per year for Windows 10 and a mandatory expiry date of SAC builds, the focus / Engineering task focuses back to perform in place Upgrades via Task Sequences.

    As those Task Sequences are not deployed at a specific time during the week it might happen that some Windows OS Quality or Office Update are pending or queued for Installation. It does not make sense to deploy a Quality Update for the OS Build which is queued to be upgraded to a new OS Build (with new Quality Updates).

    Myā€¦

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

    23 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

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

    22 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

  10. RBA During Unknow OSD

    With unknown computer deployments, there should be an authentication step that allows the deployment technician to authenticate to SCCM so he\she will only see the deployed task sequences to the unknown computer collection that are ONLY scoped to them instead of seeing all task sequences deployed to the unknown computer collection.

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

    Refreshing status on this item.
    See https://docs.microsoft.com/en-us/mem/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.

    Would using SMSTSPreferredAdvertID solve this for you?
    https://docs.microsoft.com/en-us/mem/configmgr/osd/understand/task-sequence-variables#SMSTSPreferredAdvertID

    That way each technician would only know the task sequence deployment IDs assigned to them. They’d enter the ID to start the task sequence, simple script example
    dim env_set
    set env = CreateObject(“Microsoft.SMS.TSEnvironment”)

    AdvID = inputbox(“Preferred Deployment ID” ,“Please enter the deployment ID:”,"",400,0)

    env(“SMSTSPreferredAdvertID”) = AdvID

    env_set = "Preferred Deployment set to: " & env(“SMSTSPreferredAdvertID”)

    ’MsgBox( env_set, vbOKOnly, “Result”)
    MsgBox( env_set)

    with that added as a Prestart command in the Boot image properties – use as a batch file.

  11. Built-in OSD Tattoo Steps \ Registry Edits

    We currently have custom scripts that run during an OSD Task Sequence that Tattoo the registry with the computer name, technician who started the TS, date, TS name, TS Version, etc. etc. I would like to see a built in step where you could fill in these values whether it be a static value in or a variable. This built in tattoo could also already be in the hardware inventory by default so we can build collections around task sequence versions.

    We also have a TS that we use primarily for a kiosk w/s and is set to AutoLogon toā€¦

    21 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. More meaningful TS error messages in UI (no more 0x80004005!)

    When a task sequence fails, the most common error message that you see is 0x80004005 which is useless. Normally, you get much better information from SMSTS.log file, but there are scenarios when you cannot access SMSTS.log.

    There must be a way to provide more meaningful error messages in UI when a task sequence fails.

    21 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. We have made some improvements to the task sequence monitoring – adding columns for Exit Code and Action Output to the status view.

    We’ve more work to do replacing use of Generic E_FAIL with more meaningful error codes.

    Updated by bobmn for sangeev/OSD

  13. Updating Content shouldn't cause running task sequences to fail

    When you update content that is referenced by an application, devices currently running the task sequence will fail when they get to that step because the version of the files they were expecting is no longer available.

    It has been suggested before to keep old versions of the content around on the DP so that these devices can successfully finish.

    My suggestion is to either do that, or change it so that the content request is for a version equal to OR GREATER THAN what was validated at the beginning of the task sequence. This would be useful both insideā€¦

    20 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 →
  14. Enable New-CMBootableMedia to use a Cloud DP (or Content enabled CMG)

    This Cmdlet does not support using a cloud distribution point as the distribution point source (and neither does the GUI).

    This means that in order to use this feature we have to have an on-premise DP purely for this purpose.

    Regards
    Wayne

    19 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 →
  15. For the option to "Run only on the specified client platform," include the option to specify specific Windows 10 branches.

    Include the ability to select specific Windows 10 branches for the option "Run only on the specified client platform." I have scenarios where I would like to limit certain task sequences and/or packages to e.g. current branch 1607 but not 1703.

    19 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 →
  16. OSD - Have different command-line options in the "Upgrade Operating System Task Sequence" to upgrade Windows 10

    Make the Upgrade Step more customizable. I'd actually like the ability to remove the /quiet tag from the setup.exe command line, and be able to add the additional commands right on that step instead of having to add additional steps to create the those variables.
    Add Check boxes for additional preset parameters to enable /disable, and text box to add custom (reflect drivers, etc)

    19 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 →
  17. Provide a framework for vendors to provide driver packages directly into SCCM

    It would be nice to have a driver package catalogue, which is populated with packages built by vendors for their hardware. Vendors are best placed to release drivers for their hardware so why not leverage this knowledge and integrate it fully in SCCM?

    17 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

  18. Offline Image update on schedule

    Option to Automatically update Offline Windows Image on schedule.

    So that My Custom Windows 7 with preinstalled software will alway have all windows updates already in the image when its deployed.

    An option in SCCM to pick few images that SCCM would automatically update on set time. Eg after patch tuesday. s

    16 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

    We took a look at this – one potential drawback is the there’s no user interaction meaning the updates applied would be what’s presented in the Offline Servicing view. That’s the default view – filtered for that architecture.

    Would that selection be acceptable?

  19. Enable Download Package Content step for stand-alone media

    The Download Package Content step fails when used in stand-alone media. However, during media creation, the package content specified in the Download Package Content step does get added. Despite this, the step still fails.

    16 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 →
  20. OSD - Create Variable to control creation of DisableCMDRequest.TAG in Setup Windows & ConfigMgr Step

    During OSD, specifically the Setup Windows & Configuration Manager Step, the step creates the file DisableCMDRequest.TAG right before rebooting from WinPE into the Full OS

    This disables the F10 prompt during the Windows Setup.

    Could you allow us to change this behavior via TS variable?
    Example: SMTSTDisableCMDRequest = False

    [Bonus] Then also automatically set the it to false if TSDebugMode = True

    This would be helpful for troubleshooting Windows Errors during Setup before the TS kicks back in after setup. (SetupComplete.cmd runs)

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

    Thanks for your suggestion. Updating status to noted – see https://docs.microsoft.com/en-us/mem/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.

    Can you elaborate with some examples of why this would be needed?

    We already have the task sequence debugger and comprehensive logging. https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/debug-task-sequence

    Also, Windows developed SetupDiag which can be run from the task sequence or used on setup.exe completion https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

  • Don't see your idea?

Feedback and Knowledge Base