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. Unable to import state message from 'co-management' enabled client

    nable to import status message when following condition.
     ・Clients with co-management enabled
     ・If the state message(.SMX) contains Japanese

    ◆Error Log
    [statesys.log]
    SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 241 at record 53 for TopicType 810:
    " Conversion failed when converting date and/or time from character string.", Line 0 in procedure ""

    ◆state message(.SMX)
    -<StateMessage SerialNumber="593" MessageTime="20180427063011.557000+000">
    <Topic UserSID="" User="" IDType="0" Type="810" ID="CoManagementState"/>
    <State ID="105" Criticality="0"/>
    -<StateDetails Type="1">
    -<![CDATA[<ClientCoManagementMessage><MDMEnrollment><Enrolled Value="0" /><ServiceUri Value="" /><RegistrationKind Value="0" />
    <ScheduledEnrollTime Value="04/27/2018 06:30:11 午前" /><ErrorCode Value="2147549183" />
    <ErrorDetail Value="MDM enrollment hasn't been configured yet on AAD, or the enrollment url isn't expected."…

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Co-Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Enable co-management using multiple ConfigMgr hierarchies to one Intune tenant

    Some customers has multiple SCCM environments (Test and Production), and want to enable co-management from multiple (two) ConfigMgr hierarchies.
    They need to test and verify that nothing is broken before moving into production.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Co-Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Enable Azure Resource Management for Cloud DPs

    It would be great if you had the same ability to create a cloud DP like you can with the cloud gateway. Utilizing the classic installation type of using a certificate to create the cloud DP is cumbersome and prone to simple errors.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Co-Management  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base