tag:blogger.com,1999:blog-7396481053359703519.post8726851635364025459..comments2024-03-26T04:04:33.060+01:00Comments on Henk's blog: How to manage Obsolete clients in ConfigMgrHenk Hoogendoornhttp://www.blogger.com/profile/01066841733613965112noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7396481053359703519.post-80760931522062575812013-09-11T09:30:46.458+02:002013-09-11T09:30:46.458+02:00Not valid anymore, because SCCM 2012 will merge an...Not valid anymore, because SCCM 2012 will merge an object after re-deployment. No need to delete obsolete objects anymore. Much better this way!Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-24582627220545359802013-09-09T22:51:37.965+02:002013-09-09T22:51:37.965+02:00how to do it on SCCM 2012?how to do it on SCCM 2012?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-90640485540590372412011-03-16T22:05:40.561+01:002011-03-16T22:05:40.561+01:00Sometimes I use a query on the client name to mana...Sometimes I use a query on the client name to manage collection memberships instead of direct allocations. That way the new clients appear in the same collections as obsolete ones automatically.Anonymousnoreply@blogger.com