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. Pre-Cache In-Place Upgrade - TS Variable to set OS Source

    When doing a In-place upgrade and using Pre-Cache, the Task sequence process copies the needed files from Cache to _SMSTaskSequence\packages. This process can take some time when the in-place upgrade media is more than 4GB. this is unnecessary, there should be a variable to say install the OS directly from cache, or like the task sequence step to Download package content have a variable for the pre-cached source files that can then be used to access the OS later when upgrading, so that the content does not have to be copied from cache to the _SMSTaskSequence folder but rather accessed…

    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 →
  2. Fix OSD Re-run Behavior

    Consider the following...

    You Deploy an OSD TS to a Lab and the Lab images Successfully. Next year you wish to Refresh that same Lab. You deploy this TS to the lab with the default 'Re-run Behavior' and it immediately shows as Successful because it was run before. You do another schedule and switch the 'rerun behavior' to 'Always rerun.' Lab images, grabs policy, images, grabs policy, images.........

    This seems like a huge flaw to me especially for those environments that Refresh certain Labs annually (K-12, Education). I'll now have to remember each Summer to either create a new TS…

    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 →
  3. Install Software updates TS step improvements

    The "Install Software Updates" TS step could use some improvements, including adding an option to run a package after the reboots (before update step continue), and customizing the restart time-out and messages. The status messages are also pretty vague. For example, we know that after it installs the updates it can check for updates again, but it doesn't actually say when it's doing that. I've also noticed some blank black screens showing up for at least a minute as it is about to reboot.

    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 →
  4. Let the TSAgent consume enough RAM in VMs configured with Dynamic Memory for OSD compatibility checks to succeed

    Setup: Hyper-V Gen2 VM configured with 1GB startup RAM, Min 512MB, Max 4GB.

    I was testing servicing Windows 10 1511 to Windows 10 1607 on my VM and the compatibility check failed because the VM was only consuming 1560MB at the time of the compatibility check. I'd think that it would be able to tell if the VM's maximum RAM value was higher than the minimum RAM requirement for Windows 10.

    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 →
  5. OSD - task sequence media - network

    the task sequence media has been created for offline scenarios, so the data does not get copied to the sccm. it would be great to have a task sequence media that is online, so all information is also sent and the checks also happen, like a boot image does, the only difference would be instead of downloading the software from the DP it would use the local usb/dvd disk

    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 →
  6. OSD - task sequence media

    when creating a stand alone media, a option to update an existing ISO would be great. also, would be great if you could create an iso and an extract of the iso (like on MDT) so when you copy the files using a slow link connection you only need to copy the changed files and not all files.

    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 →
  7. 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 →
1 2 20 21 22 24 Next →
  • Don't see your idea?

Feedback and Knowledge Base