Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice - Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

Scott Macpherson

My feedback

  1. 26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Scott Macpherson supported this idea  · 
  2. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Client Discovery  ·  Flag idea as inappropriate…  ·  Admin →
    Scott Macpherson supported this idea  · 
    An error occurred while saving the comment
    Scott Macpherson commented  · 

    We just had this issue and resolved it with our PFE. We are on SCCM CB 1610 and will be updating to 1706 in a couple of weeks. We found that new AD sites were not being brought into our Boundaries thru the Forest Discovery. We have 33 other Forests trusted to our main Forest we are migrating all 33 into. The Discovery was stopping after 7 Forests were discovered. Seemed like it was discovering them alphabetically from the bottom up. An error message was found in the ADForestDisc.log log that states " ERROR: [ForestDiscoveryAgent]: Discovery is being aborted due to an unexpected exception.". No other errors were found. We resolved this temporarily by turning off discovery for all domains that are not primary to our needs and the discovery completes successfully now. We only have this environment published to 2 of the 33 Forests. Maybe if the Discovery were set to on do Forests that are published to and we have to turn on any others we want would be beneficial.

Feedback and Knowledge Base