SCCM update membership of device collection (OU based) not working

Question

SCCM update membership of device collection (OU based) not working

Eaven HUANG 2,191

Dear Experts,

We are running SCCM CB2111 version and our device collections are using OU queries to synchronize them from on-premises OUs. It works just fine when creating new collections, it detected and collected all the AD computers without any issues.

However, we moved out some computers from the OUs, I right-clicked on device collection to update membership a few times in a day. 24 hours passed and now those specified computers (which had been moved out of OU from AD) are still there in SCCM collection.

Anything I'm missing and how we can update our collection to reflect the same as what displayed in AD OUs?
Thanks a lot!

Accepted answer

1 additional answer

Your answer

Answer 1

Amandayou-MSFT 11,156

Hi @Eaven HUANG ,

Could we know how we schedule a full update on this collection? The default is every 7 days, so 24 hours passed and now those specified computers (which had been moved out of OU from AD) are still there in SCCM collection.

We can modify it according to our requirements.

I test it in my environment, and I modify the tab to every 3 minutes.

After I create the collection, there are 7 clients in this collection.

And I move one client to another OU, and after 3 minutes, there are 6 clients in this collection.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Eaven HUANG 2,191 Reputation points

2022-04-27T09:23:53.063+00:00

Dear @Amandayou-MSFT ,

I did what you suggested and yes it's working this way.
By default it's actually running every 7 days. so if we wanted to see the updates, we have to manually change this timeframe? I guess right-click on Update Membership didn't really work in such case?

Thanks again for your super nice support!
Amandayou-MSFT 11,156 Reputation points

2022-04-28T02:51:03.58+00:00

Hi,

Thanks for your reply.

Yes, in default, it runs every 7 days, if we want to see the changes faster, we should change the schedule manually.

What I don't understand is that, when we created these collections, there was no clients installed in any of the computers but SCCM collected them already. Now we updated some computers, it required CCM agent?

Yes, it is normal, in the query, which just query the computer in OU named xx.COM/xx.COM not sccm client:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = "xx.COM/xx.COM"

so these computer appear in this collection. If we want to deploy client to this computer, we could push client to this computer.

Answer 2

Garth 5,801

This is a loaded question and will depend on if the computers have the cm client installed. If so then heartbeat discovery must be run first then the collection membership can be updated.

Eaven HUANG 2,191 Reputation points

2022-04-28T02:27:24.963+00:00

Hi @Garth ,

I tried the solution provided by Amanda and it worked.

What I don't understand is that, when we created these collections, there was no clients installed in any of the computers but SCCM collected them already. Now we updated some computers, it required CCM agent?

Share via

SCCM update membership of device collection (OU based) not working

1 additional answer

Your answer