Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

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.

Please do not use UserVoice to report product bugs or for assisted support.
If you believe you have found a product bug, please send us a bug report through the Configuration Manager Console (1806 and newer). To do this, press the šŸ™‚ button in the top right corner and choose ā€œSend a Frownā€. For more details, seeĀ https://docs.microsoft.com/en-us/sccm/core/understand/find-help.

If you require assisted support, please see https://aka.ms/cmcbsupport for more details.

Standard Disclaimer ā€“ our lawyers made us put this here ;-)
We have partnered with UserVoice, a third-party service, so you can give us feedback. Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft Configuration Manager. Do not send any novel or patentable ideas, copyrighted materials, samples or demos. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Export all data option for key nodes

    I would like the ability to right-click various nodes, eg packages, applications, task sequences, etc and export the data for that node to a file, eg csv which could easily be read back in via powershell. This would allow test environments to be set up quickly and might even help provide an a way to restore a production environment if all else fails...

    3 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Add NumberOfDependedDTs property to Get-CMApplication

    Currently, the only place to see NumberOfDependedDTs is from Get-CMDeploymentType. Other properties like NumberOfDependentDTs and NumberOfDependentTS have been propagated to the Application Level, it would be useful to have NumberOfDependedDTs too.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. 4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Remote powershell for SCCM

    Like: Import-PSSession $(New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://server.domain.local/PowerShell/)
    -But for SCCM..

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. Issues with Import-ClientConfiguration

    Import-CMComputerInformation is not allowing me the same access via Powershell as the console itself.

    https://www.reddit.com/r/SCCM/comments/6dipv2/permissions_to_importcmcomputerinformation/

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Run Scripts: Show PowerShell Intellisense in script editor prompts

    Now that we have the ability in TP1706 to upload and run PowerShell scripts against endpoints, it has exposed the need to be able to tab complete and validate syntax with intellisense from the console. I'm not asking you to recreate the PowerShell ISE/VSCode, just some rudimentary intellisense for when you are working on the Admin Console.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Allow Wildcard for cmdlets Get-CMPackage and Remove-CMPackage

    This would make it easier to remove multiple packages with similar names.

    3 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Allow use if DeploymentID as identifier in Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment

    Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment do not allow DeploymentID as unique identifier. Instead you need to use e.g. programname and packageid.

    In the case of Set-CMSoftwareUpdateDeployment this requires DeploymentName which is not even possible to retrieve from Get-CMDeployment

    Please, allow DeploymentID as an option to identifying the deployment in these cmdlets.

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. PowerShell cmdlet "Remove-CMMaintenanceWindow" should accept Window Time as parameter

    Powershell cmdlet "Remove-CMMaintenanceWindow" should accept StartTime as a parater. Current implementation only accepts limited parmaters of collectionid, and maintenance window name. If you have two windows by the same name, with different start times... you will remove both by using this utility. I suggest it should also accept the StartTime as a paramter for specific window deletion. Maintenance windows are a point in time schedule, and therefore the Point in time should be considered as a parameter for removal. The current implementation of this cmdlet is dangerous, and cannot be used for finite window removal.

    5 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Collection Configure Alerts

    Create a powershell to configure the alerts on a specific collection. like adding collection to EP dashboard and configure thresholds

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. The cmdlet move-cmobject FolderPath does not reflect name of Applications node

    The folder names are different in the console and the cmdlet Move-CMObject.
    Console: Applications
    Cmdlet: Application
    Since this is a standard folder regardless of site code, the names should be the same.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. Included canned powershell scripts

    Include canned scripts for creating collections applications and deployments with the ability to create a template from selections.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. Set-CMAutoDeploymentRuleDeployment to include missing AllowWUMU and AllowUseMeteredNetwork

    Although you can now add multiple deployments to a single Automatic Deployment Rule there a couple of options that can be read but not set. These are:

    "If software updates are not available on the distribution point in current, neighbor or site boundary groups, download content from Microsoft Updates."
    and
    "All clients on a metered internet connection to download content after the installation deadline, which might incur additional costs"

    I can successfully retrieve all Deployments associated with an Automatic Deployment Rule via the Get-CMAutoDeploymentRuleDeployment cmdlet and see the current settings for these properties by parsing the DeploymentTemplate XML.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. CM Pivot - have autostart use the SMS_Autostartsoftware wmi class

    CM pivot appears to just list the registry autostart locations.
    Please use the SMS_autostartsoftwarewmiclass.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. Server groups (cluster patching) - Powershell cmdlets

    Please add cmdlets, to be able to configure and maintain server groups.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. PowerShell Cmdlet to collections & deployments for a computer

    Would be good to have a PowerShell CmdLet to get information on all collections and deployment for a computer is listed for.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
1 2 3 5 Next →
  • Don't see your idea?

Feedback and Knowledge Base