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.

There are well documented issues with issues when using older versions of the Windows Update Agent. The configmgr client install still just checks for the base level of the Windows Update client. The client install should include the most up to date windows update agent so that customers will not be required to deploying the updated agent after client install to resolve known scan and related issues.

Need certificate based communication between site server and site systems for server role installation. Need to remove dependency on RPC Dynamic ports and use WinRM SSL for secure communication and installation of site roles. This would improve security by eliminating a high range of ports that must be open between site systems.

Select a collection and trigger clients to run a software update deployment evaluation cycle. For those scenarios where you need clients to check for updates (now) prior to the default schedule (5 days) that you setup in client settings.

Ok, i try to explain my problem.
Office 365 Updates are not fully integrated to WSUS. When i use an upstream WSUS in my environment with downloading content locally, the o365 conent is only a dummy content, the real content is downloaded from MS.

So, when my SUP has no internet connection, i have to configure a proxy for downloading it. But this is greyed out or not possible when using an upstream WSUS. I have to configure the SUP to go directly in the internet, and than i have the option, to configure the proxy.

Full Office 365 Integration with upstream WSUS

Ok, i try to explain my problem.
Office 365 Updates are not fully integrated to WSUS. When i use an upstream WSUS in my environment with downloading content locally, the o365 conent is only a dummy content, the real content is downloaded from MS.

So, when my SUP has no internet connection, i have to configure a proxy for downloading it. But this is greyed out or not possible when using an upstream WSUS. I have to configure the SUP to go directly in the internet, and than i have the option, to…

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 - Click two - Start loading [---100%---] OK, everything is back, put the old machine to the same delivery box and leave to posting.

Simple and powerful.

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

As there may be situations that admin would like to get extensive reporting if GPOs are in place and effective as planned in their organization, would be nice to have some dropdowns or listitems of GPOs that one could select to be as Configuration Items.

1000's of GPOs are available but sure MS has some ready list/xml/whatever that could be included in SCCM CI so reporting of GPOs, as they are just reg values, would be possible.

Delta Discovery doesn't pick up the changes when you move OU's and objects around in AD and kicking off a Full System, User or Group Discovery with all of the Container paths is very inefficient so it would be nice if there was a way to do a one-time discovery from a path you set using the browse button.

We often export packages from QA to production, but the export does not include the deployments. Also, collections are not included so we have to 1. export collections, 2. Export TS or package, 3. Manually recreate the deployments.

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.

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.