System Center Configuration Manager Feedback

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.

Standard Disclaimer – our lawyers made us put this here ;-) Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos which you do not want to grant a license to Microsoft. See the “User Voice Terms of Service” link below for more information.

How can we improve Configuration Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.

You can remove your votes from an open idea you support.

To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Tell us your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

We’re making some good progress on this. We’re going to deliver these improvements in multiple phases. Currently working on phase 1, which will make 3rd party patches easier to use out of the gate, just in the sccm console.

The windows 10 adk has changed a few times since the original release of Windows 10, there have been two major releases and one hotfix to fix issues with the second release, as a consequence of that many people got jittery about upgrading to ADK 10 1511.

How are we going to deal with this in a good way, a really good way. Prior to this we didn't have to upgrade our boot images every 6 months or so.

Here's the suggestion:-

#1. When we update from 1602 to 1607 (or whatever) to support the next generation of Windows, it would be great if (via) the configmgr updates and servicing node that during the installation of the next update pack, that it automagically uninstalls the current ADK, downloads the new Windows 10 ADK, installs the new ADK and continues with its' business until Configmgr XXXX is upgraded.

And wouldn't it be great if that behaviour was available via the wizard as a choice

Automatically update the Windows ADK [Yes/No]

#2. Secondly, we may need to revert to a previous version of the ADK due to unseen issues therefore another option that we'd want would be to allow the ability to rollback the Windows ADK to the previously installed version via a choice:

Rollback ADK [Yes/No]

#3. Thirdly, let's imagine the 1511 ADK scenario, where an ADK is released, has issues, and everyone finds out, and they rollback to the previous version. How about the Updates and Servicing node also allows resolution of this via an ADK hotfix ?

Install applicable ADK Hotfix [Yes/No]

cheers !
niall

The windows 10 adk has changed a few times since the original release of Windows 10, there have been two major releases and one hotfix to fix issues with the second release, as a consequence of that many people got jittery about upgrading to ADK 10 1511.

How are we going to deal with this in a good way, a really good way. Prior to this we didn't have to upgrade our boot images every 6 months or so.

Here's the suggestion:-

#1. When we update from 1602 to 1607 (or whatever) to support the next generation of Windows, it…

With a standalone WSUS-Server deployed Windows Updates can be uninstalled/removed from clients. With SCCM SUP this is not possible,
Implement a function to remove installed Windows Updates from clients.

It would be really great if when configuring an Automated Deployment Rule you could configure it to run based on the number of days / weeks since "patch Tuesday" (especially in countries other than the USA where "patch Tuesday" is actually a Wednesday and not necessarily the second Wednesday of each month). I currently get around this by having a script detect when patch Tuesday has passed and subsequently execute an ADR and create one or more deployments based on the number of weeks since that date. This works fine, but an in product solution would be better

When I go to the Windows 10 Servicing Dashboard, I got a nice PieChart of the Windows 10 Clients and their Version.
But when I click on the PieChart, nothing happens. It would be great to have the same experience on this Dashboard like on the SCEP Dashboards.
That means, if I click on the PieChart one of the Windows 10 Version, a new collection would be opened, with the corresponding Devices.

WSUS has an inbuilt option to control the approval /Auto Approval of revised updates.
However ConfigMgr is missing this feature. This is causing the revised updates to get auto installed on the clients if the deployment is active.
The latest example for this issue was KB3172605. This was revised by MS and caused auto install with reboot on clients

Currently behavior is that if Software Updates have installed and a restart is required, initial notification will pop up and then disappear. User may not have seen notification and often will not see any further notifications unless they happen to be in front of the system at just the right time or see the final no-dismiss dialog.

Would be great to have the initial restart dialog remain on screen until user dismisses (or initiates restart) to ensure dialog is seen by user. Dialog should include time remaining to restart deadline.

It would be very helpful to be able to set maintenance windows to be relative to Patch Tuesday. For example, apply patches on the 1st Saturday after patch Tuesday, or the second Sunday after patch Tuesday. Since patch Tuesday changes each month, the current "second Saturday of the month" type options are not useful when Patch Tuesday could fall before or after that depending on the calendar.

I would like option 4 to be possible. Without this it seems quite easy for users to miss seeing the balloon notification and therefore not know that a restart is coming.

It would be good if there was an option in Client Settings > Computer Restart to automatically show the temporary restart notification window. It would also be good if there was an option here to permanently set the 'SCNotification.exe' in Notification Area Icons to 'show icon and notification' to further improve the visibility to users of pending restarts so they know to save their work before they leave their computer for lunch or when they go home.

I've attached an image of the temporary notification window I am talking about

Thanks,

Andrew

Here is the User experience for the update process as I understand it:

We have a few Software Updates that we just don't deploy. Every month, our list of "Needed, but not deployed" updates show these updates (for example, IE10). I want a way of filtering these out so we don't accidentally deploy them.

I tried doing a search by adding the article IDs, but this doesn't work (as the attached screenshot shows).

Maybe allow us to add a custom category for individual updates (such as "Do not deploy"), so we can then include these in our search.

When you only use ConfigMgr to install updates, the date on the Windows Update control panel applet often reflects something that is really inaccurate as ConfigMgr doesn't update it. This often leads to a very negative reaction of "I thought those darn ConfigMgr admins were updating our workstations and servers!?!" And then we have to explain that we are, but that date doesn't get changed.

Can we please just ensure that when Software Update Management installs any updates, the Windows Update control panel applet gets set to the current date?

When you only use ConfigMgr to install updates, the date on the Windows Update control panel applet often reflects something that is really inaccurate as ConfigMgr doesn't update it. This often leads to a very negative reaction of "I thought those darn ConfigMgr admins were updating our workstations and servers!?!" And then we have to explain that we are, but that date doesn't get changed.

Can we please just ensure that when Software Update Management installs any updates, the Windows Update control panel applet gets set to the current date?