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 found some strange behavior's when having a Pull DP deployed and will deploy a SCCM Agent later. This occurs only when the newest Client version has not been upgraded to production.
According to https://technet.microsoft.com/en-us/library/gg712321.aspx> the versions must be the same.
---
On a computer that is configured as a pull-distribution point and that runs a Configuration Manager client, the version of the Configuration Manager client must be the same as the Configuration Manager site that installs the pull-distribution point. This is a requirement for the pull-distribution point to use the CCMFramework that is common to both the pull-distribution point and the Configuration Manager client.
---

Ask: can't we make sure that all agents in the infrastructure run the latest client version.

Workaround for now is to add all PullDP servers to the Pilot collection to ensure they are upgraded in a timly manner.

We found some strange behavior's when having a Pull DP deployed and will deploy a SCCM Agent later. This occurs only when the newest Client version has not been upgraded to production.
According to https://technet.microsoft.com/en-us/library/gg712321.aspx> the versions must be the same.
---
On a computer that is configured as a pull-distribution point and that runs a Configuration Manager client, the version of the Configuration Manager client must be the same as the Configuration Manager site that installs the pull-distribution point. This is a requirement for the pull-distribution point to use the CCMFramework that is common to both the pull-distribution…

1. Add an "exclude collection" to client push properties so that *nix clients can be excluded.
2. Fix the OS type of *nix clients so that they don't show as Windows and CCM doesn't try to push to them.
3. Add an option for exclude OU's in Active Directory System Discovery so that *nix OU's can be excluded.

The SMS_ExcludedMachineNetBIOSName option isn't an attractive workaround since we have thousands of *nix clients and new hosts are being added often.

In cases where we need to install the SCCM client from a script or other process, Ccmsetup.exe launches sub processes then exits. This makes monitoring the installation difficult. It would be helpful to have the setup behave more like a traditional installer.

Fix this problem Software Center not working after SCCM Client update from 5.00.8540.1007 to 5.00.8540.1611 also the clients are not upgrading properly. You have to run a repair to get the ner client to finish installing.

Please create a possibility to create new OS Image automatically without downloading auf importing the Image. Same for Upgrade packages . And we Need a Working Solution for MUI Installations. TS Variable UI Language in unattend File dont Work since 1607.

Stop the DCOM 10028 errors on a Primary site server that FLOOD the System logs when the primary attempts to contact an MP in an untrusted domain\forest.

I believe this a result of the order in which CM tries to authenticate to the MP - computer account then network service account - neither of which will work in an untrusted domain scenario. The connection eventual happens as expected using the Installation account. The DCOM errors are bogus errors that can consume a log file for no reason. Seems like some deeper error logging\checking is needed?

Production Client Deployment dashboard displays duplicate records especially for Not Compliant subset of discovered computers. It's confusing because it shows data which is not in line with the real client numbers. It seems like the report shows every state message reproted by the particular machine related with client installation. for some of them, there are more than one such message, so the machine comes up multiple time and the total count is wrong.

I configured a Fallback Status Point on a test site and noticed illogical behavior.
IntranetHostName Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\FSP gets the new FSP, but Hostname doesn’t get this value. This is noted in LocationService.log every 25 hours ‘Updated FSP … from AD to local. When I execute ccmsetup.exe on a machine both values get the new FSP.

I presume the next message means the FSP Message got send with the InternalHostname afterwards.
State message with TopicType 1000 and TopicId CCM Framework Communication State has been sent to the FSP
These Errors went away when I changed the HostName Value.

The FSP was configured as Intranet Only. This could explain why only the InternalHostName is set. But not why ccmsetup will still set both. And I think Hostname should be ignored when it’s empty.
The current behavior creates the impression something is not working when you look at FSPStateMessage.log.

I will change the HostName value in the registry to avoid these errors in the logs. This will also happen when ccmsetup is executed again on these clients.

Could you consider to change the behavior.
- Set Hostname consistently
- Don't try to contact Hostname when the value is empty.

Currently running CM1702+kb4019926+kb4038659

I configured a Fallback Status Point on a test site and noticed illogical behavior.
IntranetHostName Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\FSP gets the new FSP, but Hostname doesn’t get this value. This is noted in LocationService.log every 25 hours ‘Updated FSP … from AD to local. When I execute ccmsetup.exe on a machine both values get the new FSP.

While we have this great feature called 'Client Push Installation for Configuration Manager client' and we can turn it on for 'Just Servers' or 'Just Desktops' It would be REALLY wonderful if we could specify a collection we DONT want automatic push to work for. There are certain devices that due to regulation just can't have the client installed. Sucks I can't turn the feature on because 1-5% of my environment can't have the client.

I'm hoping that since we've already got that logic for clients we don't want to automatically upgrade that something like this might even be easy to accomplish.

While we have this great feature called 'Client Push Installation for Configuration Manager client' and we can turn it on for 'Just Servers' or 'Just Desktops' It would be REALLY wonderful if we could specify a collection we DONT want automatic push to work for. There are certain devices that due to regulation just can't have the client installed. Sucks I can't turn the feature on because 1-5% of my environment can't have the client.

I'm hoping that since we've already got that logic for clients we don't want to automatically upgrade that something like this might even be easy…

Bug fix needed. When I pin the control panel to my taskbar and use the configuration manager applet it appears when I hover over the pinned control panel app on my task bar but it does not work, instead it fails

We are having issues with the metadata on the update occupying the CPU on our SCCM management point which causes TransientErrors on any of the BITS jobs that are in process during the CPU timeout.

The problem is that the commands to reset the BITS queue on the SCCM clients don't work even in the built-in Administrator account with elevated powershell as there isn't "sufficient permissions." forcing us to reinstall the client on ALL of our machines.

SCCM BITS jobs should retry or rerun after being in the TransientError state for some time, maybe 15-30 minutes.

Enhance site auto upgrade option for servers. Provide the ability to control the schedule for server operating system client upgrade using a maintenance window type Client Upgrade. Server changes in production fall under change management control. It would be great to be able to specify when the upgrade will take place so that we can align to the change process. This will be similar to MW type SUM and gives more control. Auto Upgrade is great but not having a predictable dedicated MW for Servers makes it difficult to get acceptance to use for servers. Though MW is respected the existing MW for servers are normally set for other know activities like patching and ad-hoc MW for SD.

Enhance site auto upgrade option for servers. Provide the ability to control the schedule for server operating system client upgrade using a maintenance window type Client Upgrade. Server changes in production fall under change management control. It would be great to be able to specify when the upgrade will take place so that we can align to the change process. This will be similar to MW type SUM and gives more control. Auto Upgrade is great but not having a predictable dedicated MW for Servers makes it difficult to get acceptance to use for servers. Though MW is respected the…

Enhance site auto upgrade option for servers. Provide the ability to control the schedule for server operating system client upgrade using the auto upgrade feature. Server changes in production fall under change management control. It would be great to be able to specify when the upgrade will take place so that we can align to the change process. So include schedule option for servers and collection selection

If sccm is set to NOT auto approve workgroup devices it would be super if there was a function to auto approve devices added to certain collections. That way organizations could choose to auto approve certain machines based on collections and their membership rules instead of either auto approving ALL machines or NO machines.

Provide the option for permissions that would disallow client push. We would like to provide access to users to manage SCCM but do not want them to be able to push the client from ConfigMgr. In our particular case, client push does not work with our network setup, so if someone attempts to do a client push, the process gets stuck. I can imagine some security reasons for this setting as well.

While running a task sequence I would like to see the option to create a custom Task Sequence Variable and it's value depending on a return code from a running step (cmdline, PowerShell script, Application, Package). This variable can be used later on in the TS to run or skip specific steps.
Think about additional reboot steps if a BIOS flash is performed (if no flash is performed you don't want a reboot). Currently I need to create and run a powershell script to make this happen.

Microsoft provided the ability to check for and close running applications during install operations. We would really like the ability to perform the same action during removals (and include a comment field to inform the user why these applications need to be closed).

Example: Application X is currently running which halts the removal of application Y. It would be beneficial to detect these running applications, prompt the user to close (or force close after a set time), and allow the removal of application Y to continue.