Sccm update collection membership not updating
Here is an example: Fix: In this scenario, the issue is that “The Device” is not part of “Dallas Devices”.
They factor into almost everything from deployments to client settings, to… It just so happens that collections are a unique breed of things that are easy to understand but difficult to master.I ended up with a script that I sent to the member and thought that I’d share here as well. What happens in the background is that the script will enumerate all collections for those that contains a membership query rule and evaluate that rule checking for a match in the SQL query statement of what’s specified in the Locate parameter. This is how the output looks like when I executed the script in my lab environment: Here’s a short video clip of the scenario that is described in this post: Principal Consultant and Enterprise Mobility MVP since 2016.You can get your hands on the script from this Tech Net Gallery page. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation.The problem the member was facing concentrated about a migration project they were working on where part of the WQL query statement would have to be amended, e.g. System Group Name like "CONTOSO\\ I want to change the Domain name from CONTOSO to FABRIKAM. Open an elevated Power Shell console and browse to C:\Script, or where else you have stored the script. Run the following command: Since we’ve included the -Verbose parameter in the command above, we’ll be presented with lot’s of verbose output.you would like to replace a Domain name in the query or perhaps a group name. Since both of the collections have this string in common, I can simply execute my Update-CMCollection Query.ps1 script to locate CONTOSO and replace that with FABRIKAM. You can also specify the -What If or -Confirm parameters if you’d like.At pm on Wednesday, the client moves into the “IBM Laptop Devices” collection. The update times are get earlier as we move closer to the “IBM Laptop Devices” collection.
Fix: All collections times in the limiting train need to be in Ascending order from All Systems to the “IBM Laptop Devices” Collection.
Here is one example of a simple fix: In the scenario above, clients will now move from “All Systems” to “IBM Laptop Devices” somewhere in the range of 2 hours if added before pm, and as many as 24 hours if added after pm.
Cause: There are too many collections with incremental update cycles.
Chances are that we develop quite a backlog and the line grows longer and longer.
For Collections, this is usually due to a high number of scheduled updates taking place together.
A member of the Swedish System Center User Group, also known as SCUG, asked for some help with updating all the collections that had membership queries matching a specific pattern/text.