The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications.

We have a number of clients that are multi-homed, the SCCM client is often choosing interface that cannot communication with the SCCM infrastructure to determine site membership.

Our clusters fall into this category. 'secure web application servers' that have a "Client Network", "Admin Network", "Backup Network" and "Management Network" connections.

May something similar to the NOSMS file, that will tell the client to not use specific interfaces but continue to inventory, configure, etc.

When creating custom discovery data using the smsresgen class there is no way to remove this from the discovery related tables in ConfigMgr. Since there is a supported way to add this data, there should be a supported way to remove it. This is necessary as a rollback option, to return ConfigMgr to its default state, before the custom discovery data was added.

In our enterprise we have quite a few locations where 802.1X is impelemented, e.g. networks port-based network access control and/or VLANs. Some locations even use DHCP snooping.

We would like to implement SCCMs wake-up proxy feature in these locations but it is not currently supported. Also, network administrators are concerned about the IP-to-MAC mapping (MAC flapping) feature used in wake-up proxy.

Please provide us with wake-up proxy support that will work on any type of network.

When System Discovery finds an object that seems invalid, currently it won`t be imported (which is good).
ERROR: System <systemname> is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is: ().
However if the same object has an AD Group Membership and AD Group Discovery finds it, it won't check if it is valid, but write the DDR and create the object record in SCCM DB.

Please change AD Group Discovery so it validates new objects too.

Machines with an EEC client certificate can connect to the DP to download the content and install the agent but the client never registers with the site.

once i suspected the ECC certs I was able to find thread on technet which confirms the same issue I was seeing
https://social.technet.microsoft.com/Forums/en-US/cc9ec0ff-5998-4225-9ce1-2c7b5fe5677d/sccm-and-ecc-certificates-not-supported?forum=ConfigMgrDeployment

Having the ability to use Client Push more granularly would be awesome. We have about 6 domains, and multiple OUs are defined in System Discovery, yet I don't want Client Push enabled on them all, so it is currently disabled. Maybe having an option in the Discovery area, for an OU that is added (right where it says "Search AD Groups and Search Child containers") that enabled Client Push on that discovered OU. Or More granular settings on Client Push itself, maybe a small GUI attached to it

We would like the ability to have seperate client push settings for Workstations vs Servers, specifically the ability to have seperate installation properties.

Hello

can you please support Mac OS 11.

Thanks.

If the ccmexec.exe is missing (ie Malware) the ccmeval is not able to remediate and it does not trigger a repair of the SMS Agent Host client

It would be great if we could exclude certain OS's from discovery. I have over 5500 machines in my DB that I couldn't care less about but they reside in an OU where I have machines I do care about.

Create a new Parameter for the ccmsetup to use the latest Client Version. Currently there is no Opportunity to install the newest Client Version by Script. So in Cases of Troubleshooting the Client will be installed/updated two times within an short period.

While working with boot images, I need to click UPDATE DISTRIBUTION POINTS and see if the client within the boot image is the same as the client on the site server. It would be nice if I can see the current (latest) ConfigMgr agent shown in HELP-ABOUT from ConfigMgr console as a all-in-one screen so I would spare some time checking and updating the boot images

With R2SP1 automatic client upgrades will now function for the first time in an R2 environment.

It would be nice if that deployment wasn't hidden though so we could actually see the progress of the clients being upgraded.

If I import a new computer using its MAC Address but later I install manually the client in the actual computer, two resources with the same name end up in the SCCM Database.
An option to make the default action merging both resources or just associating the client DDR to the manual import.