Software normalization built into SCCM reporting. An integrated solution to manage software inventory, software intelligence and license management. As a SCCM administrator it has been difficult to provide accurate reporting on installed software packages without purchasing third party normalization tools like BDNA or SNOW. Software normalization capabilities would be a great addition to SCCM.
1. Software Recognition Service that recognizes software requiring a license.
2. Software title normalization.
3. Ability to import all owned software licenses and then compare against what is actually installed.
4. Ability to recognize when software has been removed or upgraded. Example: if Office 2010 has been upgraded to Office 2013, will SCCM reporting show both Office 2010 and 2013 installed, same with Visio?
5. Ability to detect software version information. Example: SQL Server 2014 version, is it Standard or Enterprise?
System Center Configuration Manager has a good inventory agent, normalization would make it great!
Thank you and Regards

When I started working with SCCM years ago I was told that you're not really an SCCM admin until you accidently deployed MS Office to the whole company. Through my years of working with SCCM I've seen many people update a collection not knowing that there was a mandatory deployment attached which resulted in the deployment getting sent to systems that were not intended.
I would like to see a check/notification box added when a query based collection is updated that reminds you of the required deployments attached. This message will only show if an unexpired required advertisement is still set. This would ensure that admins understand the potential impact of their collection change.

There is a hard limit of 50 MBs for Hardware inventory set within the data loader for MIF file. If you enabled AI classes to collect more data by SCCM, it is not unusual for these computers to hit this hard-coded limit. This causes an endless loop of resyncs being performed by SCCM clients. the resync then consumes network bandwidth and processing time on the client/MP/etc. It is not until it hit the Data loader that these MIF files are rejected and ultimately a resync occurs to start the whole process over. The hard code limes should be increased to 200MB (for now), this will stop this issue and allow the computers to only send delata after the full inventory.

Since ConfigMgr is now more user centric, it would be nice if user specific settings(registry) are discoverable via Hardware Inventory ( or a new inventory function. I would not consider this a DCM as we are looking to query and report on the data that is on the users profile vs a DCM which checks for compliance. Example would be something like if a user has a proxy set, what is it. Another example would be discovering all the trusted sites a user has configured. This would help us identify sites that we may need to include in a GPO trusted sites deployment or if there are unwanted sites that people are trusting.

It would be very helpful if the Properties window of a device included all of the information in the Resource Explorer.

Motivation:
1. I almost never open the Properties view because it rarely contains the information I'm looking for. The Resource Explorer, on the other hand, has almost everything.
2. Having the Resource Explorer buried under a sub-menu makes it difficult to train and convince technicians to use it in their day-to-day workflow to find information and solve problems.
3. Since Resource Explorer is far more useful than Properties, it should be the easier of the two things to get to. Currently, Properties is a simple double-click while Resource Explorer is a right click, two mouse movements and one or two single clicks.

Implementation Ideas:
1. It could be a tab contained within Properties (while retaining a full version of Resource Explorer for when you need a larger window), or it could be a complete rework of the Properties GUI.
2. All information currently accessible still needs to be accessible.
3. Combined window still needs to be resizable like the Resource Explorer window.
4. Double-click on the device should open the combined window.
5. Lazy loading of data may be helpful if opening the embedded resource explorer hurts the responsiveness of the Properties window.

Alternative Suggestion: As an alternative, I'd be OK with having a console option that replaces Properties with the existing Resource Explorer as the double-click target. This may be more polarizing among the user base though as some users may prefer the quick access of the Properties window as the default target. If this alternative were implemented, it should allow the user to choose which view is their default.

My customer has +_ 600 maintenance windows using the server grouping feature .

Feature Request Nr1 : They use the node drain / node resume feature with PowerShell. They are still modifying and changing the script almost every week . That script is used for those 600 collections :

a) a central repository/place to enter the script details and be able to reuse that for each server group collection like for power management custom templates .
b) If they make a change in the “central” PowerShell repository , it keeps history ( Like application revisions ) and replaces that automatically in all Server Groups Collections where applied.

Feature Request Nr 2 : More options per server group

I would like to see a fourth option ( in the server group options) that is a combination of option b) and c) , meaning that you define a list but that from that list a number of machines in that list sequence can be patched at the same time. The reason is that you may have 20 servers in a maintenance window of 3h , then you don’t want to wait until the first one is patched , then the second one and so on . It would take way to much time to complete. If you have a predefined sequence list and you can from that list patch for example 5 servers at a time , that would help saving you time. Best one would be that you can create blocks in the sequenced list that can patch at the same time within the same maintenance window.

Feature Request Nr 3 : Powershell remoting (credential Manager)

Support for a credential manager within Configmgr where you can store certain credentials that the script (powershell remoting) need to run with ? to support a kind of “run as” scenario .

Feature Request nr 4 : Decent RBAC

Can you please create an RBAC role that only allows you to edit the maintenance windows or server group settings ? Reason is that most of the time , the business or release managers are defining their maint windows and not the server teams.