locked
Collection update OU RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    We use a device collection which queries a OU in AD. The collection schedule is to run every 5 minutes.

    So basically if we move or remove a computer account from the OU the collection will update every 5 minutes. It's like a sync.

    Unfortunately it's broken since today and the collection doesn't really update. I can move a computer account to another OU and the collection will not update.

    How do I best troubleshoot this. Is there a log for collection?

    Thanks,

    Edy

    Edy from Switzerland

    Tuesday, June 16, 2015 6:29 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    We use a device collection which queries a OU in AD. The collection schedule is to run every 5 minutes.

    So basically if we move or remove a computer account from the OU the collection will update every 5 minutes. It's like a sync.

    This is not correct. Your collection query can only query what's in the ConfigMgr db. Thus, the AD information in ConfigMgr must also be updated for the query to pick up any changes. This is done by AD System Discovery as Jeff indicated and so you need to check to make sure it is running properly and is also configured to use delta discovery.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Tony Chirillo Wednesday, June 17, 2015 3:41 PM
    • Marked as answer by Edy Werder Wednesday, June 17, 2015 7:38 PM
    Tuesday, June 16, 2015 7:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In other words to Jason's response, if the computer object does not show up under devices or the 'all systems' collections first, it won't show up in any other collections. If system discovery is not working correctly, computer objects won't show up in 'all systems' or other devices.  See how things trickle down. One more thing to keep in mind is for AD System Discovery to work the AD object most have an active DNS record. What that means is if you create a new AD object, it won't show up in SCCM until it has an OS installed on it. Hope all this helps!

    -Tony

    • Proposed as answer by Tony Chirillo Wednesday, June 17, 2015 3:41 PM
    • Marked as answer by Edy Werder Wednesday, June 17, 2015 7:37 PM
    Wednesday, June 17, 2015 3:41 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    colleval.log

    https://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SiteSiteServerLog

    AD discovery would need to be configured for deltas as well.

    Jeff

    Tuesday, June 16, 2015 6:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks,

    The colleval.log is fine. There are no errors. I runs every 5 minutes. It seems the collection doesn't catch when I remove a computer to another OU.

    Edy from Switzerland

    Tuesday, June 16, 2015 6:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What happens if you run a full AD system discovery?

    Jeff

    Tuesday, June 16, 2015 6:59 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    We use a device collection which queries a OU in AD. The collection schedule is to run every 5 minutes.

    So basically if we move or remove a computer account from the OU the collection will update every 5 minutes. It's like a sync.

    This is not correct. Your collection query can only query what's in the ConfigMgr db. Thus, the AD information in ConfigMgr must also be updated for the query to pick up any changes. This is done by AD System Discovery as Jeff indicated and so you need to check to make sure it is running properly and is also configured to use delta discovery.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Tony Chirillo Wednesday, June 17, 2015 3:41 PM
    • Marked as answer by Edy Werder Wednesday, June 17, 2015 7:38 PM
    Tuesday, June 16, 2015 7:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks about system discovery, yes I think this is an issue. I ran a new discovery and it has found more system. I un-ticked the box about computers not logged in for a certain time.

    I have a question re AD containers. Can I just select the container on the top level of my OU and it will discover all systems below it even there are sub OU's?

    I ticked "recursively search Active Directory child containers"

    Thanks,

    Edy from Switzerland

    Tuesday, June 16, 2015 8:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a question re AD containers. Can I just select the container on the top level of my OU and it will discover all systems below it even there are sub OU's?

    I ticked "recursively search Active Directory child containers"

    Yes, that's what that option does.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, June 16, 2015 8:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In other words to Jason's response, if the computer object does not show up under devices or the 'all systems' collections first, it won't show up in any other collections. If system discovery is not working correctly, computer objects won't show up in 'all systems' or other devices.  See how things trickle down. One more thing to keep in mind is for AD System Discovery to work the AD object most have an active DNS record. What that means is if you create a new AD object, it won't show up in SCCM until it has an OS installed on it. Hope all this helps!

    -Tony

    • Proposed as answer by Tony Chirillo Wednesday, June 17, 2015 3:41 PM
    • Marked as answer by Edy Werder Wednesday, June 17, 2015 7:37 PM
    Wednesday, June 17, 2015 3:41 PM