I was going to also recommend that you increase the interval for which you clean out “aged” clients. However, it seems that you have already recognized that 7 days is far too short for that particular setting. I would suggest a value not less than 30.
To echo what David O’Brien has already stated, query-based rules for ConfigMgr collections are also a recommended approach to collection building. Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: Wednesday, January 8, 2014 6:42 AM To: [email protected] Subject: RE: [mssms] Console Auto-cleaning Correct. I would believe they will be getting a new ResourceID and such won’t retain direct memberships. One of the reasons I rarely work with „Direct Memberships“, besides OSD. Try doing as much as possible with „Query based membership”. David ------ Microsoft MVP for Enterprise Client Management From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Mittwoch, 8. Januar 2014 13:34 To: [email protected] <mailto:[email protected]> Subject: Re: [mssms] Console Auto-cleaning If the collections are based upon direct membership then I would anticipate the membership not being retained. Sent from Windows Mail From: Gary Ossewaarde <mailto:[email protected]> Sent: Wednesday, 8 January 2014 12:33 To: [email protected] <mailto:[email protected]> Over Christmas break (higher ed), we had most of our computers disappear from Config Manager (2012). My site was set to deleted aged clients after 7 days (which, after this break, we have decided is too short of a time). My question is, when computers show back up in config manager (as they have been), will they retain collection membership? We have software deployed to collections and the HelpDesk assigns the machine as a direct rule to the collection to assign software. Will these clients need to be re-added or will they show back up in their appropriate collections? Thanks, Gary
